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

# Data and analytics

> APIs for reporting, event streams, language detection, and custom properties.

Everything you see in the Text dashboard is accessible through these APIs — and so are the events that the dashboard doesn't surface at all.

## Reports API

**What it does:** Exposes all performance data in the Text dashboard — chat volume, response times, customer ratings, and agent metrics.

**When you'd use it:**

* Scheduling data pulls into your BI tool or spreadsheet
* Building a custom performance dashboard
* Combining Text data with other business metrics

<Card title="Reports API" icon="chart-bar" href="/api/reports/" horizontal>
  Pull chat volume, response times, ratings, and agent performance into your own
  tools.
</Card>

## Language Detection API

**What it does:** Detects the language a customer is writing in and returns a language code your integration can act on — for routing, automated responses, or analysis.

**When you'd use it:**

* Routing customers to agents who speak their language
* Triggering responses in the customer's language
* Analyzing language distribution across your customer base

<Card title="Language Detection API" icon="language" href="/api/language-detection/" horizontal>
  Detect customer language and use it to route and respond more intelligently.
</Card>

## Webhooks

**What it does:** Sends an HTTP request to your URL when a registered event occurs — no polling required.

**When you'd use it:**

* Syncing chat transcripts to your CRM when a conversation ends
* Triggering workflows based on specific events (a bad rating, a chat abandoned)
* Alerting external systems the moment something happens in Text

<Card title="Webhooks" icon="webhook" href="/api/webhooks/" horizontal>
  Register events and let Text push data to your systems automatically.
</Card>

## Events and properties

**What it does:** Covers two related things: the properties system, which lets you attach custom data to chats, threads, events, groups, or a license; and system activities, which are predefined events Text emits internally — things like cart operations, thread summaries, and routing changes.

**When you'd use it:**

* Attaching custom data to conversations or events for richer reporting
* Reading system activities to react to internal Text events
* Defining and registering custom property namespaces for your integration

<Card title="Events and properties" icon="list" href="/api/events-and-properties/default-properties" horizontal>
  Access the full event stream and enrich it with custom properties.
</Card>
