Create an API key in the dashboard
1
Open the Plans section
Log in to your SphereScout account and navigate to Dashboard → Plans.
2
Go to the API Keys tab
Select the API Keys tab within the Plans section. This page lists all existing keys on your account, showing each key’s prefix, creation date, and expiry date (if set).
3
Create a new key
Click Create API Key. Optionally set an expiry date if you want the key to auto-expire after a specific period. Leave the field blank to create a key with no expiry.
4
Copy and store the key securely
After creation, the dashboard displays the full API key once. Copy it immediately and store it in a secrets manager, environment variable, or another secure location. The dashboard will only show the key prefix (
token_key) from this point on — the full key cannot be retrieved again.Use an API key in requests
Pass your API key in theAuthorization header of every request using the Bearer scheme:
Manage keys via the API
You can also manage API keys programmatically using the key management endpoints. These endpoints require authentication with an existing API key or a valid JWT access token.List API keys
Retrieve all keys on your account. The response includes the key prefix (token_key), not the full key value.
string
required
Unique identifier for the API key. Use this ID to revoke the key.
string
required
The key prefix (first several characters). The full key value is not retrievable after creation.
string
required
ISO 8601 timestamp of when the key was created.
string | null
required
ISO 8601 expiry date, or
null if the key has no expiry.Create an API key
Send a POST request with an optionalexpiry field. If you omit expiry, the key has no expiry.
string
Optional ISO 8601 expiry date and time (e.g.
"2027-01-01T00:00:00Z"). Omit to create a key with no expiry.string
required
The full API key value. Store this immediately — it is only returned once.
object
required
Metadata about the newly created key.
Revoke an API key
Send a DELETE request with the key ID. Revocation is permanent and takes effect immediately. Any requests using the revoked key will receive a401 Unauthorized response.
204 No Content with no response body.