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

# Number Registration

> How RevDesk registers eligible hosted US phone numbers with the analytics engines behind carrier spam labels.

## What it is

The **Free Caller Registry** is a joint intake used by the analytics engines that score caller
reputation for major US carriers: **Hiya**, **TNS**, and **First Orion**. Registering a number
associates it with the business identity that uses it and helps the engines recognize legitimate
calling.

RevDesk manages this workflow for eligible US numbers hosted on RevDesk. It is an included part of
operating those numbers, not a separate product or a bring-your-own-number registration service.

<Note>
  Registration is preventive. It establishes the business identity behind a number, but it does not guarantee
  that carriers will never label a call. Calling behavior, complaint rates, consent, and list quality still
  affect reputation. For a number already labeled, see [caller trust](/concepts/caller-trust).
</Note>

## How it works

1. Add or port an eligible US phone number to RevDesk.
2. Complete the workspace's business identity and caller-trust profile.
3. Confirm the authorization attestation in **Numbers → Trust**.
4. RevDesk submits the hosted number and tracks acknowledgments from the registry engines.

The workflow is asynchronous. You can review its status in **Numbers → Trust** or through the
read-only API endpoints.

## Lifecycle

| Status | Meaning |
| - | - |
| `pending` | RevDesk queued the hosted number for submission |
| `submitted` | The registry accepted the submission; acknowledgments are pending |
| `active` | At least one engine acknowledged receipt |
| `failed` | The submission needs another attempt or operations review |
| `cancelled` | RevDesk stopped monitoring this registration |

Use `GET /v1/number-registrations` to list registrations and
`GET /v1/number-registrations/{id}` to inspect one registration's latest submission and per-engine
acknowledgments. New registrations are created from the authenticated RevDesk number workflow, not
through the public API.

## Webhooks

Subscribe via [`POST /v1/webhook_subscriptions`](/api-reference/webhooks):

* `registration_submitted`: the registry accepted a submission
* `registration_confirmed`: the first engine acknowledgment arrived
* `registration_failed`: a submission failed after retries

Registration for eligible RevDesk-hosted numbers is included. There is no separate Number
Registration subscription or per-number registration line item.


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