For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
LoginSandbox
Platform GuidesAPI DocsSDKMCP ServerChangelog
Platform GuidesAPI DocsSDKMCP ServerChangelog
  • Getting started
    • Introduction
    • Concepts
    • Onboarding guide
  • Use cases
    • Monetizing an AI agent
    • Pricing models for AI products
    • Configuring entitlements for AI products
  • Usage metering & events
    • Meters
    • Usage events
    • Unmatched events
    • Event reprocessing
  • Products & plans
    • Product Catalog
    • Pricing Plans
    • Features & Entitlements
  • Wallets & credits
    • Credit types & wallets
    • Credits in pricing plans
  • Customers & subscriptions
    • Customers
    • Subscriptions
    • Quotes
  • Invoicing
    • Invoices
    • Invoice corrections
    • Payment Collections
    • Tax
    • Currencies & Exchange rates
    • E-invoicing
  • Analytics & reporting
    • Insights
    • Report downloads
    • Revenue Recognition & Deferred Revenue
  • Integrations
    • CRM
    • ERP
    • Email Providers
    • Data Imports: Event File Uploads
    • Data Exports
    • Payment Service Providers
  • Settings & admin
    • Billing entities
    • Payment Options
    • User management
    • Customising invoices
    • Custom fields
    • Default platform settings
    • API key creation
    • Alert Rules
    • Workflows
  • Workflows
    • Workflow Triggers
    • Workflow Actions
    • Monitoring and Audit
    • Common Use Cases
  • For developers
    • Introduction
    • Authentication
    • Local development setup
    • API
    • Errors
    • Troubleshooting
    • Query Parameters
    • Expanding Responses
    • Idempotency
    • Timestamp formatting
    • Webhooks
    • Locale
    • MCP Server
LoginSandbox
On this page
  • HTTP response codes
  • Errors
  • List of error codes
For developers

Errors

Was this page helpful?
Previous

Troubleshooting

Next
Built with

HTTP response codes

Solvimon uses conventional HTTP response codes to indicate the success or failure of an API request.

  1. Codes in the 2xx range indicate success. Generally, you will get either a 201 or 200, the former for when a resource is created, the latter when fetching information.
  2. Codes in the 4xx range indicate an error that failed given the information provided. Some 4xx errors that could be handled programmatically include an error code briefly explaining the reported error.
  3. Codes in the 5xx range indicate an error with Solvimon’s servers (these are rare).

Our API responses hold a unique request reference in the header field: X-REQUEST-ID, that holds a value of the following format:reqr_HwDeRw0dFUrJrjCKk31w. It is advised to provide this reference for troubleshooting.


Errors

An error response consists of the following fields:

  1. type: possible values are: API_ERROR and INVALID_REQUEST. The latter will indicate a failure on the request submitted being invalid, the former is where processing failed due to internal issues or other non-recoverable problems
  2. code: programmatic value to indicate what failed, e.g. RESOURCE_NOT_FOUND or UNABLE_TO_PROCESS_INSTRUCTIONS. Below is a list provided for all the existing codes.
  3. field (optional): indicates which field was deemed invalid
  4. message: a human-readable explanation of the response

An example of such a response would be:

1{
2 "type": "INVALID_REQUEST",
3 "code": "INVALID_FIELD",
4 "field": "schedules.0.included_volumes.0.number",
5 "message": "value required, but not set"
6}


List of error codes

A list of the existing error codes that can be within the field code.

Error CodeDescription
RESOURCE_NOT_FOUNDThe requested resource is not found
RESOURCES_NOT_FOUNDThe requested resources are not found
UNABLE_TO_PROCESS_INSTRUCTIONSThe payload of the request can not be processed
UNSUPPORTED_MEDIA_TYPEThe Content-Type of the request is not set or is incorrect
RESOURCE_ALREADY_EXISTSThere is an existing resource with the provided identifier
COULD_NOT_CREATE_RESOURCEThe resource could not be created
COULD_NOT_UPDATE_RESOURCEThe resource could not be updated
COULD_NOT_DELETE_RESOURCEThe resource could not be deleted
MISSING_VERSIONThe version in the path is missing
UNSUPPORTED_VERSIONThe version in the path is not supported
MISSING_IDThe id is missing from the path
INVALID_IDThe id from the path is not valid
MISSING_REFERENCEThe reference is missing from the request
MISSING_FIELDA mandatory field is missing from the request
INVALID_FIELDA field from the request is not valid
INTERNAL_ERRORAn internal error has occurred
UNAUTHORISEDThe credentials provided are invalid
USER_NOT_ALLOWEDThe user has no permission to make the request