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

# API availability

> Release status, version retirement, and historical data coverage.

API v2 is live at:

```text theme={null}
https://api.migration.powerdialer.ai/api/public/v2
```

Availability checked on **October 8, 2026**. Create a scoped key in
[Developers](https://migration.powerdialer.ai/dashboard/developers) and follow the
[quickstart](/quickstart). Requests without a valid key return `401`.

Before relying on the integration, verify your webhook receiver and confirm the
historical data coverage described below.

## Version transition

Shared public API keys are no longer accepted. Every request to
`/api/public/v1` returns `410 Gone` with error code `api_v1_retired`. Create a scoped
key in **Developers** and use `/api/public/v2`. There is no shared-key fallback or
caller-selected acting identity.

Existing outbound webhook subscriptions are a separate integration surface.
They keep their existing payloads and signing behavior. The v2 webhook guide
applies only to subscriptions created through v2; do not apply its verifier to a
legacy subscription.

## Included in v2

| Capability | Endpoint |
| - | - |
| Credential identity | `GET /me` |
| Contacts and external-ID upserts | `/contacts` |
| Lists and membership | `/lists` |
| Asynchronous imports | `/imports` |
| Call history and permitted recordings/transcripts | `/calls` |
| Calling-list and rep metrics | `GET /analytics/summary` |
| Incremental resource changes | `GET /changes` |
| Signed webhooks, delivery history and replay | `/webhooks` |

## Historical data and coverage

The release does not automatically expose all historical contacts or calls.
Only records with established workspace and owner attribution are visible.
Historical data needs a separately reviewed, bounded backfill; ambiguous records
remain excluded. A successful empty read does not prove that no historical
activity exists. Confirm your workspace's history coverage before using these
results for reporting.

Event capture begins while a workspace has at least one non-revoked, unexpired
API credential. Changes from before the first key or a period with no active keys
are not reconstructed later. Enumerate current resources and reconcile removals
after such a gap. See [recovery](/guides/webhooks#recover-with-the-change-feed).

There is no server-initiated dialing endpoint, automatic phone timezone inference,
or calling-window enforcement in this contract. Verified meeting/payment/sales
conversions must come from the system that records the business outcome.


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