Developer API/Errors and versioning
Errors and versioning
Error envelopes, status codes, compatibility, and deprecation.
All REST errors share one envelope:
{
"error": {
"code": "not_found",
"message": "The requested resource was not found in this organisation.",
"requestId": "019c..."
}
}Include requestId when contacting support.
| Status | Meaning |
|---|---|
401 | The API key is missing, invalid, expired, revoked, or lacks permission. |
404 | The resource does not exist or does not belong to the key's organisation. |
429 | The key exceeded its rate limit. |
500 | Strave could not safely complete the operation. |
Resources outside the key's organisation also return 404.
Versioning policy
The major API version is part of the base URL. Within v1, integrations must
tolerate:
- new endpoints;
- new optional response fields;
- new gateway event types;
- new enum values.
Do not reject an entire response only because it contains an unknown optional field. Removing or renaming a field, changing its type, or changing established semantics requires a new major version.