Authentication
The TokenOS API uses API keys to authenticate requests. You can view and manage your API keys in the TokenOS Dashboard.
Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth.
Authentication to the API is performed via HTTP basic auth, HTTP body auth, or JWT bearer auth. All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.
Basic Auth
For HTTP basic auth, the client sends its client ID and client secret as part of the authorization header in an HTTP request. The Authorization header contains a Base-64 encoded string of {URL-encoded-client-ID}:{URL-encoded-client-secret}.
JWT Bearer Auth
For JWT bearer auth, this method is similar to basic and body authentication, but instead of sending the client ID and client secret, the client sends a JSON Web Token (JWT) which was signed by its cryptographic key.
Enhanced Security Authentication
For clients requiring enhanced security, we do offer
Last updated