Terminal 3 Sub Client V1 API
Manage sub-clients under a Terminal 3 tenant.
Terminal 3 Sub Client V1 API is one of 7 APIs that Terminal 3 publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Sub Client V1. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.
This API exposes 5 operations across 2 paths. It is described by OpenAPI 3.0.3, at version 1.0.
Requests are made against a single base URL, https://staging.terminal3.io.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Terminal 3 Sub Client V1 API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (bearerAuth).
An API key is passed in the header as x-api-token (apiKeyAuth).
By default, every request must be authenticated.
bearerAuth— Bearer access token (default authentication for the T3 API).apiKeyAuth— API token required on specific endpoints (e.g. user creation). Contact enterprise@terminal3.io to obtain a key.
Paths & Operations 5
Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Manage sub-clients under a Terminal 3 tenant.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Terminal 3 6
Other APIs Terminal 3 publishes across the network.