Skip to main content
Every Paylead API call carries two things:
  1. A bearer access token in the Authorization header.
  2. The mandatory X-Api-Version header (see Versioning).
Why this matters. Leaked credentials grant access to your Program data. Treat your API client secret like a password: store it in a secret manager, and never commit it to source control.

​
How authentication works

Authentication is a two-step model. You hold long-lived client credentials and exchange them for short-lived access tokens.
1

Create an API client in Shift

In Shift, create an API client for your service. Shift returns a client_id and a client_secret (prefixed sk_…). The secret is shown once; copy it into your secret manager immediately.
2

Exchange the credentials for an access token

Call the token endpoint (POST /tokens) with your client_id and client_secret. Paylead returns a short-lived access token plus an expires_in (about an hour).
3

Call the API with the token

Send the access token as a bearer credential, together with the X-Api-Version header. Refresh the token by calling the token endpoint again before it expires.

​
Credentials vs. tokens

These are two different things; keep them straight:
Never send your client_secret on a regular API call. It is only ever used against the token endpoint to mint an access token.

​
Get your API client credentials

Create an API client in Shift (one per environment) under Settings > API Keys. Shift returns a client_id and a client_secret. For the full walkthrough (signing in, creating, viewing, and revoking clients) see API keys and Sign in to Shift.
The client_secret is shown exactly once. Copy it into your secret manager immediately. If you close the dialog without copying it, delete the client and create a new one.

​
Exchange credentials for an access token

Call the token endpoint with your client_id and client_secret. The response carries the access token and its lifetime (expires_in, in seconds).
Code examples coming soon. The Paylead API (v2) is still under construction. Request and response examples for this section will be published once the contract is finalized. In the meantime, contact your Paylead account manager for early-access details.
Cache the access token until shortly before expires_in elapses, then request a new one. Do not call the token endpoint on every API request.

​
Call the API

Pass the access token as a bearer credential and set the mandatory X-Api-Version header. All calls must use HTTPS.
Code examples coming soon. The Paylead API (v2) is still under construction. Request and response examples for this section will be published once the contract is finalized. In the meantime, contact your Paylead account manager for early-access details.
A call without a valid token returns 401 Unauthorized. A call missing the X-Api-Version header is rejected; see Versioning. See Errors for the full list.

​
Sandbox vs. production credentials

Sandbox and production credentials are separate. A sandbox client cannot mint tokens that work against production, and the reverse.
Use distinct secret-manager entries for each environment. Mixing them risks pointing your staging environment at production data.

​
Rotate credentials

Access tokens expire on their own (about an hour), so there is nothing to rotate there. What you protect and rotate is the client secret.
1

Create a new client

In Shift, create a new API client for the same environment. It returns a fresh client_id and client_secret.
2

Roll the new credentials to your service

Update the secret in your secret manager. Redeploy or hot-reload the services that read it, so they exchange the new secret at the token endpoint.
3

Verify traffic is on the new client

Watch your logs or Shift’s API activity panel. Confirm requests are succeeding with tokens minted from the new secret.
4

Revoke the old client

Delete the old client in Shift. It can no longer mint tokens, and tokens already issued from it expire within the hour.
Keep both clients active during rotation. Revoke the old one only after the new one is verified in production traffic. This avoids downtime if the rollout fails.

​
Security checklist

  • Store the client_secret in a secret manager (Vault, AWS Secrets Manager, GCP Secret Manager). Never in code, never in environment files committed to Git.
  • Restrict who can create API clients in Shift. Audit the Program Manager role.
  • Use a separate API client per service. If one service is compromised, you revoke one client, not all.
  • Never log the client_secret or the access token.
  • Log token usage on your side (request ID, timestamp). Correlate with Shift’s audit log if you suspect misuse.
If a client_secret leaks, delete that client in Shift immediately. Tokens it already issued expire within the hour. Then audit the previous 30 days of API activity for unexpected calls.

​
What’s next

Versioning

The mandatory X-Api-Version header and the version policy.

Rate limits

Per-token request limits and backoff strategy.

Errors

Diagnose 401, 403, and other auth-related failures.

Environments

Switch from sandbox to production safely.