# Create an API Access Token as a Brand

*Account Administrators* and *Implementation Specialist* members of a brand account can enable impact.com API access and view account credentials. Follow the steps below to create a new API token and configure access scopes for the token. Read some tips on how to [keep your access tokens secure](https://app.gitbook.com/s/hRN1rcrim887TwHLBjac/readme/api-access-tokens-and-changelog/keep-your-access-tokens-secure).

{% hint style="info" %}
**Note:** Visit impact.com's [Integrations Portal](https://integrations.impact.com/impact-brand/reference/how-to-structure-requests) to view API reference documentation, integration guides, and more.
{% endhint %}

#### Create an access token

1. From the top navigation bar, select ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-1183576591b45997efe4dc81a25024640591d02a%2F245137dc972a7a7f6165b59538fcdbac8fd5bd8fee4ba9f20c1a2982c5b58b57.svg?alt=media) **\[User profile]** → **Settings**.
2. In the left column, scroll to *Technical*, then select [**API**](https://app.impact.com/secure/advertiser/api/fr/api-access-tokens-ui.ihtml).
3. Create a new token by selecting **Create Access Token** on the upper-right side of the page.

#### Create a token

<details>

<summary>1. Setup</summary>

* Enter a suitable name into the **Token Name** text field.
* Add a **Description** that describes the purpose of the token for your reference in the future.
* Specify the **API Version** that the token will be compatible with. We suggest using the latest API version, which is also the default choice.
* Select **Next**.

  <div data-with-frame="true"><figure><img src="https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-62d668ef403ad96413355d4252365f777ee2bd77%2F27f7be4e1e67a2277cd86ea134f106d54dac272af818264ed051e4da11e7a7c0.png?alt=media" alt=""><figcaption></figcaption></figure></div>

</details>

<details>

<summary>2. Contact Information</summary>

* Select a **Primary Contact** from the drop-down menu. We'll be in touch with the primary contact about development updates.
* Optionally, add email addresses for developers who should know about updates related to the access token. This is handy when creating tokens for developers who are not account users.

  <div data-with-frame="true"><figure><img src="https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-c0e22bf8dbadf0febcb4e0876a2e27ba9c11601c%2Fc74ae8bc7e7306841becdf55210e23393384325a6754ab8bebf53a72656115b1.png?alt=media" alt=""><figcaption></figcaption></figure></div>
* Select **Next**.

</details>

<details>

<summary>3. API Scopes</summary>

* Toggle an API category on, then check the checkboxes on the left to select the access scopes that you would like to allow on your API token.
* You can clear all scopes by clicking the **Clear All** button near the top-right of the page.

  <div data-with-frame="true"><figure><img src="https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-fbe37ae532c52045515b549a72cdbdf52572ffd2%2F09a1c1600bb506bf3cf731e5a89ae7991c9b7f339096d6aa47c23a9e2daadef2.png?alt=media" alt=""><figcaption></figcaption></figure></div>

</details>

<details>

<summary>4. Select Create</summary>

* Finally, select **Create** on the lower right of the page.

</details>
