# Onboarding

### Obtaining the API Endpoint URL

When logging in to Cordial, you should be able to see which domain your account belongs to. This will determine which endpoint you need to select from the dropdown in the form.

<figure><img src="/files/UBbzShDKgopTuK56qrhG" alt=""><figcaption></figcaption></figure>

### Creating an API Key

To create an API key to use for this channel, please follow the instructions described in the Create an API Key section of Cordial's knowledge base article:

{% embed url="<https://support.cordial.com/hc/en-us/articles/115005365087-API-keys>" %}

The configuration you'll need to use for the API key is as follows:

<figure><img src="/files/5GOBT9RA1Z6Pc748d6CU" alt=""><figcaption></figcaption></figure>

You should now be able to copy the API key to the clipboard for the next step.

### Adding the Cordial Channel

Open your site's view and add the Cordial channel, which will open up the provider form.

<figure><img src="/files/JabQYVuX3T4eFH8aN5Et" alt=""><figcaption></figcaption></figure>

Enter a channel name and select the matching API URL that you've identified in the first step above. For the **Access Token,** use the API key value that you copied in the second step. After clicking **Save & Deploy,** your channel is set up and should start sending events to Cordial.


---

# 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.edgetag.io/channels/cordial/onboarding.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.
