ENTERPRISE API · VERSION 1
Useful services. One integration.
Connect your business systems to Nexora's sales reporting and support triage services.
Authenticate
Ask your Nexora administrator for a scoped customer API key. Pass it in the request header. Keep keys in your server environment, outside source code and URLs.
Authorization: Bearer YOUR_CUSTOMER_API_KEY Content-Type: application/json
Available scopes: usage:read, sales:analyze, and support:triage. Administrator credentials only manage accounts and keys.
Business services
Quotas & errors
Accounts share one allowance across their keys. A validated, admitted service request uses one processing unit. AI mode also uses one AI unit, including attempts where the provider later fails. Account lookups do not consume monthly processing units but count toward minute limits. Usage periods reset on UTC calendar months.
| Status | Meaning | Next step |
|---|---|---|
| 400 / 413 / 415 | Invalid input, oversized body, or wrong content type | Correct the request before retrying. |
| 401 | Missing, expired, revoked, or invalid credential | Ask the administrator for a valid key. |
| 403 | Scope, account status, or browser-origin restriction | Check key scopes and account access. |
| 429 | Minute or monthly allowance reached | Respect Retry-After for minute limits; review the plan for monthly limits. |
| 502 / 504 | AI provider failed, returned invalid output, or timed out | Use human review; automatic retries can consume additional units. |
| 503 | Provider unconfigured or service unavailable | Check configuration or contact Nexora. |
Processing responses include X-Request-ID, minute-limit headers, and monthly quota headers after admission. API errors include a correlation ID:
{
"error": {
"code": "insufficient_scope",
"message": "This key requires the sales:analyze scope.",
"request_id": "correlation-id"
}
}Data handling
Sales transactions and ticket content are not stored in the application database. AI mode sends ticket text to the configured AI provider. All classifications and response drafts require human review. Application request logs store metadata and are retained for 30 days; aggregate monthly counters remain available.
This starter supports one administrator token and manually assigned customer plans. Payment collection, SSO, and automatic subscriptions are not enabled.