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

# Use Tartini as your system's channel

> Generate access tokens to integrate your own systems directly with Tartini.

export const Artigo = ({titulo, href, children}) => <a className="lista-artigos-item" href={href}>
    <span className="lista-artigos-texto">
      <span className="lista-artigos-nome">{titulo}</span>
      {children ? <span className="lista-artigos-desc">{children}</span> : null}
    </span>
    <svg className="lista-artigos-seta" viewBox="0 0 24 24" width="18" height="18" aria-hidden="true">
      <path d="M9 6l6 6-6 6" fill="none" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" />
    </svg>
  </a>;

export const Lista = ({titulo, children}) => <div className="lista-artigos">
    {titulo ? <p className="lista-artigos-titulo">{titulo}</p> : null}
    <div className="lista-artigos-itens">{children}</div>
  </div>;

With an API token, your system talks directly to Tartini, without needing anyone to open the screen.

<Note>
  Who can generate and revoke tokens: only Administrator. Available on the Scale plan.

  The Tartini interface is in Portuguese. Screen and button names appear here exactly as on screen, with the translation in parentheses.
</Note>

***

## What it's for

An API token gives your system access to the Tartini public API, with AI features and knowledge base search. The technical details of using the API are for whoever develops your system.

Where to find it: **Configurações > Canais > Conexão via API** (Settings > Channels > API Connection).

<Note>
  Keep your tokens secure and never share them. Whoever has the token can access your account through the API, the same way you can.
</Note>

***

## One token per system

You can create more than one token, one for each system you integrate, with a name that identifies where each is used, like "Integração ERP".

Each token is revoked independently: revoking one system's token doesn't affect the others.

***

## Generate a token

By default, a new account has no tokens created yet.

<Steps>
  <Step title="Open the screen">Go to **Configurações > Canais > Conexão via API**.</Step>
  <Step title="Start a new token">Click **Criar Token** (Create token).</Step>
  <Step title="Name the token">Fill in **Nome do Token** (Token name), to identify later where it's used, and optionally a **Descrição** (Description).</Step>
  <Step title="Create it">Click **Criar Token**.</Step>
  <Step title="Copy and save it">Click **Copiar** (Copy) and store the token somewhere secure.</Step>
</Steps>

<Warning>
  The token is only shown once, at the moment it's created. If you lose it, there's no way to recover it: create a new one and revoke the old one.
</Warning>

***

## Track your tokens

Each registered token shows the name, the description, when it was created, and the last time it was used, or **Nunca** (Never), if it hasn't been used yet.

***

## Revoke a token

<Steps>
  <Step title="Open the screen">Go to **Configurações > Canais > Conexão via API**.</Step>
  <Step title="Delete the token">Click the trash icon on the token's card.</Step>
  <Step title="Confirm">Click **Excluir** (Delete).</Step>
</Steps>

<Warning>
  Once revoked, the token stops working and any system that was using it loses access.
</Warning>

***

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Who can create or revoke tokens?">
    Only Administrator.
  </Accordion>

  <Accordion title="I lost the token before copying it. How do I recover it?">
    It's not possible to recover a token after closing the modal. Create a new one and revoke the old one, if it's not in use.
  </Accordion>

  <Accordion title="Do tokens expire on their own?" />

  <Accordion title="Do I need a different token for each system I integrate?">
    No. You can use a single token across several systems or create one for each. Separate tokens make it easier to identify where each one is used and let you revoke one system's access without affecting the others.
  </Accordion>
</AccordionGroup>

***

## Related articles

<Lista>
  <Artigo titulo="Receive events in your system" href="/en/integracoes/webhooks">Automatic notifications when a conversation is closed.</Artigo>
  <Artigo titulo="Channels explained" href="/en/canais/canais-explicados">The channels available in Tartini.</Artigo>
</Lista>


## Related topics

- [Receive events in your system](/en/integracoes/webhooks.md)
- [Channels explained](/en/canais/canais-explicados.md)
- [What Tartini is](/en/visao-geral/o-que-e-o-tartini.md)