> ## 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, campaigns, projects (GoHighLevel sub-accounts), contacts, calls, outcomes, skills, cadences, phone numbers.
> Scope requests by locationId rather than projectName.
> Read the guide linked from each API reference group before recommending an endpoint.

# Caller ID API

> Register the businesses behind your calling numbers with Twilio, and read where every number stands.

Registering a business tells the US carriers who owns its numbers, so its calls
are labelled as spam less often. What a registration does, what it needs and
what it cannot promise are in [Caller ID registration](https://docs.teamfollowup.ai/phone-numbers/caller-id.md).

Both operations take the business's `locationId`. Read the summary first: it
says which numbers are ready, lists every detail a registration takes in
`fields`, and gives the `termsVersion` a registration echoes.

| Endpoint | Use it to |
| - | - |
| [Get caller ID status](https://docs.teamfollowup.ai/api-reference/caller-id/get-caller-id-status.md) | See every number, whether it can be registered, and every registration's state. Scope `phone_numbers:read`. |
| [Register a business for caller ID](https://docs.teamfollowup.ai/api-reference/caller-id/register-a-business-for-caller-id.md) | Register one business and its numbers in one call, naming who confirmed the details. Scope `phone_numbers:write`. |

Both use the phone number scopes your key already has, so no new key is needed.
`phone_numbers:write` also covers reading. See [Authentication](https://docs.teamfollowup.ai/authentication.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.