Migrating from v1
v1 of the Flxpoint API is retired. If your integration still targets v1, plan your move now — these pages show the v2 equivalents.
High-level changes
- Base URL.
api.flxpoint.com/v1→api.flxpoint.com(no version prefix). Just remove the/v1from your URLs. - Auth header. The header name changed to
X-API-TOKEN. v2 authenticates only with that custom header — notAuthorization: Bearer, and not HTTP Basic Auth (which some v1 integrations used). Basic Auth is not supported on the current API. - Purchase Orders.
POST /purchase-ordersis replaced byPOST /fulfillment-requests. The semantic shifted — fulfillment requests are routed-and-actionable, purchase orders were inventory-side bookkeeping. - Inventory.
POST /inventory(create-or-update) is replaced byPATCH /inventory/variants. The v2 endpoint is variant- aware and batches up to 50 variants per call.
v1 → v2 quick map
| v1 | v2 | Notes |
|---|---|---|
| HTTP Basic Auth / v1 header | X-API-TOKEN header | No Basic Auth in v2; the token type (Account / Source / Channel) decides scope. |
api.flxpoint.com/v1/… | api.flxpoint.com/… | Drop the /v1 prefix. |
POST /purchase-orders | POST /fulfillment-requests | FRs are routed and actionable; POs were inventory-side bookkeeping. |
POST /inventory (create-or-update) | PATCH /inventory/variants | Variant-aware; batches up to 50 variants per call. |
Don't build new integrations on Purchase Orders. The entire Purchase Order resource is deprecated in v2 — every operation is flagged deprecated in the reference. Use Fulfillment Requests for anything you would have done with a purchase order.
For the per-endpoint mapping, browse the API reference— deprecated endpoints are flagged and link to their replacement. If you're unsure which v2 endpoint matches a v1 call, the chatbot in the bottom-right knows the mapping — paste the v1 endpoint and it'll respond with the v2 equivalent and a sample request.