For developers & assistants
Your workflow.
Connected.
One FaxHub account for the web, mobile and integrations.
Pre-launch documentation. API access and account registration are not open yet. Planned API base: https://api.faxhub.us/v1. This separate contract describes existing ERP operations; public gateway activation is not yet verified. Launch prices do not mean every payment or faxbox workflow is available today.
Connect your account
Account access is not open yet. See launch status. When available, sign-in will use your FaxHub account. Authentication and API keys use the existing ERP account system. Integrations send X-API-Key: <id>:<secret>. Key management requires an authenticated cabinet session; an API key cannot create another key.
Prefer a key bound to the correct billing account. These existing keys are not automatically restricted to faxes or a spending budget. Keep credentials in the client’s secret store, never in a chat transcript.
Send a document
- Read the contract and verify account access.
- Upload the chosen document, then create a draft with
send_now=false. - Review the recipient, page count and actual charge with the user.
- Start transmission, retain the operation ID and check its status.
- Download the delivery receipt after a confirmed success.
Never retry a send blindly after a timeout. Payment and queue acceptance are not delivery. The current ERP flow charges before transmission; automatic failure refunds are not yet implemented.
Agent resources
Read the FaxHub skill · Documentation index · Launch prices
Agent OAuth/MCP, a dedicated quote flow and incoming-number provisioning are planned. Do not infer working endpoints from examples or marketing copy; use only available operations in the published contract and account.
Terms · Privacy · Contact · Back to FaxHub