API reference

GET /v1/three_way_calls/:bridge_id · Get a three-way call

Both legs of a three-way call. They're billed and tracked separately, with one connection fee per person.

Request

text
GET https://api.spoofey.com/v1/three_way_calls/:bridge_id
Path param Notes
bridge_id The bridge_id returned by POST /v1/three_way_calls.

Example

bash
curl https://api.spoofey.com/v1/three_way_calls/3b7e1c2a-... \
  -H "Authorization: Bearer sk_live_..."

Response

json
{
  "bridge_id": "3b7e1c2a-...",
  "status": "completed",
  "created_at": 1789800000000,
  "legs": [
    { "id": "...", "status": "completed", "user": "14165557890", "sees": "18005551234", "rate_per_minute": 0.9, "billed_seconds": 62, "billed_credits": 1.4, "answered_at": 1789800005000, "ended_at": 1789800067000 },
    { "id": "...", "status": "completed", "user": "18005551234", "sees": "14165557890", "rate_per_minute": 1.1, "billed_seconds": 62, "billed_credits": 1.71, "answered_at": 1789800006000, "ended_at": 1789800067000 }
  ]
}

Each leg's user is that party's own number; sees is the caller ID they were shown (the other party's number).

Errors

Errors come back as {"error":{"message":"...","code":"..."}}. See API errors and rate limits for every status code and the rate limit.

Was this helpful?Your answer helps us improve this page.
Still stuck?Ask Spoofey AI about your exact case, or a person on our team will reply by email.
Last modified on September 25, 2026 · 1 min read
Edit