Authentication

Authenticate a request

Use a SellRaze Platform API key in the Authorization header:

Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Create and manage keys in the API keys dashboard. A key authorizes requests for its owning platform account. All keys on an account draw from the same credit balance.

Create and store keys

1. Sign in to your platform account and open API keys.
2. Create a key with a descriptive name for your application or environment.
3. Copy the full secret before closing the creation dialog. You cannot retrieve it later.
4. Store it in your server’s environment or secret manager.

Do not embed API keys in a website, mobile application, public repository, or client-side environment variable. Send requests from your server.

Rotate or revoke a key

Create a new key, update your application’s secret, and verify your integration before revoking the old key. Revoking a key prevents it from authorizing new requests. Historical key metadata remains available.

If a key is exposed, revoke it in the dashboard and replace it. If you lose a key, create a replacement; the original secret cannot be shown again.

Platform and playground sign-in

The platform uses its own account system, separate from the SellRaze mobile app. Sign in with Google, GitHub, or an email sign-in link.

The playground uses your platform sign-in session to call Analyze. You do not need to create or select an API key to use it. Playground requests consume credits from the same account balance.

Use an API key for your server integration. Dashboard account, key, and billing operations use the signed-in platform session.

Authentication errors

An absent, invalid, or revoked credential returns 401 unauthorized. A valid credential does not override account eligibility: an account that cannot run analysis receives 403 account_ineligible.

See Handling errors for response formats and recovery steps.