err:unkey:authentication:malformed
Example
What Happened?
This error occurs when your request includes authentication credentials, but they are not formatted correctly. The Unkey API expects API keys to be provided in a specific format in the Authorization header. Common causes include:- Missing the “Bearer” prefix before your API key
- Including extra spaces or characters
- Using incorrect casing (e.g., “bearer” instead of “Bearer”)
- Providing a malformed or truncated API key
How To Fix
To fix this error, ensure your Authorization header follows the correct format:- Use the correct format: Ensure your Authorization header follows the format
Bearer unkey_YOUR_API_KEY
- Check for extra spaces or characters: Make sure there are no invisible characters or line breaks
- Verify the API key format: Your Unkey API key should start with
unkey_
Common Mistakes
- Authorization header format: Must be exactly
Bearer unkey_YOUR_API_KEY
with a single space after “Bearer” - Incorrect casing: Using “bearer” instead of “Bearer”
- API key format: Your Unkey API key should start with
unkey_
and contain no spaces - Using wrong key type: Ensure you’re using a root key for management API calls
- Copying errors: Check for invisible characters or line breaks that might have been copied
- Extra characters: Including quotes or other characters around the API key
- Truncated keys: Accidentally cutting off part of the API key when copying
Related Errors
- err:unkey:authentication:missing - When no authentication credentials are provided
- err:unkey:authentication:key_not_found - When the provided API key doesn’t exist