The information in this article applies to customers on paid Dropbox Fax plans.
Note: The Dropbox Fax endpoints have changed from v1 to v3. The v1 endpoints will no longer being maintained. Learn more about the migration to the new v3 endpoints and the benefits for developers.
This article contains information on how to set up the Dropbox Fax API using the v1 endpoints, ensure it’s working, and buy additional fax lines if needed.
To get started using the v1 endpoints:
curl -u "[your username]:[your password]" \ "https://api.hellofax.com/v1/Accounts/[Your Account GUID]"
curl -u "myemail@hellofax.com:fakepassword" "https://api.hellofax.com/v1/Accounts/15da1c48b10c96a903eb1bac3d592fbed24ebc35"
curl "https://myemail%40hellofax.com:fakepassword%40api.hellofax.com/v1/Accounts/15da1c48b10c96a903eb1bac3d592fbed24ebc35"
The response will be a JSON representation of your account settings.
curl -u"[your username]:[your password]" \ -d "DefaultInboundFaxCallbackUrl=https://www.example.com/inboundFax" \ -d "DefaultOutboundFaxCallbackUrl=https://www.example.com/outboundFax" \ "https://api.hellofax.com/v1/Accounts/[Your Account GUID]"
Note: Incoming faxes will be POST'ed to your callback URL so you don't need to retrieve them separately.
curl -u "[your username]:[your password]" \ "https://api.hellofax.com/v1/Accounts/[Your Account GUID]/FaxLines"
The response will include the FaxLine you chose when you signed up for a premium subscription.
curl -u "[your username]:[your password]" \ "https://api.hellofax.com/v1/AreaCodes?StateCode=CA"
curl -u "[your username]:[your password]" \ -d "AreaCode=[area code from step 7]" \ "https://api.hellofax.com/v1/Accounts/[Your Account GUID]/FaxLines"
curl -u "[your username]:[your password]" \ "https://api.hellofax.com/v1/Accounts/[Your Account GUID]/Transmissions?To=[destination phone number]" \ -F "file=@myfile.pdf"
This starts the fax sending process. Receiving a 200 HTTP response doesn’t guarantee the fax will go through, a file conversion error may occur. However, once the fax's StatusCode becomes E (for Error) or S (for Success), you’ll receive a POST to the callback URL you provided in step 4. Learn more about callback events.
Possible StatusCode values:
Possible ErrorCode values (reference only when StatusCode is set to E):
Notes:
curl -u "[your username]:[your password]" \ "https://api.hellofax.com/v1/Accounts/[Your Account GUID]/Transmissions?To=[destination phone number]&From=[your fax line phone number]" \ -F file=@myfile.pdf`
For the format of the "From" value, please see the "Number" field returned by calling /FaxLines (see step 5 above).
curl -u "[your username]:[your password]" \ -F file[]="@1.pdf" -F file[]="@2.txt" \ "https://api.hellofax.com/v1/Accounts/[Your Account GUID]/Transmissions?To=[phone number in all digits]"
curl -X POST https://[your username]:[your password]@api.hellofax.com/v1/Accounts/[Your Account GUID]/Transmissions -F 'file[0]=@file1.pdf' \ -F 'file[1]=@file2.pdf' \ -F 'To[0]=[destination fax number 0]' \ -F 'To[1]=[destination fax number 1]'
Error sending fax. Status: 429; Message: Please wait. You already have at least 200 transmissions that are currently pending or transmitting.
curl -u "[your username]:[your password]" \ "https://api.hellofax.com/v1/Accounts/[Your Account GUID]/Transmissions/[Transmission GUID]"
curl -u "[your username]:[your password]" \ "https://api.hellofax.com/v1/Accounts/[Your Account GUID]/Transmissions"
If a successful POST callback is prevented by a server or network issue, Dropbox will try again at these intervals:
At each interval, Dropbox may attempt the POST multiple times if a 200 response code isn't received.
curl -u "[your username]:[your password]" \ "https://api.hellofax.com/v1/Accounts/[Account GUID]/FaxLines"
curl -u "[your username]:[your password]" -X DELETE "https://api.hellofax.com/v1/Accounts/[Account GUID]/FaxLines/2132935579"
Note: There is a known issue where the JSON in the callbacks contains a "Transaction" instead of a "Transmission". This is a typo that will be corrected in the next version of the API.
Yes, thanks!
Not really
Let us know how why it didn't help:
Thanks for letting us know!
Thanks for your feedback!