HTTP API

The Order Change API allows partner systems to read order details, check edit eligibility, and apply changes on behalf of merchants. All edits respect the merchant's configured settings — edit window, enabled capabilities, and plan limits.

API requests require authentication via API key or OAuth2. The API supports both ApiKeyAuth and OAuth2 schemes. Authentication credentials are issued per merchant and scoped to a single Shopify store.

Contact support@orderchange.com for API credentials and integration assistance.

Order Change offers two tiers. The capabilities available through the API match the merchant's plan:

API requests to Pro-only endpoints return a 403 error if the merchant is on the Free plan. Check eligibility first using the GET /orders/:id/eligibility endpoint.

Most mutation endpoints follow a two-phase pattern: preview the change, then commit it.

1. Preview — Validate the change without applying it. Returns what the order would look like after the edit, including any recalculated totals or shipping costs.
2. Commit — Apply the previewed change. Must be called within the merchant's configured edit window.

This pattern ensures that customers and partners see exactly what will happen before the order is modified.

Read endpoints are scoped per order: /v1/stores/:store_id/orders/:order_id/...

Mutation endpoints use the custom method pattern: /v1/stores/:store_id/edits/resource:action

The API returns standard HTTP status codes. Error responses include a JSON body with details:

{
  "error": {
    "code": "edit_window_closed",
    "message": "This order's edit window has expired.",
    "details": {
      "window_closed_at": "2026-09-20T14:30:00Z"
    }
  }
}

Rate limits are applied per merchant and may vary by plan. For current rate limits, quota increases, or custom integration needs, contact support@orderchange.com.