Errors and troubleshooting
Error responses
| HTTP | Meaning |
|---|---|
401 | Missing, invalid, expired or revoked token, or a token issued for a different tenant or environment. |
403 | The token lacks the required scope, the Partner API is not enabled for your tenant, or the action is not allowed for this record. |
404 | Unknown id, an id under the wrong parent in the URL, or a write to a soft-deleted record. |
405 | The resource does not support this method (read-only resources). |
409 / 423 | The change conflicts with the record's current state, or the record is locked (documented on the operations that can return them). |
422 | Validation failed. errors is a list of { "field": "…", "message": "…" }. |
429 | Rate limit exceeded. |
Application errors use the envelope with success: false. 405, 429 and unknown paths return a plain { "message": "…" } body instead. Token endpoint errors follow OAuth 2.0 ({ "error": "invalid_client" } and similar).
Troubleshooting
| Symptom | Likely cause |
|---|---|
403 on every call, even with a fresh token | The Partner API may not be enabled for your tenant yet — contact Eventogy. |
401 immediately after a successful token fetch | Calling the wrong tenant host, or the credential was revoked. Confirm the host matches the tenant your credential was issued for. |
{"error":"invalid_client"} at the token endpoint | Wrong client ID/secret, or the credential belongs to a different tenant. |
{"error":"invalid_scope"} at the token endpoint | Requested a scope that doesn't exist — only partners:read and partners:write are valid. |
A write returns 403 but reads work | Your credential doesn't hold partners:write (see the scope caveat under Conventions). |
401 after ~1 hour of working | Token expired — request a new one. |