QUODD Authentication Token API
Token generation for trial and firm users. Exchanges username and password credentials for an access token that is appended to REST requests as the _token query parameter. Tokens expire after 24 hours and must be regenerated.
QUODD Authentication Token API is one of 10 APIs that QUODD publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Authentication, Tokens, and Security. The published artifact set on APIs.io includes an API reference, API documentation, and an OpenAPI specification.
This API exposes 2 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.0.3, at version 1.0.
Requests are made against a single base URL, https://api.quodd.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
QUODD Authentication Token API declares
1 security scheme
for authenticating requests.
An API key is passed in the query as _token (tokenQuery).
By default, every request must be authenticated.
tokenQuery— Access token obtained from the token endpoints (trial or firm user) and appended to each request as the token query parameter. Expires after 24 hours.
Paths & Operations 2
Across 2 paths, the API surfaces 2 operations — 2 POST. Each is listed below with its method, path, parameters, and response codes.
Token generation for trial and firm users.
Schemas 3
The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Credentials (2 properties), Error (2 properties), TokenResponse (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from QUODD 9
Other APIs QUODD publishes across the network.