iFax API Documentation
All calls to the iFax API should be made tohttps://api.ifaxapp.com/v1, which remains current with the latest minor updates.
Getting Your API Key
You can find your API key on the Settings page of your dashboard. All iFax API responses are formatted in JSON.HTTP Methods
Since our API is RESTful, each API call requires a specific HTTP method to indicate the type of operation to be performed.Standard HTTP Methods
Method Simulation
Some HTTP clients don’t support all HTTP methods. Use the POST method with the_method parameter:
Authentication
Most API calls require authentication via theaccessToken header.
HTTP Authentication
Data Formats
All API calls return JSON responses by default.API Objects
Fax Object
The fax object represents a fax job in the iFax system.
Example Fax Object:
Webhooks
Webhooks allow iFax to update you in real-time about the status of your faxes.Specifying Webhook URLs
Provide a valid webhook URL on your webhook settings page, e.g.,https://www.example.com/ifax_webhook.
Postflight Webhooks
Postflight webhooks are triggered when a fax completes, regardless of success.Webhook Retries
If a webhook fails, it will automatically retry up to 5 times with exponential backoff:Fax Statuses
Error Codes & Messages
Send Fax
Endpoint:POST /customer/fax-send
Base URL: https://api.ifaxapp.com/v1
Request Headers
Request Parameters
Fax Data Array
Each item infaxData should include:
Sample Request
Sample Response
Request Restrictions
Cancel Scheduled Fax
Endpoint:POST /customer/fax-cancel
Cancel a fax that has been scheduled for future delivery.
Request Parameters
Sample Request
Sample Response
Resend Fax
Endpoint:POST /customer/fax-resend
Resend a previously sent fax.
Request Parameters
Sample Request
Sample Response
Fax Webhook Events
Webhook URL: Configured in your dashboard settingsWebhook Payload
When a fax completes, iFax sends a POST request to your webhook URL with the following payload:Webhook Security
Always verify the webhook signature to ensure the request came from iFax. The signature is sent in theX-iFax-Signature header.
Rate Limiting
iFax API implements rate limiting to ensure fair usage:
If you exceed rate limits, you’ll receive a
429 Too Many Requests response.
Response Codes
Best Practices
Always use file URLs over base64 encoding for better performance and lower bandwidth usage.
- Error Handling - Implement proper error handling and retry logic
- Webhooks - Always verify webhook signatures before processing
- Rate Limiting - Implement backoff strategies when approaching rate limits
- Scheduling - Use
send_atparameter to batch faxes during off-peak hours - File URLs - Provide publicly accessible HTTP/HTTPS URLs instead of base64 data
- Monitoring - Log all API calls for debugging and auditing purposes
Support
For additional help, contact support at:- Email: support@ifaxapp.com
- Website: https://ifaxapp.com/support