Agent Stream

Overview#

Agent Stream is a WebSocket endpoint that lets a telephony provider point its media stream at a single URL and drive a Paladin agent run. The agent UUID in the URL selects the agent; provider-specific identifiers in the query string (for Cloudonix: Domain) tell Paladin which stored telephony configuration to use for that call. The bearer token and other credentials are never passed in the URL — they live in the stored configuration and are used by Paladin to validate the session and to issue provider API calls (hangup, transfer) during the call.

This is useful when:

• You're integrating Paladin into a SIP gateway or in-house dialer that already speaks a supported provider's streaming protocol
• You want one stable endpoint per agent rather than wiring up an inbound webhook per phone number

Endpoint#

wss://app.paladin.northmanngrp.com/api/v1/agent-stream/{agent_uuid}

{agent_uuid} is the agent's stable UUID (see Get the Agent UUID below). Use https://app.paladin.northmanngrp.com as the Paladin API base URL.

Prerequisites#

• A Paladin agent (workflow) — published or in draft is fine
• A Cloudonix telephony configuration in your Paladin organization whose domain_id matches the Domain you pass on the URL. Paladin uses the bearer token from this configuration to validate the call session and to issue provider API calls (hangup, transfer).

Get the Agent UUID#

The Agent UUID is the workflow's stable identifier — it doesn't change when versions are published.

To find and copy it in the UI, see Agent UUID.

Connect to the WebSocket#

URL parameters#

Cloudonix example#

wss://app.paladin.northmanngrp.com/api/v1/agent-stream/{agent_uuid}
  ?provider=cloudonix
  &Domain={CLOUDONIX_DOMAIN_ID}
  &callId={CALL_ID}
  &from=+15555550100
  &to=+15555550199

Use this URL inside the CXML <Stream> your Cloudonix Voice Application returns when the call needs to be bridged to the Paladin agent:

<?xml version="1.0" encoding="UTF-8"?>
<Response>
  <Connect>
    <Stream url="wss://app.paladin.northmanngrp.com/api/v1/agent-stream/{agent_uuid}?provider=cloudonix&Domain=...&callId=...&from=...&to=..."/>
  </Connect>
  <Pause length="40"/>
</Response>

The first two messages on the socket should be Cloudonix's standard connected and start events (Twilio-compatible framing). Paladin extracts streamSid and callSid from the start event payload, validates the session against Cloudonix using the bearer token from the stored telephony configuration matched by Domain, and then begins streaming audio.

Workflow run lifecycle#

When the WebSocket is accepted, Paladin:

1. Looks up the workflow by agent_uuid
2. Runs a quota check against the workflow's owning user
3. Creates a new WorkflowRun (call_type=inbound, mode=cloudonix, name WR-AGS-XXXXXXXX) with the from/to numbers stamped on initial_context, the callId/CallSid stored as call_id on gathered_context, and Domain recorded under the run's inbound_webhook log
4. Transitions the run to running and starts the agent pipeline

The run is visible under the agent's Runs tab as soon as it's minted, just like an inbound or outbound call.

Close codes#

Security notes#

• Treat the URL as a secret — the agent UUID itself authorizes the connection. Store and transmit it only over TLS, and avoid logging the raw URL in places where access is broader than your operations team.
• No bearer tokens or provider secrets are passed in the URL. Provider credentials live in the stored telephony configuration (matched by Domain for Cloudonix) and are used server-side by Paladin to validate the session and issue provider API calls.