GET

Developer documentation

Get SDK publication catalog

/api/v2/developer-portal/sdks

AUTHENTICATIONNone · publicService ownerdeveloper-platformContract sourceOpenAPISTATUSProduction listed

Purpose and usage

What this endpoint does

Return official SDK publication status and the authoritative OpenAPI generation contract; an empty package list means no official SDK is currently published.

When to use it

Use before selecting a generated or official client package so automation can distinguish a published, checksummed SDK from a client it must generate from OpenAPI.

OUTCOME · Discover

What changes

Read-only projection; it grants no mutation, settlement, traffic, or authority change.

WHY IT MATTERS

Gives people and agents a contract-backed way to discover sdk publication catalog.
Gives human and agentic integrations one discoverable path from service identity and reference data to executable OpenAPI, capability ownership, guides, SDK status, and request-signing controls.

ISOLATION + AUTHORITY

Public service metadata, the OpenAPI document, the capability registry, guides, SDK listings, bearer credentials, step-up grants, and request-signing keys are separate artifacts. Discovery metadata grants no tenant, wallet, custody, payment, settlement, publisher, matching, or trading authority; public signing-key metadata never includes private key material.

BEFORE YOU CALL

No bearer credential is required; apply bounded filters and canonical public identifiers where the contract provides them.
Use the live OpenAPI schema as the authority for the exact request shape and response model.
Resolve whether the caller needs public discovery, bearer authorization, purpose-bound step-up, or RFC 9421 request signing; do not substitute one mechanism for another.

WHAT TO DO NEXT

Follow the returned authoritative OpenAPI, capability, guide, or SDK link appropriate to the integration task.
Validate executable behavior against deployed OpenAPI rather than inferring it from narrative guidance or package names.

AGENT GUIDANCE

Use sdk publication catalog only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
Use the live OpenAPI schema as the authority for the exact request shape and response model.
Treat deployment identity, OpenAPI schema, capability readiness, guide narrative, SDK publication, bearer authorization, step-up authorization, and request-signing proof as distinct inputs; none substitutes for another.
Use response links and canonical identifiers instead of constructing internal service URLs or scraping the website.

Contract reference

Use the deployed OpenAPI for exact parameters, schemas and security requirements. The tables below provide integration guidance.

Open this operation in OpenAPI

Request and response

Make the request

Examples illustrate integration intent; the referenced OpenAPI operation and component schemas define the executable shape.

PARAMETERS

Headers, path, query, and body

NAMELOCATIONPRESENCETYPE / RULES / PURPOSE

RESPONSES

Status and payload examples

200Official package publication catalog and authoritative OpenAPI client-generation link.Read completed · JSON RESPONSE+

{
  "officialSdks": [],
  "generationContract": {
    "rel": "openapi",
    "href": "/api/v2/openapi.json",
    "mediaType": "application/vnd.oai.openapi+json;version=3.1",
    "description": "Use this authoritative implemented-route contract for generated clients."
  },
  "note": "No official versioned SDK package has been published yet. Empty means unavailable; it is not a placeholder claim."
}

INTEGRATION DECISION

CALLER ACTION: Accept the returned representation or receipt, then follow the returned authoritative OpenAPI, capability, guide, or SDK link appropriate to the integration task.
RETRY SAFETY: Repeat only when the integration needs a fresher authoritative projection.
STATE RECONCILIATION: Use returned identifiers and versions as the comparison point for later reads. Refresh the application, credential or callback record; compare scope, key identifier, secret-display state, version, and revocation or rotation receipt.

OPERATIONAL NOTES

Security and lifecycle guarantees

An empty officialSdks array means no official versioned SDK is published. It is not an incomplete response and does not authorize an integration to invent package coordinates.
When no package is listed, generate a client from generationContract.href and retain the observed OpenAPI SHA-256, generator name and version, settings, selected operations, and artifact digest.
When packages are later listed, verify language, package, version, status, sourceUrl, and checksum before use; catalog presence does not install or endorse a package for every runtime.
No bearer, query parameters, or request body are accepted. The response is cacheable for 300 seconds.

Reference version and availability details

This route is implemented in canonical gateway source and appears in the production OpenAPI snapshot observed 2026-10-02T23:27:55.510Z. Authentication, tenant, feature, venue, and market policy still apply.

Verify the exact production OpenAPI operation Return to the V2 directory