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

# Peek at the next contacts to be dialed

> Returns, in order, the contacts the allocator would serve next — a read-only, NON-BINDING snapshot. Nothing is held, locked or recorded, so any of these contacts may be taken by an agent a moment later; treat the answer as a display hint, never a reservation. There is no partner-facing way to claim a contact.

A campaign that exists but is not active, or whose queue is empty, answers 200 with an empty array — never 404. Contacts already held by an agent and contacts whose eligibility lies in the future are excluded. Callbacks pinned to a specific agent are not visible on this surface until their pin lapses.

Unknown query parameters are rejected with 400 rather than ignored.

<Warning>The Dialer is a newly released product surface: depending on your account's rollout stage, campaigns managed through this API may not yet be visible in your CloudTalk Dashboard.</Warning>


## API Specification

The full API specification for this endpoint is available in the [documentation index](https://help.cloudtalk.io/llms.txt).


## Related topics

- [Dialer Not Moving to the Next Call](/en/articles/13128134-dialer-not-moving-to-the-next-call.md)
- [Scheduled callbacks](/en/articles/17025683-scheduled-callbacks.md)
- [Salesforce Contact Lists in Campaigns](/en/articles/9170735-salesforce-contact-lists-in-campaigns.md)


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