Terminal 3

Terminal 3 OpenID Connect V1 API

OpenID Connect authorization, token, userinfo, and credential operations (v1).

GitHub OpenAPI

Operations 6

GET /v1/openidc/authorize OpenID Connect authorization endpoint #
GET /v1/openidc/credentials Get OpenID Connect credentials #
POST /v1/openidc/credentials/proof Create a proof for OpenID Connect credentials #
POST /v1/openidc/token OpenID Connect token endpoint (v1) #
GET /v1/openidc/user OpenID Connect userinfo endpoint (v1) #
GET /v1/openidc/user/social_connections Get a user's social connections #

Documentation

📖
APIReference
https://docs.terminal3.io/api-reference/t3-api/getting-started

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/terminal-3/refs/heads/main/openapi/terminal-3-openid-connect-v1-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • 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-openid-connect-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

terminal-3-openid-connect-v1-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Terminal 3 DID V1 OpenID Connect 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: OpenID Connect V1
  description: OpenID Connect authorization, token, userinfo, and credential operations (v1).
paths:
  /v1/openidc/authorize:
    get:
      operationId: openidcAuthorize
      summary: OpenID Connect authorization endpoint
      tags:
      - OpenID Connect V1
      responses:
        '200':
          description: Success
        '302':
          description: Redirect to client with authorization response
  /v1/openidc/credentials:
    get:
      operationId: getOpenidcCredentials
      summary: Get OpenID Connect credentials
      tags:
      - OpenID Connect V1
      responses:
        '200':
          description: Success
        '401':
          $ref: '#/components/responses/Unauthorized'
  /v1/openidc/credentials/proof:
    post:
      operationId: createOpenidcCredentialsProof
      summary: Create a proof for OpenID Connect credentials
      tags:
      - OpenID Connect V1
      responses:
        '200':
          description: Proof created
        '401':
          $ref: '#/components/responses/Unauthorized'
  /v1/openidc/token:
    post:
      operationId: createOpenidcToken
      summary: OpenID Connect token endpoint (v1)
      tags:
      - OpenID Connect V1
      responses:
        '200':
          description: Token issued
        '400':
          $ref: '#/components/responses/BadRequest'
  /v1/openidc/user:
    get:
      operationId: getOpenidcUser
      summary: OpenID Connect userinfo endpoint (v1)
      tags:
      - OpenID Connect V1
      responses:
        '200':
          description: Success
        '401':
          $ref: '#/components/responses/Unauthorized'
  /v1/openidc/user/social_connections:
    get:
      operationId: getOpenidcUserSocialConnections
      summary: Get a user's social connections
      tags:
      - OpenID Connect V1
      responses:
        '200':
          description: Success
        '401':
          $ref: '#/components/responses/Unauthorized'
components:
  responses:
    BadRequest:
      description: The request was malformed.
    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.