# How to migrate

{% hint style="danger" %}
We've recently migrated the whole authentication process to our new [Authentication API](/core/authentication.md). The legacy endpoints, scope syntax, and SSO using a custom org-specific secret key are no longer supported since **November 2024**. If you need to manage any projects or Commerce Layer integrations that still leverage the old way of authenticating, please follow the steps below to update them.
{% endhint %}

To migrate to the new authentication process you just need a couple of tweaks to your current codebase:

1. Change the authentication endpoint from `https://yourdomain.commercelayer.io/oauth` to `https://auth.commercelayer.io/oauth`
2. Stop using the market and/or stock location number (e.g.: `market:1234`) when [including a scope](/core/authentication.md#authorization-scopes) and start using the new syntax with the ID or the code (e.g. `market:id:xYZkjABcde` or `market:code:europe`).
3. If you're still leveraging a custom org-specific secret key to sign a manually built JWT for SSO, switch to the [JWT bearer](/core/authentication/jwt-bearer.md) flow with a proper [assertion](/core/authentication/jwt-bearer.md#creating-the-jwt-assertion).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.commercelayer.io/core/authentication/how-to-migrate.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.