Overview
Use the Medsender API v3 to send and receive the same fax documents your organization uses in the web app.
Already enrolled? Use a test key for simulated v3 sends. Existing /api/v2 integrations use the legacy v2 quickstart.
Where self-serve is offered for your account, verify email, complete the BAA, choose your fax number and add a card. Successful activation links your organization automatically. Enterprise and manual integrations coordinate enrollment with Medsender. Signup or key creation alone does not enable v3. After activation or enrollment, test keys support simulated sent-fax operations; received-fax operations require live keys.
Access and prerequisites
- Use a developer credential with a confirmed, active account and approved BAA coverage under Medsender’s existing eligibility policy. The live examples use a Bearer live key. Test keys support simulated sent-fax operations after the same enrollment; received-fax operations require a live key. Organization API credentials cannot authorize v3.
- Your developer account must be explicitly linked to the organization. Where self-serve is offered for your account, successful activation creates this link automatically after email verification, BAA completion, number selection and card setup. Enterprise and manual integrations coordinate the link with Medsender. Access is organization-wide, including department and private fax documents, independent of an employee’s inbox permissions. Web-user permissions remain separate.
- Sending and archiving require a configured active organization member for attribution. Removing that member prevents those writes; the organization grant still controls reads.
- Sending requires an active fax number owned by the linked organization. Where self-serve is offered for your account, choose your included number before activation and manage its HTTPS callback on Fax Numbers once live; additional purchases require Medsender support. Enterprise and manual integrations coordinate number setup and incoming routing with Medsender. Configure the live webhook secret for callback verification. Do not provision or move developer-owned numbers through v2 expecting v3 access.
These examples send real faxes with live credentials. Replace the numbers with your configured sender and an authorized destination. Use only an approved sample document.
Quickstart: Send your first fax
After successful self-serve activation or Medsender-coordinated enterprise enrollment, use the live key and API base configured above. Replace the sample numbers and use an approved PDF.
Save the returned faxId. A 201 response accepts the send; it does not confirm delivery. Follow polling and download and reconcile the terminal callback. A polled failure may still be retried automatically. Do not repeat a POST after a timeout or polled failure without reconciling the outcome: it can send another fax.
Fax workflows
- Sent Faxes: upload, send, list, poll and download.
- Received Faxes: list, download, archive and unarchive native incoming faxes.
- Endpoint Catalog: v3 fax operations and organization number provisioning.
Existing v2 integrations, the v2 test quickstart, fax-number APIs and other v2 resources are documented under Legacy API (v2). V3 does not automatically migrate numbers or fax history. LLM Inference has its own API contract.