> ## 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.

# Management

> APIs for configuring and managing Text — agents, routing, customer data, and identity.

Text has a lot of moving parts — agents, groups, routing rules, and data. These APIs let you control all of it in code.

## Configuration API

**What it does:** Manages agents, groups, routing rules, webhooks, and custom properties. Everything configurable in the interface is available here.

**When you'd use it:**

* Adding or updating agents in bulk
* Creating and managing routing rules
* Registering and managing webhooks

<Card title="Configuration API" icon="gear" href="/api/configuration/" horizontal>
  Manage agents, groups, routing, webhooks, and properties through code.
</Card>

## Customer Data Platform API

**What it does:** Lets you store data from your own systems — customer properties, segments, identifiers — inside Text, where agents can access it during conversations.

**When you'd use it:**

* Storing customer properties (loyalty tier, account value, product used) inside Text
* Querying customer data to build segments or trigger automated messages
* Syncing customer records between Text and your CRM

<Card title="Customer Data Platform API" icon="database" href="/api/customer-data-platform/" horizontal>
  Store and retrieve custom customer data within Text.
</Card>

## Global Accounts API

**What it does:** Handles the identity layer shared across all Text products — accounts, organizations, and the tokens that tie them together.

**When you'd use it:**

* Building sign-in with Text credentials
* Managing agent accounts across multiple products from a single system

<Card title="Global Accounts API" icon="users" href="/api/global-accounts/" horizontal>
  Manage identity and authentication across Text products.
</Card>

## Customer Accounts API

**What it does:** Handles authentication for customers using the Customer Chat API. Required for any integration built on the Customer Chat API. Supports three grant types depending on how your integration is structured: cookie grant for browser-based apps, agent token grant for backend-issued tokens, and identity token grant for transferring identity across devices.

**When you'd use it:**

* Authenticating customers in a frontend app using browser cookies (cookie grant)
* Issuing customer tokens from your backend on behalf of specific users (agent token grant)
* Transferring a customer's identity between devices or browsers (identity token grant)

<Card title="Customer Accounts API" icon="user-check" href="/api/customer-accounts/" horizontal>
  Create and manage customer identities and access tokens for use with the
  Customer Chat API.
</Card>

## Chat Widget JS API

**What it does:** Controls the Text chat widget from your site's JavaScript — showing, hiding, passing customer data to agents, and tracking outcomes.

**When you'd use it:**

* Showing or hiding the widget based on page or user state
* Passing customer data (name, email, order history) to agents before a conversation starts
* Tracking which chats resulted in a conversion
* Triggering the widget based on visitor behavior

<Card title="Chat Widget JS API" icon="code" href="/api/chat-widget-js-api/" horizontal>
  Control the Text widget behavior and pass data to agents from your website.
</Card>

## Partner API

**What it does:** Lets Text partners pull earnings, campaign performance, and client data out of the partner portal and into their own systems.

**When you'd use it:**

* Building a dashboard to track commissions and referral performance
* Managing client accounts from your own system
* Syncing partner data into your CRM or reporting tools

<Card title="Partner API" icon="handshake" href="/api/partner/" horizontal>
  Access partner earnings, campaign data, and client accounts through code.
</Card>
