find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/terminal-3-sub-client-v1-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Terminal 3 DID V1 Sub Client 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: Sub Client V1
  description: Manage sub-clients under a Terminal 3 tenant.
paths:
  /v1/sub_client:
    get:
      operationId: listSubClients
      summary: List sub-clients
      tags:
      - Sub Client V1
      responses:
        '200':
          description: Success
        '401':
          $ref: '#/components/responses/Unauthorized'
    post:
      operationId: createSubClient
      summary: Create a sub-client
      tags:
      - Sub Client V1
      responses:
        '200':
          description: Sub-client created
        '401':
          $ref: '#/components/responses/Unauthorized'
  /v1/sub_client/{subclient_id}:
    parameters:
    - name: subclient_id
      in: path
      required: true
      schema:
        type: string
    get:
      operationId: getSubClient
      summary: Get a sub-client
      tags:
      - Sub Client V1
      responses:
        '200':
          description: Success
        '404':
          $ref: '#/components/responses/NotFound'
    put:
      operationId: updateSubClient
      summary: Update a sub-client
      tags:
      - Sub Client V1
      responses:
        '200':
          description: Sub-client updated
        '404':
          $ref: '#/components/responses/NotFound'
    delete:
      operationId: deleteSubClient
      summary: Delete a sub-client
      tags:
      - Sub Client V1
      responses:
        '200':
          description: Sub-client deleted
        '404':
          $ref: '#/components/responses/NotFound'
components:
  responses:
    Unauthorized:
      description: Authentication is missing or invalid.
    NotFound:
      description: The requested resource was not found.
  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.