---
title: "Get Call Transfer Flow"
method: GET
path: "/calls/{call_id}/transfer-flow"
tags: ["Calls"]
---

# Get Call Transfer Flow

`GET /calls/{call_id}/transfer-flow`

Reconstruct a transferred call's flow: our AI → transfer destination →
the PBX queue/agent hop chain (intake → fallback → who answered).

Debugging view for developers, and for customer admins when the
customer's transfer_flow_admin_enabled call-detail setting is on. PBX
hops come from a live read-only NetSapiens CDR read; customers without
NetSapiens (or an untransferred call) get just the our-side segment.

## Path parameters

- `call_id` string, uuid, required

## Response `200`

Successful Response

- TransferFlowResponse — Developer-only transfer-flow reconstruction for a call.
  - `transferred` boolean, required — Whether the call was transferred at all
  - `hops` TransferFlowHop[] — Ordered flow hops
    - `source` string, required — 'openintake' (our side) or 'pbx'
    - `timestamp` string, date-time, nullable — When this hop started
    - `label` string, required — Human-readable hop, e.g. 'Intake Dept' or 'AI Receptionist'
    - `action` string, nullable — Verb/action, e.g. 'Transferred', 'Queue dispatch'
    - `queue_name` string, nullable — PBX queue name if this hop rang a queue
    - `agent_name` string, nullable — Staff member who was rung/answered
    - `answered` boolean, nullable — Whether this hop was answered
    - `talk_seconds` integer, nullable — Seconds of conversation on this hop
    - `detail` string, nullable — Extra context, e.g. release reason or transfer outcome
    - `inferred` boolean — Hop reconstructed from the forward-rule chain at capture time (the PBX emits no CDR row for unanswered intermediate queues)
    - `post_answer` boolean — Hop after the first answered PBX hop (staff-side onward transfers); the UI collapses these behind an 'additional transfers' toggle
  - `pbx_available` boolean, required — Whether PBX-side hops could be resolved (NetSapiens configured)

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/openintake/apis/fastapi.md) · [All operations](https://skmtc.dev/openintake/apis/fastapi/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/openintake/fastapi/revisions/b642b91e0a5c/schema)