API
Limits and errors
Where to find your current limits, and the error codes the API returns.
Not verified yet
Where to find your limits
Live current limits and usage are in app.norcube.com → LangSync → Limits. Free-tier allowances and paid-plan ceilings are listed on the pricing page.
What's rate-limited:
- Cost-driving endpoints – translation calls, auto-translate, AI recommendations.
- Public-API reads (per API key).
Exceeded requests return:
HTTP/1.1 429 Too Many Requests
Retry-After: <seconds>with the JSON body shape below.
Validation rules
| Field | Rule |
|---|---|
| Namespace name | URL-safe slug: letters, digits, hyphens, underscores. |
| Custom language code | Starts with a letter; lowercase letters, digits, hyphens, underscores. |
| Term mark | Non-empty, no leading/trailing whitespace. |
Validation failures return 400 INVALID_INPUT with a descriptive
message field.
Error codes
| HTTP | Code | Meaning |
|---|---|---|
| 400 | INVALID_INPUT | Validation failed. Check message. |
| 401 | INVALID_TOKEN | Token missing, malformed, or expired. |
| 401 | INVALID_API_KEY | API key revoked or unrecognised. |
| 403 | FORBIDDEN | Authenticated but not allowed. |
| 404 | NOT_FOUND | Resource doesn't exist. |
| 409 | CONFLICT | Resource already exists. |
| 422 | INVALID_STATE | Operation isn't valid in current state. |
| 429 | RATE_LIMITED | See Where to find your limits. |
| 500 | INTERNAL_ERROR | Unexpected server error. Retried with backoff. |
| 503 | SERVICE_UNAVAILABLE | Transient. Retry with exponential backoff. |
Error code names follow the platform-wide convention; exact codes per endpoint are visible in the Swagger UI.
Behaviour during platform incidents
Live status at status.norcube.com.