August 12, 2026

Buy the Napster API directly

You no longer need an Azure subscription to use the Napster API. Sign up at napster.com/developer, and you can create an API key and start building right away:

• New accounts start with $6 of free credits — roughly 100 minutes of conversation.
• When the credits run out, top up your balance with a card from the dashboard — or enable auto-recharge and never think about it.

The Azure Marketplace path remains available if you prefer billing through your Azure subscription.

Your agent can place outbound SIP calls

SIP is no longer answer-only. Start a call with POST /public/sip-connections/{sipConnectionConfigurationId}/call — the agent dials the number and, optionally, speaks first:

curl -X POST https://companion-api.napster.com/public/sip-connections/$SIP_CONNECTION_ID/call \
  -H "X-Api-Key: $NAPSTER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "destination": "15551234567",
    "initialSpeech": "Hi, this is Ava from Acme — I'\''m calling about your recent order."
  }'

See SIP — Outbound calls.

Session metadata is always sent to WebSocket tools

The initialize message your functions server receives at session start now always includes a metadata object carrying the connection's context — tags, external_client_id, and external_client_profile. Your server can tie the session to your own user, tenant, or profile without a separate lookup, and without any per-tool opt-in.

See WebSocket Tools — Session metadata for the message shape and field mapping.

Control what a session does when your tool server is slow or down

WebSocket-based tools have a new connectionBehavior setting with two flags:

• connectionBehavior.waitBeforeStart — the session waits for your tool's socket to fully connect before starting.
• connectionBehavior.abortOnFailure — the whole session is aborted if your tool's socket fails to connect.

Both default to false — and that is a behavior change worth checking your integration against: previously every session waited for tool sockets and died if one failed to connect. Sessions now start fast and survive a failed tool connection unless you opt back in.

See WebSocket Tools — Connection behavior.

See how each tool's connection went

Session details now include functionMetrics — a per-tool record of the WebSocket connection lifecycle: when it started connecting, when it connected, whether it failed (and why, as { code, message }), or whether the user left before it finished connecting.

See Sessions — Tool connection metrics.

Sessions that never start are now failed

The session status field has a fourth value: pending, started, closed — and now failed, for sessions whose connection was never established. Failed sessions appear in the session list alongside the others; use the status field to separate them in your analytics.

See Sessions — Session fields.

Agent limit per organization

Organizations can now hold up to 100 agents. Creating an agent past the limit returns a 409 with code AgentLimitExceeded. The limit can be raised per organization — contact us if you need more.

See Limits — Agents per organization.