Get access

Everything on the Builder Platform sits behind one OAuth 2.0 credential. There are two ways to get one, depending on what you are building.

Path 1: your own tools and automations (most customers)

For scripts, dashboards, scheduled jobs, and internal apps, you use a service credential tied to your MixShift account:

1. Ask us for access (get in touch) or, if your MixShift admin already has the admin page, they can mint one there directly.
2. A credential is a client_id and client_secret, shown once at mint time. Store it like any secret.
3. Exchange it for an access token whenever you need one. Service-credential tokens last 12 hours, so an unattended job that mints one at startup does not need to refresh mid-run:

curl -X POST https://mcp.mixshift.io/oauth/token \
  -d grant_type=client_credentials \
  -d client_id=YOUR_ID -d client_secret=YOUR_SECRET

4. Send Authorization: Bearer [token] on every call.

Credentials are read-only by default and scoped to exactly what they are allowed to see and do. Write permissions (retiring or restoring a brand, timeline events, advertising writes, listing writes) are granted explicitly at mint time and can be revoked or rotated any time.

If the credential is for the MixShift plugin or a scheduled task rather than your own code, there is an even simpler flow where a one-time setup code does the exchange for you and no human ever handles the secret. See Run unattended and scheduled tasks.

Path 2: partner software (apps acting for MixShift customers)

Building a product where MixShift customers sign in to your app? Email support@mixshift.io with your app name, redirect URIs, and the scopes you need. You get a registered client_id (plus a secret for confidential clients), and your users authorize through a standard consent screen using the authorization-code flow with PKCE. Partner API sessions last 12 hours, matching service credentials.

Trying it by hand

Want a token without writing code first? Open mcp.mixshift.io/login?mode=direct in a browser, sign in, and copy a token to experiment with.

Next

• Query the warehouse for your first real call.
• Connect AI tools over MCP if the "app" is ChatGPT, Cursor, or Codex.