> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://launchdarkly.com/docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://launchdarkly.com/docs/_mcp/server.

# Creating API access tokens

> This topic explains how to create API access tokens. These are required to authenticate with the LaunchDarkly REST API and are one of the options to authenticate with the LaunchDarkly CLI.

This topic explains how to create API access tokens. These are required to authenticate with the [LaunchDarkly REST API](/api) and are one of the options to authenticate with the [LaunchDarkly CLI](/home/getting-started/ldcli).

> **API access tokens are private**
>
> Only you have access to the secret values of tokens you create. Other account members cannot access them. Administrators can delete your tokens, but cannot view their values.

You can create an API access token from the Authorization page.

By default, API tokens are personal tokens. You can choose to create a service token instead during the token creation workflow.

> **Save new tokens immediately**
>
> Your API access token is visible one time, immediately after you create it. If you leave or refresh the page where the token is displayed, it will be obscured and no longer visible. You must copy and store new access tokens somewhere secure before you leave the creation page, or you will lose access to the tokens.

Here is a screenshot of the "Access tokens" section of the **Authorization** page:

![The Access tokens list with an obscured access token called out.](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/launchdarkly.docs.buildwithfern.com/b81763b173e77e4712a0d67ec50159534f86a26d444eec457c93fe3a95d60546/assets/images/auto/settings-access-tokens-obscured-callout.auto.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260926%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260926T024717Z&X-Amz-Expires=604800&X-Amz-Signature=544f3e2aeee45feabf959205b4b20991472ce18ed46ca2ff08de9a7353fa03b0&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

## Create access tokens

To create an access token:

1. Click the **gear** icon in the left sidebar to view Organization settings.
2. Click **Authorization**. The **Tokens** tab appears.
3. Click **Create token**. The "Create an access token" panel appears.
4. Give your token a human-readable **Name**.
5. Assign a **Role** to the token by choosing one from the menu.

* Select Reader, Writer, Admin, or Owner if you want to use a base role.
* Select **Custom** to choose another role, either one you've created or one provided by LaunchDarkly. This option is available only if your LaunchDarkly subscription includes custom roles.
* Select **Inline policy** to create a role policy that applies only to this token. To learn more, read [Create policies for roles](/home/account/roles/role-create#create-policies-for-roles). This option is available only if your LaunchDarkly subscription includes custom roles.

6. Select the **API version** to assign to your token. By default, API requests you send using this token will use this API version. To learn more, read [Versioning](/api#versioning).
7. (Optional) Select the **This is a service token** checkbox if you wish to create a service token. This feature is only available to customers on Enterprise plans.
8. Click **Save token**. The new token appears in the **Authorization** page.
9. Copy and save the token somewhere secure. After you leave this page, the token is obscured:

![A new access token with a reminder to copy and store it displayed.](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/launchdarkly.docs.buildwithfern.com/aeb1716199e3e51f17396725fa76bd867da66a74d8053cc8a402cee1de6e30f9/assets/images/auto/settings-access-tokens-notification.auto.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260926%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260926T024717Z&X-Amz-Expires=604800&X-Amz-Signature=990f1a194ecb82edde141a8339b67fb112d85c9c4fbbf11fc7c5faefea63aaa3&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

You can also use the REST API: [Create access token](/api/access-tokens/post-token)

After you create a token, you can clone or delete it. You can also reset the secret values of your tokens, or adjust the scope of your personal tokens.

> **Service token limits**
>
> By default, LaunchDarkly allows you to create 200 service tokens per account. You can create more upon request. To learn more, read [How to right size when you are over LaunchDarkly system resource count limits](https://support.launchdarkly.com/hc/en-us/articles/12319971362075-How-to-right-size-when-you-are-over-LaunchDarkly-system-resource-count-limits).