Unter uses API key authentication to secure merchant API endpoints. Each API key is associated with a specific merchant account and can be configured with different permissions and rate limits.
API Key Format
All Unter API keys follow this format:
unter_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Keys always start with the prefix unter_
Followed by 40 random characters
Total length: 46 characters
Authentication Methods
You can authenticate API requests using either of these methods:
Alternatively, you can use the Authorization header as a Bearer token:
Security Features
Key Hashing and Security
When an API key is generated, you'll see the full key (e.g., unter_abc123...) displayed once in your dashboard. This is the only time you'll be able to see the complete key, so make sure to copy and store it securely.
Error Responses
Missing API Key
Status Code: 401 Unauthorized
Invalid API Key
Status Code: 401 Unauthorized
Suspended Account
Status Code: 403 Forbidden
Environments
API keys can be created for different environments:
production - For live payment processing (default)
sandbox - For testing and development
Make sure to use the appropriate key for your environment.