Developers

GET/v3/fax_outbox

List outbound fax jobs

Read your outbound fax records and reconcile pages without submitting another transmission.

On this page
  1. List outbound fax jobs
  2. Read job records
  3. Reconcile pages safely
  4. Privacy and retries

List outbound fax jobs

Use an enabled MultiTEL API account over HTTPS with its configured credentials and IP restrictions. This endpoint lists outbound fax records belonging to the authenticated account. Listing does not transmit or resend a fax.

curl --silent --show-error --get --user "$API_USER:$API_PASSWORD" \
  --data-urlencode page=1 \
  --data-urlencode limit=25 \
  --data-urlencode search=0123456789abcdef0123456789abcdef \
  https://api.multitel.net/v3/fax_outbox
Outbox query parameters
ParameterRequiredMeaning
pageNoPage number, starting at 1. Default: 1.
limitNoRecords per page. Default: 25; maximum: 100. Use a positive integer.
searchNoSearches sending number, destination number and job UUID. Leading and trailing spaces are removed. It does not search status or result text.

This handler does not support date_from or date_to filters. The portal's outbox has additional filters that should not be copied into this API request. Results are ordered by creation time, newest first, without a secondary ID sort or snapshot cursor.

Read job records

Read both the HTTP result and the JSON status.code. A successful response contains response.faxes and response.pagination; the example uses fictional data. An empty mailbox returns an empty faxes array with total 0 and total_pages 0.

{
  "status": {"code": 200, "msg": ""},
  "response": {
    "faxes": [{
      "id": 13,
      "uuid": "0123456789abcdef0123456789abcdef",
      "from_number": "+12125550123",
      "to_number": "+12125550124",
      "status": "queued",
      "pages_requested": 3,
      "pages_sent": 0,
      "cost": "0.07500",
      "result_text": "",
      "created_at": "2026-10-01 12:00:00",
      "sent_at": null,
      "updated_at": "2026-10-01 12:00:00"
    }],
    "pagination": {"page": 1, "limit": 25, "total": 1, "total_pages": 1}
  }
}

id is the numeric record ID. uuid is the visible job identifier; use the job ID returned by send_fax for new submissions and retain it for status polling. The list can include older records, so do not assume every row was created through the same submission endpoint.

status and result_text carry the recorded processing state and message. This listing does not normalize them into a complete delivery-state enum. Queued means queued, not delivered. For critical documents, confirm receipt with the recipient before treating the fax as delivered or submitting a duplicate.

pages_requested and pages_sent are numeric counts. cost preserves the stored value, with a string fallback of 0.00; do not assume it has the same JSON type as the inbox cost. A queued record can already contain an estimate. Neither that value nor a list entry establishes final billing.

created_at, sent_at and updated_at are stored server-formatted values without a time-zone offset; sent_at can be null. The list omits the webhook-status field returned by the separate status endpoint.

Reconcile pages safely

Follow pagination.page, limit, total and total_pages. Pages beyond the final page can be empty. New jobs can move entries between pages while you browse. Keep job identifiers when combining pages; this endpoint has no stable-snapshot guarantee.

Privacy and retries

Outbox records contain private telephone metadata. Limit who can read them and avoid logging full responses. A missing list entry does not prove that a send request failed: check the retained job ID and portal outbox before resubmitting. A new send can create another potentially billable fax. Final worker, billing, callback and retention guarantees remain under review.