Send Fax
Compose and send an outbound fax.
Headers
The tenant you are making this request on behalf of
Your api key
Body
Compose-and-send for an outbound fax.
The browser merges the cover sheet + attachments locally and uploads the
final PDF; merged_gcs_path points at that blob, which the server
validates and forwards to SignalWire as-is. attachments is still sent
for provenance — each row records the source document a page came from.
Response
Successful Response
Direction of a fax. INBOUND is defined now so inbound work later just adds rows.
OUTBOUND, INBOUND Lifecycle status of a fax. Values mirror SignalWire's LaML fax status values.
QUEUED, SENDING, DELIVERED, FAILED, CANCELED, NO_ANSWER, BUSY ^(?!^[-+.]*$)[+-]?0*\d*\.?\d*$Minimal patient reference for a fax linked to a chart (id + name only).
Lets the detail pane show "Linked to {name}" and the create-task dialog pre-fill the patient without a second fetch.
Minimal reference to the chart document a fax is filed to (id + current title + type). Lets the link dialog seed its fields with what's actually filed instead of opening blank, so re-confirming/relinking preserves them unless the user edits — no clobber from resent defaults.
The AI analysis surface on the fax detail: status + the three suggest-only cards (patient link / note / provider task).
extraction is the raw LLM output (summary, key sections, as-printed
identity, title/type hints); the suggested_* refs are the
deterministically matched rows staff can accept. *_dismissed_at
timestamps hide a card without deleting the underlying data.
