Skip to main content
Use a Platform API key when a script, scheduled job, backend service, or internal dashboard calls SideShift for your own company. It is the shortest setup: create one scoped key and send it with each request. There is no OAuth redirect, consent screen, or token exchange.
Building a product that connects other SideShift companies? Use the OAuth quickstart instead.
This guide uses a current sspk_… key with /api/oauth/v1. Older sk_live_… Platform keys call the deprecated /api/v1 API and must not be used for new work.

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.
  1. Name the workload, such as Internal reporting dashboard.
  2. Choose Live. Use Test only for sandbox behavior; money-moving and external-side-effect writes are blocked.
  3. Select only the scopes it needs. Choose campaigns:read for this guide.
  4. Click Create key, then copy it immediately.
The complete key is shown once. SideShift stores only its hash, so a lost key cannot be recovered—create a replacement and revoke the old one.

2. Make your first request

Every current Platform resource endpoint supports the key through x-api-key:
List endpoints return:
An empty 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:
  1. Create a second key with the required scopes.
  2. Deploy the new key and verify a request succeeds.
  3. Revoke the old key.
Revocation is immediate. Keep separate keys for separate workloads so you can rotate or revoke one integration without interrupting another.

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.