Models are listed once here and can also be expanded directly from the endpoints that use them.
Error contract
How application errors are returned
The error code is identical in every locale, while the user-facing message is translated by the server. Build application logic around error and use localMessage for display only.
error
Stable machine-readable code for integration logic.
localMessage
Display-ready message in the API token user's language.
params
Values interpolated by the server into the localized message template.
文
localMessage uses the lang field of the user who owns the API token. The documentation language and Accept-Language header do not change it; Russian is used when the user has no language configured.
RUUser locale is ru
{
"error": "error_brand_already_exists",
"localMessage": "Бренд Base уже существует",
"params": {
"name": "Base"
}
}
Application errors are normally returned as JSON with error, localMessage, and params. Branch on error; localized text may change. How application errors are returned ↑
401auth_required
Authentication required
Authorization is missing, empty, or contains an invalid token.
400error_access_denied
Insufficient permissions
The token exists, but its role cannot perform this operation.
500error_unknown
Unexpected error
Internal failure. Save the request time and contact support; do not blindly retry a mutation.
400error_no_client
The client was not found or has been deleted. Write to support
Endpoint-specific error. Use the stable error_no_client code in application logic; localMessage contains the translation shown above.
400error_order_not_found
Order not found
Endpoint-specific error. Use the stable error_order_not_found code in application logic; localMessage contains the translation shown above.
400error_storage_size_exceeded
You have exceeded the file storage size limit: {limit} MB
Endpoint-specific error. Use the stable error_storage_size_exceeded code in application logic; localMessage contains the translation shown above.