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

# Quickstart

> Get up and running with the Text API — make your first call, understand how auth works, and find the right API for what you're building.

If you've been using Text through the interface, you already understand the product. The API is just a way to interact with it programmatically — the same conversations, the same agents, the same data, but accessible from your own systems.

In the next few minutes, you'll create a ticket: a customer conversation you can track, assign, and follow up on. You'll see it appear in your account the moment the call succeeds.

<Steps>
  <Step title="Create a personal access token" noAnchor>
    Open <a href="https://www.text.com/app/settings/integrations/api-access/personal-access-tokens" target="_blank">Personal access tokens</a> in Text and select **+ New token**.

    Copy your **Account ID** and your **personal access token**. You'll use both in the next step.

    See [personal access tokens](/authentication/personal-access-tokens) for more on scopes and how authentication works.
  </Step>

  <Step title="Make your first call" noAnchor>
    Open the <a href="api/ticketing/tickets/create-ticket" target="_blank">Create ticket</a> method in our API reference playground — the reference page for the endpoint you're about to call. Select the <Badge color="blue" className="buttonLike">Try it ►</Badge> button on the request page for a live way to call the API.

    In **Authorization**, enter your copied Account ID as the username and your personal access token as the password.

    Fill in the fields marked **required**, then use the <Badge color="blue" className="buttonLike">Send ►</Badge> button to send your request. If you're comfortable, feel free to adjust any of the other available params too.
  </Step>

  <Step title="See it in action" noAnchor>
    A successful call returns the ID of the ticket you just created. To view it in Text, go to <a href="https://www.text.com/app/inbox/tickets/" target="_blank">Inbox → Tickets</a>. Your new ticket is at the top of the list, ready to assign, reply to, or close.
  </Step>
</Steps>

## What's next

<Steps>
  <Step title="See what's possible" icon="compass" noAnchor>
    Before anything technical, it helps to understand what the API actually
    covers. The API overview section walks through every part of Text that's
    accessible via API — what each one does, who it's for, and when you'd reach
    for it.
  </Step>

  <Step title="Learn how conversations are structured" icon="sitemap" noAnchor>
    The API surfaces Text's data as structured objects: chats, threads, events,
    users. If you're going to read from or write to a conversation, knowing how
    these relate to each other makes everything click.
    [Chats](/key-concepts/chats) and [Users and
    accounts](/key-concepts/users-and-accounts) explain the model.
  </Step>
</Steps>

## Already know what you want to build?

<CardGroup cols={1}>
  <Card horizontal title="CRM or data sync" icon="arrows-rotate" href="/api/webhooks/">
    Use webhooks to get notified the moment something happens in Text, then push
    data wherever it needs to go.
  </Card>

  <Card horizontal title="Reports and analytics" icon="chart-bar" href="/api/reports/">
    Use the Reports API to pull conversation data, response times, and
    performance metrics into your own tools.
  </Card>

  <Card horizontal title="Team and account management" icon="gear" href="/api/configuration/">
    Use the Configuration API to manage agents, teams, tags, and routing rules
    programmatically.
  </Card>

  <Card horizontal title="A bot or automation" icon="robot" href="/api/agent-chat/">
    Use the Agent Chat API to send messages, handle routing, or automate
    responses — acting as an agent from outside Text.
  </Card>

  <Card horizontal title="A custom chat interface" icon="message" href="/api/customer-chat/">
    Use the Customer Chat API to build a fully branded chat experience — on your
    site, in your app, or on another channel.
  </Card>
</CardGroup>