Vero OMS API

Quick checklist

Check method and path

Compare your request against the endpoint definition provided for your integration.

Check credentials

For 401, verify the bearer JWT or X-Session-Token expected by the endpoint.

Check time format

Use ISO 8601 UTC timestamps with a Z suffix when sending date-time parameters.

Check response status

Use the status code and response body to identify the failing validation rule.

Symptom	Common cause	Fix
`400 Invalid query parameter`	Missing required parameter or invalid time format	Check required params and use UTC `Z` timestamps
`401 Unauthorized`	Missing or invalid credential	Check bearer JWT or `X-Session-Token`
`404 Not found`	Resource ID or path does not exist	Verify the requested resource
`422 Unprocessable`	Correct format but unsupported value	Check documented enum values and constraints
`429 Too many requests`	Request limit exceeded	Reduce request rate and retry later
`503 Unavailable`	API temporarily unavailable	Retry with backoff

Valid	Invalid
`2026-05-15T00:00:00Z`	`2026-05-15 00:00:00`
`2026-05-15T00:00:00.123Z`	`2026-05-15T07:00:00+07:00`

Information	Example
Endpoint	Method and path being called
Query params	Request query string or JSON body
HTTP status	`400`, `401`, `404`, `429`, `503`
Response body	JSON response or error body
Request time	UTC timestamp