Map Shipping Method

PUT 
/api/veracore/integration-instances/:integration_instance/shipping-methods/map

Create or update the mapping from a Veracore carrier + service combination to a SKU.io shipping method.

Authorization

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

code is the combination identifier in the form Carrier|Service Description (e.g. UPS|UPS Ground), as returned by the shipping method list endpoint. Mapping the same code again replaces the previous target shipping method.

Errors

• 404 when the integration instance does not exist or is not a Veracore instance.
• 422 when code is missing/too long or shipping_method_id is not an existing shipping method.

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 — no record with the given identifier (or the route does not exist). Verify the ID before retrying.

422

Unprocessable Entity

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.