Existing API Integrations

The former customer API key has moved to Settings → Customer settings → API Management → API Keys → Embed API Keys.

Existing Embed API Calls Keep Working

Moving the key does not change its value or invalidate existing integrations. Continue sending it in the X-API-KEY header to https://mimeeqapi.com for product listing, product configuration details, configuration pricing, and short-code generation.

The Embed API Reference remains at its existing URL. Its endpoints retain their existing response shapes. Do not change these calls to the Admin host or Bearer authentication just because the key moved.

If you regenerate the Embed API key, its previous value stops working. Update every integration that uses it. The Authorization Guide explains where to copy and regenerate the key.

New Admin Integrations Use a Separate Key

Create a key in the Admin API Keys section for the Admin API. Send it as Authorization: Bearer <admin-key> to https://admin.mimeeqapi.com/v1.

Admin keys have selectable scopes, optional expiry, and individual revocation. Creating an Admin key leaves your Embed API key unchanged. Admin operations use their own paths and response envelopes; they are not a drop-in replacement for the four existing Embed endpoints.

The Admin API Reference displays the live documentation from the Admin service. Use it for current operations and required scopes.

Website Sign-In Is Separate

Your existing mmq-auth component and mimeeqAuth session flows do not change because the API key moved. Keep using them for end-user sign-in and personalized configurator experiences. See the Authentication Overview.