Skip to content

API reference ​

Everything Tamga Network exposes over HTTP: the services you call with your own credentials, and the public registries anyone can download.

Most integrations do not call these endpoints by hand: the @tamga-network/* packages wrap them, check signatures and follow the rules for you. Use this reference when you want to see exactly what goes over the wire, write a client in another language, or debug.

Services ​

Public registries ​

At a glance ​

APIBase URLAuthenticationWho calls it
Tamga Verifyhttps://verify.tamga.networkRP assertion signed with your access certificateyour server (and your page, with a status token)
Hosted issuerhttps://issuer.tamga.network/{slug}/api/v1scoped API key tmg_<slug>_…the institution's server
Institution sourceyour URLsigned request from the hosted issuer (you verify it)the hosted issuer
Trust listshttps://trust.tamga.networknone — public, signed fileseveryone, through TrustSource
Status listshttps://status.tamga.networknone — public, signed tokensverifiers
Schema cataloguehttps://schemas.tamga.network/v1none — publicissuers, verifiers, wallets

Environments ​

Every service has a sandbox twin with the same rules on a separate test network (GUIDE-0013). The sandbox lists carry environment: sandbox; a loader configured for the real network stops on them, and the other way round.

Real networkSandbox
verify.tamga.networkverify.sandbox.tamga.network
issuer.tamga.networkissuer.sandbox.tamga.network
trust.tamga.networktrust.sandbox.tamga.network
status.tamga.networkstatus.sandbox.tamga.network
id.tamga.networkid.sandbox.tamga.network
schemas.tamga.networkshared

Conventions ​

  • JSON over HTTPS. Requests and responses are UTF-8 JSON unless the page says otherwise (signed files are compact JWS: application/jose, application/statuslist+jwt). Times are ISO 8601 in UTC, or Unix seconds where the field says so.
  • No shared secrets for verifiers. Tamga Verify authenticates your server with a 60-second statement signed by the key of your registered access certificate; there is nothing to leak or rotate on our side (ADR-0017).
  • Errors. Tamga Verify answers { "error", "error_description" } (OAuth style); the hosted issuer answers RFC 9457 problem details (title, status). A missing or foreign resource is always 404 — existence is never revealed.
  • Rate limits. Over the limit you get 429 with Retry-After (seconds). Client addresses are not stored or logged.
  • Three outcomes. A verification is ACCEPTED, REJECTED or INDETERMINATE. "Could not check right now" is never "invalid".
  • No personal data in logs. Never log credential values, the status index or identity matching keys — on your side either (SPEC-API-0001 AP3–AP4).
  • Registries are cacheable. Trust lists, status lists and the catalogue are static, served with CORS * and a short cache; always check the signature, not the transport.

Standard protocol endpoints ​

Wallets talk to the services with the standard EUDI protocols — OpenID4VCI (OpenID for Verifiable Credential Issuance)The protocol an issuer uses to deliver a credential to a wallet. for issuance and OpenID4VP (OpenID for Verifiable Presentations)The protocol a verifier uses to request a credential from a wallet and receive the presentation. for presentation. You do not call these yourself (the wallet and the packages do), but they are listed here so that a wallet developer knows what to expect. The binding profiles are SPEC-PROTO-0001 and SPEC-PROTO-0002.

Hosted issuer — https://issuer.tamga.network ​

EndpointPurpose
GET /.well-known/openid-credential-issuer/{slug}Credential Issuer Metadata; signed with Accept: application/jwt
GET /.well-known/oauth-authorization-server/{slug}Authorization server metadata
GET /{slug}/offers/{id}Credential offer (the credential_offer_uri target; no personal data)
POST /{slug}/par · GET /{slug}/authorizePushed authorization request and authorization — identity-bound offers and requests started from the wallet
POST /{slug}/tokenToken (pre-authorized code, authorization code, refresh token); DPoP (Demonstrating Proof of Possession)A way to bind an access token to a key, so a stolen token cannot be used without that key.-bound
POST /{slug}/nonceFresh c_nonce for key proofs
POST /{slug}/credentialCredential issuance (DPoP, key proof, wallet attestation)
GET https://status.tamga.network/{list_id}The issuer's status lists

Identity service — https://id.tamga.network ​

The provisional identity attestation provider (ADR-0022). The same OpenID4VCI endpoints without the {slug} segment: /.well-known/openid-credential-issuer, /.well-known/oauth-authorization-server, /par, /authorize, /token, /nonce, /credential, and the status lists under /status/{list_id}. Identity proofing happens inside this service only.

Tamga Verify — https://verify.tamga.network ​

EndpointPurpose
GET /vp/req/{id}Signed request object (application/oauth-authz-req+jwt) — the request_uri in the QR code
POST /vp/responseThe wallet's encrypted response (direct_post.jwt); rate-limited
GET /p/{id}The hosted waiting / result page for people (HTML)

Machine-readable definitions ​

Each reference page is generated from an OpenAPI 3.1 file. Import it into any OpenAPI tool to generate a client or send test requests:

DefinitionFile
Tamga Verify APIhosted-verifier-api.openapi.yaml
Hosted issuer APItamga-issuer-api.openapi.yaml
Institution source endpointinstitution-source.openapi.yaml
Trust liststrust-lists.openapi.yaml
Status listsstatus-lists.openapi.yaml
Schema catalogueschema-catalogue.openapi.yaml