Admin

Manage CLI access

Choose the IP addresses your organisation’s cradle-calls tokens and API keys can be used from, see or revoke the tokens your team has created, and manage API keys. This affects CLI tokens and API keys only, not the Cradle apps.

Your current address:

Allowed IP addresses and ranges

One address or CIDR range per line (IPv4 or IPv6). We recommend your office’s static addresses and the networks your agents run on, and nothing else. Leave empty to allow any address. Changes apply within about 30 seconds.

API keys

Organisation keys for your own systems and integrations (private beta). A key isn’t tied to a person: it keeps working if the admin who created it leaves, until an admin revokes it or it expires. It reads only what its scopes allow.

Create an API key

Name What it can read CallsWhen, who, direction, numbers, matched contacts and CRM logging. Needed for anything below except reports. TranscriptsWhat was said on calls. AI summariesThe summary and title of calls. Recording detailsWhich recordings exist, whose leg each is, and how long. Recording audioDownload the audio of recorded calls, as files that can be kept and shared. ReportsCall statistics, the same numbers as the Cradle web app. Staff presenceEach person’s Cradle presence (available, away, offline and so on) when calls rang them. Needs Reports. Only this person’s calls (optional) Only allow from these IP addresses

Required when the key can read transcripts, summaries, recording details, audio or staff presence. List the addresses of the systems that will use it, and nothing else.

Expires after I accept the Private Beta Terms for my organisation

Manage CLI access

CLI tokens in your organisation

API keys

Create an API key

This key can read your organisation’s calls or staff presence