Building a product that connects other SideShift companies? Use the OAuth
quickstart instead.
Before you start
You need a SideShift company with an active subscription and owner/admin access (or API credential management permission). Keep the key on a trusted server; never put it in browser JavaScript, a mobile app, source control, or logs.1. Create a scoped key
Open Settings → OAuth & MCP → API keys and click Create key.- Name the workload, such as
Internal reporting dashboard. - Choose Live. Use Test only for sandbox behavior; money-moving and external-side-effect writes are blocked.
- Select only the scopes it needs. Choose
campaigns:readfor this guide. - Click Create key, then copy it immediately.
2. Make your first request
Every current Platform resource endpoint supports the key throughx-api-key:
data array is successful when the company has no campaigns.
3. Use the full Platform API
The key works on the same/api/oauth/v1/* resource operations as an OAuth access token.
The selected scopes decide which operations it can call. For example:
Open an operation in the Platform API reference to see its required scope.
Send either
x-api-key or Authorization: Bearer … on a request, never both.
For POST, PUT, and PATCH requests, send an Idempotency-Key. It is required on money-moving
operations and prevents a retry from running the same change twice.
Rotate or revoke a key
Keys cannot be recovered or expanded after creation. To rotate without downtime:- Create a second key with the required scopes.
- Deploy the new key and verify a request succeeds.
- Revoke the old key.
Common errors
Every resource error includes a
requestId; include it when contacting SideShift support.
Platform API reference
Find current endpoints and the scope required for each operation.
Build for other users
Use OAuth 2.1 with PKCE when another company grants your app access.