> Part of [WHCC Developer Documentation](https://www.whcc.com/developer/llms.txt)

# Migrate Auth to API Key

Version 1.0 · Updated 2026-10-12

You already run an integration on the Editor API (Legacy), the Order Submit API (Legacy), or both. Moving it onto a WHCC API key changes how you authenticate and the names of the routes you call. The order bodies you send and the editors your users open stay the same.

> **These pages are for an existing integration being moved onto an API key.** If you are building something new, start at the [Quick Start](https://www.whcc.com/developer/docs/quick-start/index.html.md) instead: new integrations use the [WHCC API](https://www.whcc.com/developer/docs/api/index.html.md), which is a separate flow.

## Which option fits your integration?

### [Use editors with an API key ▸](https://www.whcc.com/developer/docs/legacy/api-key-auth-migration/editor-api/index.html.md)

Start here if you open WHCC editors for your users. It covers reading products and designs, creating an editor, and exporting what your users finish. You then submit the exported order with the Order Submit API.

### [Submit orders with an API key ▸](https://www.whcc.com/developer/docs/legacy/api-key-auth-migration/order-submit-api/index.html.md)

Use this page to create and confirm orders and receive order events. It works on its own if you build OrderImport bodies yourself, and it's the next step after an editor export.

## What changes

- **One API key, sent as a bearer token.** It replaces the consumer key, the secret and the access-token call. There is no token to refresh.
- **Two scopes on the key:**`apikey` and `apikey:oas`. `GET /discovery` shows what your key can reach.
- **New route names on a new host.** Ordering moves to `/oas/orders/create` and `/oas/orders/{confirmationId}/confirm` on `apis.whcc.com`. The bodies you send don't change.
- **An event subscription instead of the consumer callback.** You create it yourself with the API key, and it receives events for every order on your account.