Migrating from V1 to V3
Every V1 endpoint mapped to its V3 status — what to migrate now and what stays on V1.
V3 is the strategic version of the Core API and covers most V1 functionality with richer capabilities (customers, variants, collections, fulfillments, webhooks). This page maps every V1 endpoint to its V3 status so you can migrate with confidence — and know exactly where to stay on V1 for now.
V1 is not being switched off. No endpoint will be removed while this page marks it "keep using V1", and any future retirement will be announced in the Changelog well in advance.
Authentication
| V1 endpoint | What to do |
|---|---|
| Yotpo authentication | Use yotpo-authentication |
Orders
| V1 endpoint | What to do |
|---|---|
| Create order | Use create-order |
| Create mass orders | V3 approach differs — see send-aggregated-order-info |
| Retrieve orders | Use retrieve-orders |
| Invalidate order | Migration guidance coming soon |
Products
| V1 endpoint | What to do |
|---|---|
| Create mass products | V3 approach differs — see create-product |
| Retrieve all products | Use retrieve-products |
| Retrieve Promoted Products | Keep using V1 — no V3 equivalent yet |
| Update mass products | V3 approach differs — see update-product |
Product Grouping
| V1 endpoint | What to do |
|---|---|
| Create product group | Migration guidance coming soon |
| Retrieve product groups for account | Migration guidance coming soon |
| Retrieve details for a specific product group | Migration guidance coming soon |
| Add/remove products in group | Migration guidance coming soon |
Updated 2 months ago
Did this page help you?