Sync Order Detail
POST/api/veracore/integration-instances/:integration_instance/orders/:order/sync-detail
Refresh a single Veracore order's stored data by fetching full order detail from the Veracore API. The fetched detail (status flags, shipping, line items, addresses) is merged into the locally stored order and the detail-refresh timestamp is updated.
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
Veracore reports status as a block of flags where several can be true at once; the most advanced flag becomes the order's current status (Canceled and Complete take precedence, then Shipped, and so on).
The call is synchronous — the Veracore API is contacted during the request and the refreshed order is returned.
Errors
404when the order does not exist or belongs to a different integration instance.422when the stored record has no Veracore order id to fetch by; run a full order sync first.502when the Veracore API call fails.
Authentication: Requires Bearer token.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
- 502
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.
Bad Gateway