# Custom Token

## Properties

**Integration Name**: Display name for the integration\
**Key**: Unique identifier for the integration. This should only contain letters and numbers.

## Integration Parameters

Integration parameters allow you to parameterize the integration when defining a connected account. These parameters can be referenced through any of the custom integration inputs by surrounding the text in curly braces `{parameterName}`.

![](https://3088276961-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC6qMwMGWBgxnN70QsDuH%2Fuploads%2Fgit-blob-c8a7ac826c2c8847396744d05226d1992ea864f2%2Fcustom-token-v182-0.png?alt=media)

For example, if you want to parameterize a query parameter on the **Authorization Endpoint**, the url would look like the following:

```
https://airkit.com/auth?queryparam={parameterName}
```

![](https://3088276961-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC6qMwMGWBgxnN70QsDuH%2Fuploads%2Fgit-blob-ec1abdb878069a822353ccef040f88b71c53c0a8%2Fcustom-token-v182-1.png?alt=media)

Then, the query parameter would then be accessible when you create the connected account.

![](https://3088276961-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC6qMwMGWBgxnN70QsDuH%2Fuploads%2Fgit-blob-ca735378110687dc5f48f76873ce90324d895ddd%2Fcustom-token-v182-2.png?alt=media)

Another example for using integration parameters would be for connections where you have different servers for access token endpoints. You could customize the URL string with the following : `{serverName}`

```
https://{serverName}.airkit.com.com/oauth2/v1/token
```

This could then be used to create multiple connected accounts with the same authentication patterns when using multiple profiles (i.e. DEV, QA, PROD)

## Custom Token

**Access Token Endpoint (required)**: The URL to retrieve the access token.

**Access Token Verb (required)**: The HTTP verb for the call to retrieve the access token. GET or POST

## Access Token Parameters

Parameters to include with the HTTP request that is made to retrieve the custom token.

## Auth Token

**Token Parameter Type (required)** : Where to pass the token with the [HTTP Request data operation](../../data-operations/http-request-data-operation). Select between **URL Parameter** and **Header**.

**Token Parameter Name (required)**: The name to define how the token is specified (i.e. Authorization).

![](https://3088276961-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC6qMwMGWBgxnN70QsDuH%2Fuploads%2Fgit-blob-c4e863b91a01904565b17579c7750b38f47068ba%2Fcustom-token-v182-3.png?alt=media)

**Token Parameter Value Template (required)**: The format of how to pass the token, once retrieved. The token is denoted as `{token}` in the input. For example, if the token is passed in the header of the request, with the format `Authorization: Bearer <token>`, then this field would look like:

![](https://3088276961-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC6qMwMGWBgxnN70QsDuH%2Fuploads%2Fgit-blob-0f55fc0920dd479fc6f181ef29f639928feee90c%2Fcustom-token-v182-4.png?alt=media)

## Request Parameters

Request parameters are included with every HTTP request that is used in an [HTTP Request](../../data-operations/http-request-data-operation) in [Connections Builder](../../studio/builder-bar/connections-builder).

## Redirect URIs

> 📘 Redirect URIs If an external data source requires a Redirect URI, the url will differ based on the realm the organization was provisioned in.
>
> **US Realm**
>
> ```
> https://us.api.prod.airkit.com/internal/sessions/v1/auth/callback
> ```
>
> **EU Realm**
>
> ```
> https://eu.api.prod.airkit.com/internal/sessions/v1/auth/callback
> ```
>
> **AP Realm**
>
> ```
> https://ap.api.prod.airkit.com/internal/sessions/v1/auth/callback
> ```
