Machine-to-machine clients
Issue OAuth client-credentials tokens to your own services and your customers' integrations.
A machine client (mcli_…) gets access tokens for a service, not a person, with the OAuth 2.0 client credentials grant.
Create a client
Section titled “Create a client”POST /v1/m2m_clients with a name, one or more audiences (the APIs its tokens are for), optional scopes, an optional organization to limit it to one customer, and access_token_seconds (60 to 3600, default 600). The answer contains the client_secret once. Scope: machine_clients:write.
Clients authenticate with either:
client_secret, in the body or with HTTP Basic, never both; orprivate_key_jwt: a signed assertion checked against the 1 to 10 public keys you register (RS256,PS256,ES256orEdDSA). The assertion’sissandsubare the client ID,audnames the token endpoint, it expires within 5 minutes and eachjtiworks once.
Get a token
Section titled “Get a token”POST https: with grant_type=client_credentials, the client’s credentials and optionally resource (one of its audiences) and scope. The token is an RFC 9068 JWT (typ: at+jwt) with iss, aud (exactly one audience), sub and client_id (the client ID), scope, jti, env and, for organization clients, org_id. There is no refresh token; ask for a new one.
Rotate and revoke
Section titled “Rotate and revoke”POST /returns a new secret; withv1/ m2m_clients/ {client}/ rotate_secret keep_previous, the old one keeps working for 24 hours.DELETE /revokes the client; its next token request fails.v1/ m2m_clients/ {client}
Each client may request 10 tokens a second (bursts of 50). Secrets never appear in logs, audit entries, events or error messages.