Skip to main content
The SOLO Network API uses standard HTTP status codes and returns structured JSON error responses.

​
Error Response Format

All error responses follow a consistent structure: 
{
  "detail": "A human-readable description of what went wrong"
}
For validation errors, the detail includes the field path: 
{
  "detail": "body -> consumer_first_name: field required"
}

​
Status Codes

​
Success

CodeDescription
200 OKRequest succeeded. Response body contains the requested data.

​
Client Errors

CodeDescription
401 UnauthorizedNo token provided, or the token is malformed or expired.
403 ForbiddenToken is valid but lacks the required permission scopes.
404 Not FoundThe requested resource does not exist.
422 Unprocessable EntityRequest body failed validation. Check the detail field for the specific field and error.

​
Server Errors

CodeDescription
500 Internal Server ErrorAn unexpected error occurred. These are logged and monitored automatically.

​
Common Error Scenarios

Status: 401 Unauthorized
{ "detail": "Requires authentication" }
Ensure your Authorization header is set to Bearer <token> with a valid, non-expired token.
Status: 403 Forbidden
{ "detail": "Not enough permissions" }
Your token doesn’t include the required scopes for this endpoint. Contact your SOLO account manager to update your token permissions.
Status: 422 Unprocessable Entity
{ "detail": "body -> consumer_date_of_birth: value is not a valid date" }
Check the field mentioned in the error detail. The API Reference documents the expected types and formats for each field.
Status: 401 Unauthorized
{ "detail": "Could not validate credentials or find account" }
Your token is valid but the associated account or stakeholder doesn’t exist in the system. This typically occurs during initial setup — contact SOLO support.

​
Rate Limiting

The API does not currently enforce rate limits. However, we recommend keeping request volume reasonable and using bulk data ingestion for high-volume operations.