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

> ## Agent Instructions
> Use the public API base URL: https://api.teamfollowup.ai/api.
> Authenticate public API requests with Authorization: Bearer YOUR_API_KEY.
> Use product-owned terms: agents, calls, campaigns, contacts, phone numbers, billing, and configuration.

# Introduction to Team Follow Up APIs

> Build, operate, and monitor Team Follow Up AI workflows through customer-facing APIs.

Team Follow Up APIs let you work with the same customer-facing platform objects
used in the dashboard: agents, calls, campaigns, contacts, phone numbers,
billing status, and configuration.

Use these APIs to connect Team Follow Up AI to your existing systems while
keeping dashboard login, tenant access, and role permissions intact.

<Note>
  Public modules are launching one by one. Endpoints appear here after they have
  schemas, examples, auth notes, status codes, errors, and client parity checks.
</Note>

## Overview

Every public API request uses bearer API key authentication:

```http theme={"dark"}
Authorization: Bearer YOUR_API_KEY
```

The public API base URL is:

```text theme={"dark"}
https://api.teamfollowup.ai/api
```

Create and manage keys from the **API Keys** page in the dashboard. API keys are
scoped by module, so a key can be limited to read-only access or to specific
workflow areas.

## Platform Capabilities

<CardGroup cols={2}>
  <Card title="Build" icon="bot" href="/api-reference/agent-builder/list-agents">
    Create and update agents, campaigns, workflows, voices, phone numbers, and
    configuration.
  </Card>

  <Card title="Operate" icon="workflow" href="/api-reference/contacts/list-contacts">
    Sync contacts, inspect campaign state, manage phone number assignments, and
    read platform configuration.
  </Card>

  <Card title="Monitor" icon="activity" href="/api-reference/calls/list-calls">
    Review calls, execution history, outcomes, dashboard metrics, and event
    activity.
  </Card>

  <Card title="Control Access" icon="key-round" href="/authentication">
    Use bearer API keys, module scopes, tenant boundaries, and standard error
    responses.
  </Card>
</CardGroup>

## Start Here

1. Read [Authentication](/authentication) to create API keys and choose scopes.
2. Read [Conventions](/conventions) for response envelopes, errors, and rate
   limits.
3. Read [MCP action tools](/mcp-actions) if an AI agent will call the API.
4. Open the **API Reference** tab and start with the module you want to
   integrate.

## Published Modules

The current public reference covers agents, calls, campaigns, campaign
workflows, projects, power dialer, contacts, agency settings, billing status,
access subscriptions, dashboard metrics, events, GHL resources, voices, and
phone numbers.