> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developers.hellosign.com/llms.txt.
> For full documentation content, see https://developers.hellosign.com/llms-full.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.hellosign.com/_mcp/server.

> Learn how Dropbox Fax API can be used to send faxes.

# Fax

Fax endpoints are used to send new faxes, as well as to retrieve information or delete previously sent faxes.

The Fax object returned by these endpoints can be used to reference request-specific data including the recipient phone number or email address, cover page message, and timestamps for when the fax was sent.

To sign up and send faxes, contact support to upgrade to the Fax API plan: <a href="https://faq.hellosign.com/hc/en-us/requests/new" target="_blank">Submit a Ticket</a>

## Fax Endpoints

| Summary                                              | Endpoint              | Description                                                                 |
| ---------------------------------------------------- | --------------------- | --------------------------------------------------------------------------- |
| [Get Fax](/api/reference/operation/faxGet/)          | /fax/\{fax\_id}       | Return the Fax specified by the `fax_id` parameter.                         |
| [List Faxes](/api/reference/operation/faxList/)      | /fax/list             | Return a list of Faxes that you can access.                                 |
| [Download Files](/api/reference/operation/faxFiles/) | /fax/files/\{fax\_id} | Obtain a copy of the current documents specified by the `fax_id` parameter. |
| [Send Fax](/api/reference/operation/faxSend/)        | /fax/send             | Create and send a new fax with the submitted documents.                     |
| [Delete Fax](/api/reference/operation/faxDelete/)    | /fax/\{fax\_id}       | Delete the fax specified by the `fax_id` parameter.                         |

## Fax Status

Making a request to the [Send Fax](/api/reference/operation/faxSend/) starts the sending process. Receiving a 200 HTTP response does not guarantee the fax was sent successfully for a number of reasons (i.e. a file conversion error or busy signal).
Once the `status_code` updates, you’ll receive a POST to the [callback URL](/docs/fax/v3migration/#callbacks) you provided.

## Fax Status Codes

List and details of possible Fax status codes that can be returned:

| Status         | Description                      |
| -------------- | -------------------------------- |
| `transmitting` | Transmitting/sending             |
| `success`      | Successfully sent                |
| `on_hold`      | On hold - account is unconfirmed |

## Fax Error Codes

List and details of possible Fax errors that can be returned:

| Error                   | Description                                                                                          |
| ----------------------- | ---------------------------------------------------------------------------------------------------- |
| `error_busy`            | Busy signal                                                                                          |
| `error_no_answer`       | No answer                                                                                            |
| `error_could_not_fax`   | Unable to fax (usually due to a bad connection)                                                      |
| `error_disconnected`    | Line disconnected or unreachable                                                                     |
| `error_bad_destination` | The line is has been banned (should not happen for US numbers)                                       |
| `error_unknown`         | Unknown error (usually occurs if someone picks up the line or an error occurred during transmission) |
| `error_file`            | Error processing the provided file                                                                   |