openapi: 3.0.3
info:
title: Terminal 3 DID V1 VC V1 API
version: '1.0'
description: Terminal 3 (T3) REST API for decentralized identity, verifiable credentials, OpenID Connect, sub-client management, transactional email, and user data. Reconstructed from Terminal 3's own published SDK & API Reference (https://docs.terminal3.io/developers/adk/reference), which enumerates every path, method, and tag as verified against the provider's terminal-3-openapi.yml (21 paths, 24 operations, OpenAPI 3.0.3). Request/response body schemas are not reproduced here because the raw spec file is served only through the Mintlify viewer and returns 404 as a downloadable document; this capture is structural (paths, methods, operationIds, tags, security, server) and carries no fabricated field-level schemas. Verify field shapes against the live API Reference.
x-provenance:
method: generated
source: https://docs.terminal3.io/developers/adk/reference
note: Structural reconstruction from the provider-published operation table; raw terminal-3-openapi.yml (referenced in llms.txt) 404s as a file.
generated: '2026-07-21'
servers:
- url: https://staging.terminal3.io
description: Documented REST API server (per the published API Reference)
security:
- bearerAuth: []
tags:
- name: VC V1
description: Verifiable Credential issuer operations.
paths:
/v1/vc/issuer/credentials:
get:
operationId: getIssuerCredentials
summary: Get issuer credentials
tags:
- VC V1
responses:
'200':
description: Success
'401':
$ref: '#/components/responses/Unauthorized'
/v1/vc/issuer/credentials/proof:
post:
operationId: createIssuerCredentialsProof
summary: Create a proof for issuer credentials
tags:
- VC V1
responses:
'200':
description: Proof created
'401':
$ref: '#/components/responses/Unauthorized'
/v1/vc/issuer/store:
post:
operationId: storeIssuerCredential
summary: Store an issued verifiable credential
tags:
- VC V1
responses:
'200':
description: Credential stored
'401':
$ref: '#/components/responses/Unauthorized'
components:
responses:
Unauthorized:
description: Authentication is missing or invalid.
securitySchemes:
bearerAuth:
type: http
scheme: bearer
bearerFormat: JWT
description: Bearer access token (default authentication for the T3 API).
apiKeyAuth:
type: apiKey
in: header
name: x-api-token
description: API token required on specific endpoints (e.g. user creation). Contact enterprise@terminal3.io to obtain a key.