> ## Documentation Index
> Fetch the complete documentation index at: https://docs.slant.app/llms.txt
> Use this file to discover all available pages before exploring further.

# API connections

> Create API tokens and connect Slant to MCP clients and Zapier.

API connections let you connect Slant to external tools. Use the **API** tab to create personal access tokens, the **MCP** tab to connect MCP-compatible clients, and the **Zapier** tab to connect Zapier automations.

Personal access tokens let you read your Slant data from outside the app — useful for spreadsheets, custom dashboards, AI assistants, and other integrations. Each token is tied to your user account and inherits your access.

<Note>
  Tokens are read-only by default. To enable write access for a token, click **Enable write access** on the token's row and tell us how you'll use it — see [Enable write access](#enable-write-access).
</Note>

## Create a token

To open the token list, go to **Settings** → **API connections**, then select the **API** tab.

<Steps>
  <Step title="Click Create token">
    The **Create API token** form opens.
  </Step>

  <Step title="Enter a Token name">
    Use a name that describes where the token will be used (for example, "Tax export spreadsheet" or "Personal Zapier"). The name only helps you recognize the token later.
  </Step>

  <Step title="Click Create token">
    Slant generates a token that starts with `slnt_pat_` and shows it under **Your new API token**.
  </Step>
</Steps>

<Warning>
  Copy the token before leaving the page. After you navigate away, the full value cannot be viewed again — only the first few characters are stored.
</Warning>

Click **Copy** next to the token, then paste it into the tool that needs API access.

## Token list

Each token you create appears in the table below the create button:

* **Name** — the label you gave the token
* **Token** — the first few characters, for identification only
* **Access** — **Read only** or **Read & write** — read-only by default
* **Created by** — the user who issued the token
* **Created** — the date the token was issued
* **Last used** — the most recent time the token made a request, or **Never** if it hasn't been used yet

## Enable write access

<Steps>
  <Step title="Click Enable write access">
    Click **Enable write access** on the token's row in the list. (Only appears for read-only tokens.)
  </Step>

  <Step title="Describe how you'll use it">
    In the **Enable write access** dialog, fill in **Why do you need write access?** with a short description of how you'll use it.
  </Step>

  <Step title="Click Enable write access">
    A toast confirms "Write access enabled" and the token changes to **Read & write** immediately.
  </Step>
</Steps>

## Revoke a token

Revoke a token any time you no longer need it, or as soon as you suspect it's been exposed.

<Steps>
  <Step title="Find the token in the table">
    Match the **Name** or first few characters of the token.
  </Step>

  <Step title="Click the trash icon">
    The **Revoke token** confirmation appears.
  </Step>

  <Step title="Click Revoke">
    The token stops working immediately. Any tool using it will lose access.
  </Step>
</Steps>

<Warning>
  Revoking a token cannot be undone. Tools using the revoked token need a new one before they'll work again.
</Warning>

## Use a token

Pass the token in the `Authorization` header of every API request:

```
Authorization: Bearer slnt_pat_<your-token>
```

For full request and response details, see the [API reference](/api-reference/overview).

## FAQ

<AccordionGroup>
  <Accordion title="Can I get write access?">
    Yes. Tokens are read-only by default. Click **Enable write access** on the token's row, fill in the reason, and click **Enable write access**. Write access is enabled immediately.
  </Accordion>

  <Accordion title="What happens to my tokens if I leave the firm?">
    Your tokens are tied to your user account. When your account is removed, the tokens stop working.
  </Accordion>

  <Accordion title="I lost the token. Can I see it again?">
    No. The full token is only shown once, right after it's created. Revoke the old token and create a new one.
  </Accordion>

  <Accordion title="Does a token give access to every book I'm in?">
    Yes. A token inherits the same book access as your user account. If you're added to or removed from a book, the token's access changes with it.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="API reference" icon="code" href="/api-reference/overview">
    Authentication, endpoints, and request examples.
  </Card>

  <Card title="Zapier" icon="zap" href="/setting-up-slant/integrations/zapier">
    Connect Slant to thousands of apps without writing code.
  </Card>
</CardGroup>