> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/agency/what-would-you-like-to-learn-about/account-settings/api-tokens/create-api-access-tokens-as-an-agency.md).

# Create API Access Tokens as an Agency

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](/other/reference-documentation/api-access-tokens-and-changelog/keep-your-access-tokens-secure.md).

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

#### Create an access token

1. From the left navigation menu, select ![](https://1033662419-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTNfAIjBtFchXJ9pC2q%2Fuploads%2Fgit-blob-2353e6dbc5652c0304edc7da554b01277ad88839%2F380bebd18697484deff243a63d0ed3fda5b8b3ae7a5d1da26278c64764d33cd9.svg?alt=media) **\[Menu]** → **Settings**.
2. In the *Account* column, navigate to *Technical*, then select **Platform REST Web Services**.
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://1033662419-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTNfAIjBtFchXJ9pC2q%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://1033662419-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTNfAIjBtFchXJ9pC2q%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://1033662419-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTNfAIjBtFchXJ9pC2q%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>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.impact.com/agency/what-would-you-like-to-learn-about/account-settings/api-tokens/create-api-access-tokens-as-an-agency.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
