Signals Docs
Signals API

Signals API

The Signals API manages everything in your account: trunks, numbers, carrier connections, voice applications, call history, webhooks, billing and the platform itself. It takes and returns JSON over HTTPS.

Base URL

Send every request to https://api.signals.pressone.africa. Paths in this reference are relative to it: GET /trunks means GET https://api.signals.pressone.africa/trunks.

Every request

TerminalCode
curl https://api.signals.pressone.africa/trunks \ -H "Signals-Version: 2026-10-27" \ -H "Authorization: Bearer $SIGNALS_API_KEY"
  • Authorization: Bearer with an API key. See Authentication.
  • Signals-Version: 2026-10-27, which selects the API snapshot. Paths have no version prefix.
  • Content-Type: application/json on every request with a body.
  • Idempotency-Key on the create and action requests marked in this reference, so a retry is safe. See Idempotency.
  • If-Match with the resource's ETag when you change a versioned resource, such as a trunk. See ETag and If-Match.

Lists are paginated, and errors use one format with a request_id you can quote to PressOne support. See Pagination and Errors.

The Calls API

Placing and controlling Programmable Voice calls uses a separate, Twilio-compatible API with its own credentials. See the Calls API reference.

Tags
Trunks
A trunk connects your PBX or SBC to Signals over SIP. Create and change trunks, add the IP addresses and digest credentials that authenticate them and the termination targets that receive inbound calls, attach an outbound policy, and suspend and resume new calls. See the SIP Trunks overview.
Outbound policies
An outbound policy is a named set of rules for the calls your PBX places: which destinations may be called, how many calls may run, how much may be spent in a day and whether calls are recorded. One policy can serve many trunks. See Outbound policies.
Destination countries
The countries a destination rule in an outbound policy can name.
Numbers
Signals sells Nigerian numbers in blocks of consecutive numbers. Search for a block, hold it while you decide, accept its quote to buy it, then route its numbers to a trunk or a voice application. See Numbers and routing.
Carrier connections
A carrier connection carries calls between Signals and a carrier you already have a contract with. Create a connection, give it the peers outbound calls go to and the source networks and password that authenticate inbound calls, and disable or release it. See Bring your own carrier.
Hosted numbers
Numbers your carrier holds for you. Import them onto a carrier connection so Signals knows which connection a call to each number belongs to, and remove them when they leave. A hosted block is routed like any other block. See Numbers your carrier holds.
Voice applications
A voice application is a named set of URLs on your server: the voice URL Signals requests when a call arrives, with an optional fallback URL and status callback URL. Route a number to an application to run it. See Receiving calls.
Voice account
The project's voice account, which holds the AccountSid for the Calls API. The auth token is shown and rotated in the console. See Calls API credentials.
Calls
Your call history. Search it, then read one call in detail: its lifecycle events, a summary of its media and its SIP ladder.
Recordings
The recordings your calls have made. List them, stream the audio and delete a recording you no longer need. See Recording calls.
Automations
Trigger an automation call for one customer, and cancel it before it is dialled. You build automations in the console. See Triggering calls.
Webhooks
A webhook endpoint is a URL on your server that receives signed events from Signals. Create and change endpoints, see every delivery and its result, retry or replay deliveries, and send a test event. For automation events, see Webhook events.
Billing
Your balance, and your financial documents, such as invoices, to list, read and download.
Usage
Your usage and charges, totalled over a time window.
Rates
The destinations you can call, and the rate that applies to one destination.
Projects
The projects in your organization. A project owns your telephony resources and pays for them. See Project.
Subaccounts
A subaccount is a named group inside a project with its own limits, such as one for each customer or branch. Create and change subaccounts, and suspend and resume their new calls. See Subaccount.
Alerts
The alerts Signals has raised for your organization, and the alert policies that decide when they are raised.
Audit trail
A record of the changes made in your organization: who made each one and when. List it, or read one event in detail.
Platform endpoints
The public addresses of Signals that your PBX and firewall need: where to send SIP, which ports to use and which addresses audio comes from. See Platform endpoints.