# Get access

You do not register yourself with Mirakl Connect.
The Mirakl partner team registers your channel, then gives you the credentials, the identifiers, and the resources your connector needs.
Request them before you start to build.

## What Mirakl provides

* **OAuth2 client credentials**: a **client ID**, a **client secret**, and the token endpoint URL.
Your connector exchanges them for the access token that authenticates every REST call, so store them securely.
For how to use them, refer to [Authorization](/content/product/connect-channel-platform/developer-guide/authorization).
* **A channel ID**: your channel's identifier in Mirakl Connect.
Mirakl generates it when it registers your channel in Mirakl Connect, so your connector does not create it.
You pass it to the APIs that require it, and you also see it on the events you receive.
Store it in your connector's configuration.
* **Event subscriptions**: Mirakl Connect subscribes your connector to the event types it needs, and routes those events to the destination you configure.
Mirakl provisions these subscriptions for you.
* **The taxonomy activation in the Catalog Transformer**: your connector registers the channel's taxonomy itself.
Mirakl then activates its synchronization to the Catalog Transformer, and trains the model on it.
This step is not self service.
Until Mirakl completes it, no product is transformed for your channel, so your connector receives no product to create.
Refer to [Activation by Mirakl](/content/product/connect-channel-platform/developer-guide/taxonomy#activation-by-mirakl).
* **A Mirakl Connect test account**: the account you build and validate against before you deploy to production.
It keeps the test data separate from the production data.


## What you configure

* **The destination of your events.**
Mirakl owns the subscriptions, and you own the queue or the topic they deliver to.
Choose one, and supply what it needs, as described in [Receiving events](/content/product/connect-channel-platform/developer-guide/receiving-events).
* **The hosts your connector calls.**
Each host has a test address and a production address.
Refer to [Environments](/content/product/connect-channel-platform/getting-started/environments).


## Related pages

* [Authorization](/content/product/connect-channel-platform/developer-guide/authorization): how to exchange the client credentials for an access token, and the model of the scopes.
* [Receiving events](/content/product/connect-channel-platform/developer-guide/receiving-events): the three supported destinations, and how to configure each one.
* [Environments](/content/product/connect-channel-platform/getting-started/environments): the test and production addresses of each host.
* [Taxonomy](/content/product/connect-channel-platform/developer-guide/taxonomy): the two calls that register the channel's taxonomy, and the activation Mirakl owns.
* [Integration overview](/content/product/connect-channel-platform/getting-started/integration-overview): where your connector sits, and what it owns once it runs.