Send Fax
Authentication
Headers
Unique key for one logical send. Use 1–128 ASCII letters, numbers, periods, underscores, or hyphens. Reuse it only with the identical from, to, mediaUrl, and effective quality; any change returns 409.
Request
Fax-enabled, non-sandbox number owned by your HIPAA team, in E.164 format (+ followed by 10–15 digits; the first digit cannot be zero). The number must remain enabled and configured through preparation. Fax sending is unavailable to development-mode teams.
Recipient fax number in E.164 format (+ followed by 10–15 digits; the first digit cannot be zero).
Public HTTPS URL on port 443 for one PDF, TIFF, JPEG, PNG, DOC, DOCX, RTF, or TXT document. The URL must contain 9–8,192 characters, including signed query parameters. Usernames, passwords, redirects, private or local addresses, IPv6-only hosts, and non-200 responses are rejected.
The origin must complete the download within 30 seconds and return no more than 16 KiB of response headers. If present, Content-Length must be a non-negative decimal integer no greater than 50,000,000, and Content-Type must be one of the accepted types listed in the endpoint description. The source and processed document must each be no larger than 50,000,000 bytes. The document must contain 1–3,500 pages.
A permitted URL extension or Content-Type is not sufficient: file signatures and structure must identify a supported format. JPEG/PNG images are limited to 250,000,000 pixels and TIFF images to 2,000,000,000 pixels. DOCX archives must be non-encrypted and free of macros, ActiveX controls, embedded objects, symbolic links, and unsafe paths; ZIP64 and multi-disk containers are not accepted. See the endpoint description for the complete DOCX archive and document-processing limits.
Rendering profile applied to the fax. Defaults to HIGH. Higher-detail profiles can take longer to process but do not change the $0.025 per-page price or any document limit.
Response
OUTBOUND for faxes sent by your team or INBOUND for faxes received by your team.
Current state of the fax:
PREPARING: Pinnacle is downloading, validating, converting, splitting, or archiving the document.SUBMITTING: The fax is waiting for transmission to start.SUBMISSION_UNKNOWN: Transmission may have started, but Pinnacle cannot confirm it. The fax is not retried automatically.QUEUED: The outbound fax is queued for transmission.PROCESSING: The outbound document is being processed.SENDING: The outbound fax is being transmitted.RECEIVING: An inbound fax is in progress.DELIVERED: Every outbound part was delivered.RECEIVED: The inbound fax was received and archived.FAILED: Preparation, submission, or delivery failed.partialContentindicates whether any pages were transmitted.CANCELLED: The outbound fax was cancelled before transmission started.
Stable failure category, or null when no failure is recorded:
MEDIA_PREPARATION_FAILED: The source was unavailable, invalid, unsupported, over a limit, or could not be rendered.MEDIA_PREPARATION_INTERRUPTED: Preparation could not be completed after retries.INSUFFICIENT_CREDITS: The team’s available credits could not cover the prepared page count.SUBMISSION_UNCONFIRMED: Transmission may have started, so Pinnacle will not retry automatically.SUBMISSION_REJECTED: Transmission could not start.DELIVERY_FAILED: Delivery failed or a transmitted part did not match the expected page count.
Settled fax cost in USD, calculated at $0.025 per final transmitted page. Quality does not change the rate.
Credit reserved after document preparation for an unsettled outbound fax, in USD. This equals $0.025 multiplied by the prepared page count, regardless of quality, and is zero while status is PREPARING.
PENDING while a reservation or uncertain submission remains open; SETTLED after final charging, refund, or cancellation.

