API referenceAPIAvailable
Authentication
Create API keys, authenticate requests, and understand scope-based access control for the Vendo API.
Last reviewed July 13, 2026
The Vendo REST API uses account-scoped API keys.
Each key belongs to a single account. Keys can be created with explicit scopes, and older keys without scopes continue to work with full account access for backwards compatibility.
Creating an API Key
- Go to Settings
- Open API Keys
- Click Create API Key
- Name the key for its purpose
- Choose scopes if you want to restrict access
- Copy the generated key immediately
The full key is only shown once.
API Key Format
vendo_sk_<random-string>Using Your API Key
Include the key as a bearer token:
curl -H "Authorization: Bearer YOUR_API_KEY" \
https://app2.vendodata.com/api/v1/appsScopes
API routes can require scopes such as:
apps.writesources.writeintegrations.writemodels.writejobs.write
If a route does not require a scope, any valid API key can access it.
If a key has no scopes stored on it, Vendo treats it as full-access for backwards compatibility.
Example Errors
Missing API key:
{
"error": {
"code": "UNAUTHORIZED",
"message": "Missing API key. Include Authorization: Bearer <your-api-key>"
}
}Invalid API key:
{
"error": {
"code": "UNAUTHORIZED",
"message": "Invalid API key. The key may be expired, revoked, or incorrect."
}
}Insufficient scopes:
{
"error": {
"code": "FORBIDDEN",
"message": "This API key does not have the required scopes: apps.write"
}
}Best Practices
- Use separate keys for production, staging, and local tooling.
- Prefer scoped keys for automation.
- Rotate keys regularly.
- Store keys in environment variables or a secrets manager.
- Revoke unused keys promptly.
Environment Variable Example
export VENDO_API_KEY="vendo_sk_your-key-here"
curl -H "Authorization: Bearer $VENDO_API_KEY" \
https://app2.vendodata.com/api/v1/meLast updated on