Export call trace by link

Exports a call's trace as a file: the ladder diagram as SVG, or the event rows as CSV. Name the call by its SIP call IDs and a time window, as in GET /sipflow, or send a share key k for a stored trace. It takes the same fields as POST /sipflow/export, as query parameters, so a link can embed the diagram: GET /sipflow/export?k=<key> renders a shared trace as an image.

Super User and Super User Read Only see every trace. A Reseller sees calls that have a party domain (originating, terminating, or by) in its territory. Office Manager and the other domain-tier scopes see calls that have their own domain as a party domain. User-tier scopes see only calls where their own user is the originating or terminating party. A call outside your scope answers the same 404 as a call that does not exist. A scope without the call-trace privilege gets 403; by default Office Manager, Reseller, Super User, and Super User Read Only hold it. Every call ID you send must match a CDR in your scope inside the window; the rest are ignored, and if none remain the answer is 404. A share key needs no token and exports read-only; with a token, the stored call must be in your scope.

The answer is a file in the media type export_format picks:

image (the default): the SVG ladder diagram, image/svg+xml, sent inline

csv: the event rows with a header row, text/csv, as an attachment

base64: base64 of the PHP-serialized raw rows, text/plain. The cluster's servers use this format with each other; integrations should use csv. Times in CSV and base64 rows, and in the call_trace_text block headers, are YYYY-MM-DD_HH:MM:SS in UTC (an underscore, no offset); the millisecond Unix time is the UnixTsm column.

For JSON renderings, use GET /sipflow.

Example requests

SVG diagram:

GET /sipflow/export?start_time=2026-09-01T14:30:00+00:00&end_time=2026-09-01T14:34:10+00:00&callids=0f1e2d3c4b5a69788796a5b4c3d2e1f0@192.0.2.10

Shared trace as SVG: GET /sipflow/export?k=202609019f86d081884c7d659a2feaa0c55ad015

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

image/svg+xml

The export. The stored type is the default, image/svg+xml; export_format=csv answers text/csv and export_format=base64 answers text/plain, as the description lists.

curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/sipflow/export?start_time=2026-09-01T14%3A30%3A00+00%3A00&end_time=2026-09-01T14%3A34%3A10+00%3A00&callids=0f1e2d3c4b5a69788796a5b4c3d2e1f0%40192.0.2.10&export_format=image&k=202609019f86d081884c7d659a2feaa0c55ad015&search_callids=yes&margin=10&ds=diag&show_attendees=no' \ --header 'Authorization: Bearer <token>'

Request

Responses