Authentication | Sweet Spot API Documentation

The Sweet Spot API uses Bearer token authentication. All API requests must include a valid authentication token in the Authorization header. You can obtain API tokens from your organization's settings in the Dashboard.

Your API tokens carry many privileges, so be sure to keep them secure! Don't share your secret API tokens in publicly accessible areas such as GitHub, client-side code, and so forth. Treat your API tokens like passwords.

Bearer Token Authentication

All API requests must include an Authorization header with a Bearer token. The token format is: Bearer YOUR_TOKEN

API Token Scopes

API tokens can be configured with specific scopes and roles, allowing you to limit access to particular resources and actions. This provides granular control over what each token can do within your organization.

Token Expiration

API tokens can have optional expiration dates. Expired tokens will be rejected. You can manage token expiration and rotation in your organization's API token settings.

Warning: All API requests must be made over HTTPS. API requests made over plain HTTP will fail. API requests without authentication will also fail.

AUTHENTICATED REQUEST

cURL

curl https://api.thesweetspot.com/v1/products \
  -H "Authorization: Bearer sk_test_YOUR_API_KEY_HERE"

YOUR API TOKEN

Your API tokens authenticate your requests. You can create and manage API tokens in your organization's settings. Each token can be configured with specific scopes and permissions.