Skip to main content

Clear Shipping Method Mapping

DELETE 

/api/shiphero/integration-instances/:integration_instance/shipping-methods/mappings

Forget the decision for one ShipHero value entirely, so it falls back to the text rules and automatic matching below it. Distinct from mapping it to null, which would still be a stored decision.

Not yet available to API tokens

This endpoint currently requires session authentication; Personal Access Token scope support is in progress.

Values are addressed by the (carrier, service) PAIR, not a row id: what ShipHero sends is derived from fulfillment history, so most values have no stored row until a decision is made about them.

Body fields:

  • carrier (required, string, max 191) - as ShipHero reports it, e.g. endicia
  • service (required but may be EMPTY, string, max 191) - ShipHero really does report a carrier with no service, and that is a distinct value

Authentication: Requires Bearer token.

Every endpoint in this folder returns the SAME full configuration payload (provider_methods, sku_methods, text_rules, summary).

Request

Responses

OK

Response Headers
    Content-Type