We’re excited to announce a major update to the Fax.Plus API that brings more control, flexibility, and reliability to our users. Whether you’re a developer building advanced integrations or a business leveraging fax for communication, these improvements make our platform more powerful and user-friendly. Let’s dive into the details of what’s new!
Key API Updates
- Directly Purchase a Fax Number from Supported Countries: We’ve made it easier than ever to expand your fax capabilities! Users can now directly purchase a fax number through the API from a wide range of supported countries using their Alohi credit.
- Return Initial Session IDs in Webhooks: With this improvement, both session IDs are returned in webhooks, allowing better tracking and management of fax attempts. This is especially useful for identifying initial and retry attempts in real-time.
- Added Offset-Based Pagination to the Inbox: We’ve added offset-based pagination to the API, making it easier to retrieve large sets of faxes or user data by skipping a specific number of records. This is a crucial improvement for those managing extensive datasets.
- Sort Faxes by Date, Sender, Recipient, and More: You can now sort faxes based on various criteria such as date, sender, recipient, and more, making it easier to manage and search through your fax records.
- Retrieve Fax Thumbnails Directly from the API: Need a visual reference? Now, you can retrieve the fax thumbnail directly through the API in JPEG format for easier document handling.
- Enhanced Permissions for Better Access Management: We’ve introduced more specific permission configurations for API tokens beyond the existing options, providing more flexible access control tailored to particular use cases.
- Revamped API Documentation: We’ve redesigned the Fax.Plus API documentation to enhance user experience. The updated version offers clear, concise, and well-structured guidance to help users seamlessly integrate faxing capabilities into their systems.
- A lot of bug fixes and improvements, including
- Fixed a bug when sending multiple webhook calls if the same number is attached to multiple users.
- Fixed limitation when passing one’s own UID. With this bug fix, developers can now pass their own UID without hitting limitations, making integrations smoother.
- Resolved issues related to retrieving a clean and complete list of users in a corporate account. No more missing or incorrect data—just a reliable list at your fingertips.
- The API now handles errors for invalid send times more effectively, ensuring that any incorrect date or time formats are flagged instantly, helping prevent sending failures.
- We’ve also added more detailed error messages for failed fax transmissions, helping developers quickly troubleshoot and resolve issues.
- and much more ...
What’s Next? These updates are now live and available to all developers working with the Fax.Plus API. As always, we remain committed to providing a seamless experience and welcome your feedback to continue improving our services.For more details on the Fax.Plus API, check out our API Documentation.