Preview Source Code for Sales Order

GET 
/api/veracore/integration-instances/:integration_instance/source-code-mappings/preview

Preview which Veracore source code would be applied to a given sales order under the current mappings. This is a read-only computation — nothing is stored and no call is made to the Veracore API.

Authorization

Any valid API token can call this endpoint — no specific scope required. Manage tokens.

Resolution order:

1. A mapping matching the order's sales channel and sub sales channel (matched_type: "sub_channel").
2. The sales channel's catch-all mapping with no sub channel (matched_type: "catch_all").
3. No match — source_code and matched_type are null.

The response also includes the sales channel and sub channel context used for resolution so you can see why a mapping did or did not match.

Errors

• 404 when no sales order exists with the given sales_order_id, or the integration instance does not exist.

Authentication: Requires Bearer token.

Request

Responses

200

OK

Response Headers

Content-Type

401

Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.

403

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.

404

Not Found

Response Headers

Content-Type

429

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.