GET /api/faxes. Which one works depends on what reaches Faxbeep with your test.
A test appears in the list when its processing is done: usually 1 to 2 minutes after the call ends, or after your machine sends the email.
Two rules of the list
- With no
since, the list covers the last 24 hours only. So?from=Xgives an empty list ([]) if the last test of X is older. Addsinceto look further back, up to 30 days. - Encode the values.
sinceis an ISO 8601 time with an offset, for example2026-10-01T14:25:00Z. A date alone, or a time with no offset, answers 422. Use UTC withZ: it needs no encoding. Send each+, in a time offset or infrom, as%2B. The code below lets the HTTP client encode the values.
Find it
- By time
- By sender
- By email
Note the time just before you send the test. Then ask for the tests that arrived after it. Compare
page_count and received_at with what you sent: other people send tests at the same time.[] if no test matches. The fields of each test are on the page List faxes.
Check that it is yours
received_atis after the time you noted, and close to it.page_countis the number of pages you sent.sourceisphonefor a fax by phone andemailfor a test by email.fromis masked, as on faxbeep.com. See How the sender shows. You cannot compare it with your full number.view_urlopens the test on faxbeep.com, where you can see the page.pdf_urlandthumbnail_urlgive the files.
GET /api/faxes/{slug} with its slug. After 30 days, or after a removal, it answers 410.
Do not use the newest
received_at that you saw as your next since. received_at is the time a test arrived, and a long fax can appear after a newer short one. Keep since at the time you noted until your test appears.Next
Station ID
When
from works for a fax by phone, and when it is shared.Test in CI
A script that waits for your fax and stops after a time limit.
