Skip to main content
The API Connection integrates your systems directly with the Tartini platform. The page manages the API tokens that authenticate these calls. The page is at Configurações > Canais > Conexão via API (Settings > Channels > API Connection) (talk.saninternet.com/settings/channels/api).
For the complete reference of endpoints, authentication, payloads, and error codes, see the API Reference.

How It Works

Each token is an application credential (it isn’t tied to a human user) that authenticates requests to Tartini’s REST API. You create as many tokens as you need, one per integration, for example, and revoke them individually when a key leaks or an old system is decommissioned. Authentication follows the Bearer Token standard in the HTTP header:
The full token appears only once, at the moment of creation. After that, Tartini shows only a masked version (e.g., talk_••••••••a1b2). If you lose the token, you’ll have to generate a new one.

Create a Token

1

Open the creation modal

Click Criar Token (Create Token), in the page header (or the empty-state button, before any token exists).
2

Fill in the details

  • Nome (Name) (required): a short identifier, e.g.: Integração ERP.
  • Descrição (Description) (optional): free text describing the token’s purpose.
3

Copy the token

After creation, a modal displays the full token. Copy it and store it somewhere secure: for security reasons, Tartini won’t show that value again.
This is the only moment the full value is visible. Once you close the modal, Tartini only shows the masked version from then on.

View and Manage Tokens

The page lists all tokens created by the Company in cards, with:

Delete a Token

Each card has a trash-can button (tooltip Excluir token / Delete token). Clicking it opens a confirmation. Once confirmed, the token is revoked and stops authenticating API calls.
On this screen, the only action available for an existing token is deletion, which can’t be undone. Before removing one, make sure no critical system is still using that token.

Best Practices

  • Tokens per integration: since each token can be deleted independently, different integrations can use different tokens, without affecting the others when you remove one.
  • Token security: keep the value secure and never share it, as the screen’s own warning states.
  • “Último uso” (Last used) field: helps identify tokens with no recent use when reviewing which ones are still needed.

Who Can Generate Tokens

Only the Administrador da Empresa (Company Administrator) has permission to create and revoke API tokens. Managers and Agents don’t see the API Connection page.
For authentication details and the API’s standardized errors guide, see Authentication.