API keys allow you to access your Passport account programmatically and integrate wallet passes into your applications. Each API key inherits the permissions of the user who created it, giving access to all of that user’s resources.Documentation Index
Fetch the complete documentation index at: https://docs.unblockedbrands.com/llms.txt
Use this file to discover all available pages before exploring further.
Creating an API key
You can create an API key by following these steps:Store your API key
Once your API key is created, make sure to copy and store it in a safe place. You won’t be able to see it again for security reasons. If it gets lost, you can create a new one.

Example Usage
Include your API key in theapi-key header:
Example with a Real Request
Authentication Errors
If your API key is missing, invalid, or malformed, you’ll receive authentication errors:Missing API Key (401 Unauthorized)
Missing API Key (401 Unauthorized)
Invalid API Key (403 Forbidden)
Invalid API Key (403 Forbidden)
When an invalid or malformed API key is provided, you’ll receive a 403 Forbidden response indicating that access is denied.
The exact error message may vary depending on the endpoint.
Best Practices
Secure Storage
- Use environment variables in production
- Never commit API keys to version control
- Use different keys for development and production
- Rotate keys regularly for security
Rate Limiting
- API requests are rate limited to prevent abuse
- Include proper error handling for
429responses - Implement exponential backoff for retries
- Cache responses when possible
Environment Setup Examples
When you remove a user from your organization (or they leave your organization), all API keys associated with that user will stop working as well. Keep this in mind when managing users.

