EStore Tools

Legacy REST API Migration Mapper

Map an old /wc-api/v3/ call to its /wp-json/wc/v3/ equivalent, including what changes in auth and response shape.

Describe the result you need. AI will set up the tool and ask for any missing details.

Configure with AI

Enter to submit · Shift + Enter for a new line

Sent to AI. Leave out passwords and private customer data.

Your details

The current equivalent

legacy-api-mapping.txt
Legacy REST API (removed from WooCommerce core in version 9.0, June 2024):
  GET https://example.com/wc-api/v3/orders
  Auth: OAuth 1.0a over plain HTTP, or HTTP Basic (consumer key/secret) over HTTPS.
  Response: wrapped, e.g. { "orders": [ ... ] } for a collection.

Current WooCommerce REST API (v3, under the WordPress REST API):
  GET https://example.com/wp-json/wc/v3/orders
  Auth: HTTP Basic (consumer key as username, consumer secret as password) over HTTPS,
        or ?consumer_key=...&consumer_secret=... as a fallback.
  Response: unwrapped, a plain array for a collection or a plain object for one resource.

WooCommerce removed the Legacy REST API from core in version 9.0 (June 2024). A live call to /wc-api/ now 404s unless you install the community "WooCommerce Legacy REST API" extension as a stopgap while you migrate.

This mapping covers the common resources. Field names inside the response can differ slightly between the two APIs, check your integration's parsing code too, not just the URL.

Why this matters now

WooCommerce removed the Legacy REST API (the /wc-api/v1, v2 and v3 endpoints) from core in version 9.0, released June 2024. Any integration that still calls /wc-api/ now gets a 404 on an up-to-date store, unless the separate community "WooCommerce Legacy REST API" extension is installed as a stopgap.

This tool maps common endpoints from the old shape to the current one, so you know what to change in an old integration rather than guessing.

What actually changes

Legacy (/wc-api/v3/)Current (/wp-json/wc/v3/)
AuthOAuth 1.0a over HTTP, or Basic auth over HTTPSBasic auth over HTTPS (recommended), or query-string credentials
Response shapeWrapped, e.g. { "orders": [...] }Unwrapped: a plain array or a plain object
Base path/wc-api/v3//wp-json/wc/v3/

Questions people ask

Is the legacy API completely gone?

From WooCommerce core, yes, as of version 9.0. A separate community extension can restore it temporarily, but that's a stopgap, not a long-term fix.

Will the field names inside each response be identical?

Mostly, but not always. Treat this mapping as a starting point for the URL and auth, and check your integration's parsing code against a real response from the new endpoint.

Do I need new API keys?

Your existing WooCommerce REST API keys (from Settings → Advanced → REST API) work with the current /wp-json/wc/v3/ endpoints; the legacy API used the same kind of key.

What about /wc-api/v1/ and /v2/?

Both are also gone from core as of version 9.0, same as v3. Map their resource names the same way as v3, since the resource paths themselves changed little across legacy versions.

Related tools

WooCommerce REST API Request BuilderPick an endpoint and fill in a form, get curl, JavaScript, PHP, Python and a Postman collection back. Your key never leaves your browser.WooCommerce Store API ExplorerCheck whether a store's public Store API is reachable, see a few live products, and get starter code for a headless build.WooCommerce Blueprint BuilderBuild a starter Blueprint settings file, or paste two Blueprints and see exactly what's different between them.WooCommerce Redirect Snippet GeneratorSend customers to a custom page after checkout, login, registration or add to cart, by product or user role.

Want this builtinto your store?

I'm Emmanuel, a Shopify and WooCommerce developer. If this tool pointed at something you'd rather have fixed for you (a faster store, cleaner product data, a migration, a custom feature), send me a note.

Emmanuel Asika

Emmanuel Asika

Shopify & WooCommerce developer, Dublin

I build and fix online stores: new builds, migrations, speed, SEO and the custom bits apps can't do.

hello@emmanuelasika.com
See my work

Last reviewed 30 September 2026.

Sources: WooCommerce Developer Blog: Goodbye, Legacy REST API · WooCommerce REST API Documentation