The Nexgent Public API uses API key-based authentication to authenticate and authorize API requests. Every request you make must include a valid API key in the request headers.
All API requests must be made over HTTPS. Requests without authentication, or using invalid credentials, will return a 401 Unauthorized
error.
Include your API key in the Authorization
header using the Bearer schema in every API request:
Authorization: Bearer {api_key}
Replace {api_key}
with your actual API key value.
Example:
Authorization: Bearer zpka_xxx123exampleapikey
You can generate and manage your API keys in the Integrations section of the Nexgent Portal under Agent Configuration.
Example: If you have 3 API keys, all API traffic from those keys counts toward your monthly and rate limit quotas.
If authentication fails, the API will return a 401 Unauthorized
error.
Example error response:
{
"error": {
"message": "Invalid API Key provided.",
"type": "authentication_error"
}
}
Ensure that your API key is included correctly in the Authorization
header, and that it is active and valid.
Requirement | Details |
---|---|
Authentication | API Key via Authorization: Bearer {api_key} header |
API Key Limit | Up to 10 active API keys per user |
Quota Enforcement | Quotas are linked to the user, not to individual keys |
Rotation | API keys can be created, revoked, and rotated anytime |
For additional help with API keys, quotas, or security best practices, contact Nexgent support.