Skip to main content
An OAuth client lets a server exchange a signed JWT assertion for a short-lived access token instead of holding a long-lived API key. Sixtyfour verifies the assertion against a public key you upload or publish at a JWKS URL; there is no client secret. Organization admins and owners manage OAuth clients. See Roles and Permissions.

Open OAuth Clients

Open OAuth Clients settings. OAuth Clients settings page

Create a client

  1. Click Create client
  2. Enter a Client Name (for example, my-production-app)
  3. Optionally enter a JWKS URL: a public HTTPS endpoint that serves your JSON Web Key Set
Provide a JWKS URL for automatic key rotation, or leave it blank to upload public keys. You can’t change this after creation.
  1. Click Create and continue
Sixtyfour generates a client_id and opens the client’s detail page.

Register a public key

Pick the flow that matches how you created the client.

With a JWKS URL

If you configured a JWKS URL, Sixtyfour fetches your public keys from that endpoint automatically. Validate it at any time:
  1. On the client detail page, click Validate JWKS
  2. Confirm the health indicator shows a green check and a recent validation timestamp

With an uploaded public key

If you did not set a JWKS URL, generate an RSA key pair and upload the public half:
  1. Click Upload key
  2. Paste the contents of public.pem into Public Key (PEM) (including the -----BEGIN PUBLIC KEY----- and -----END PUBLIC KEY----- lines)
  3. Click Upload key
Copy the generated Key ID (kid). It goes in the JWT header.
Keep private.pem on the server that signs assertions. Never commit it or send it to a browser.

Request an access token

Your server signs a short-lived JWT assertion with the private key, then POSTs it to the token endpoint.
The response contains a bearer token:
The access token is an opaque string that starts with s4at_. Send it as is; do not parse it. Reuse it until shortly before expires_in runs out instead of requesting a new one per call: POST /oauth/token is rate limited.

Assertion rules

  • Sign with RS256 and put a registered key’s kid in the header. Assertions with a jku, x5u, or x5c header are refused.
  • Set iss and sub to your client_id, and aud to the discovery document’s issuer, https://api.sixtyfour.ai.
  • Set iat and exp as integers. An assertion can live at most 300 seconds (exp - iat), and Sixtyfour allows 60 seconds of clock skew.
  • Use a new jti for every assertion; each assertion works once.
Token errors use the OAuth format, {"error": "...", "error_description": "..."}. See OAuth token errors.

Call the API

Send the token in the Authorization header on any Sixtyfour API request:
OAuth access tokens work on every endpoint that accepts x-api-key. When a request sends both, the API uses the token. See Authentication. An OAuth client acts for your organization’s default team. Its tokens see only that team’s workflows, runs and monitors, and count toward that team’s monthly credit limit.

Managing a client

Adjust token TTL

Token TTL sets how long issued access tokens stay valid: the default (1 hour), 1 minute, 5 minutes, 1 hour or 24 hours. The token response’s expires_in reflects the setting.

Rotate keys

If you configured a JWKS URL, publish the new key in your JWKS document and click Validate JWKS. Sixtyfour can take up to 5 minutes to accept the new kid, so keep signing with the old key until then. If you uploaded a public key directly, upload the new key, switch your signer to the new kid, then revoke the old key from the Public Keys table.

Permanently disable a client

Disable, then Disable permanently, invalidates every outstanding token at once. A disabled client can’t be re-enabled; create a new client to restore access.

Delete a client

Click the trash icon on the detail page, then Delete client. Deleting revokes all tokens and keys for that client and cannot be undone.