List emails sent
List the emails we sent on behalf of your account, most recently sent first.
This is the same record the emails screen in your settings shows, which is where to look when somebody says a sign-in link never arrived. Each email carries the three moments that can happen to it, when it left, when it arrived and when it came back, and one word that reads them for you.
The copy of each email is deliberately left out of this list. A page holds twenty five emails by default, and carrying the full text of each would turn a list somebody is scanning into a download. Ask for one email to read what it said.
The record belongs to the account rather than to you personally, so an email we sent to an address that has no account of its own is still listed here.
Nothing here can be written, changed or removed. The record is written as the mail leaves and updated only when the provider tells us what became of it.
This endpoint also answers QUERY, with the same parameters sent in the request body. How QUERY works.
Query parameters
Sent as JSON. Anything not listed here is ignored.
Which page to answer with.
How many emails one page holds, between 1 and 100. A number outside the range is brought back into it rather than refused.
Returns
A page of emails we sent, and how many there are in all. An account that has never had an email leave gets an empty list rather than an error.
The emails on this page. An empty list rather than an error when there are none.
One email.
Always email_sent. It names the kind of record, so a caller holding several kinds can tell them apart without looking at where they came from.
The id of this record, as a string even when it reads as a number. It is what every endpoint naming this record takes.
Everything the record holds.
Which of our emails this was, as a key such as new_login or magic_link_created, up to 255 characters. The keys come from a set the product keeps and adds to as it sends new kinds of mail, so match the ones you care about and let an unfamiliar one through rather than treating it as an error.
The subject line as it was sent, of no fixed length, or null for a record written before we kept them.
The address it went to, up to 255 characters. It need not belong to anybody with an account: what matters is that it left on behalf of yours.
Where the email got to: one of complained, bounced, delivered or sent. It is the one word you want out of the four moments below, worked out the same way the account screen works it out, and read in that order, so a complaint outranks a bounce and either outranks a delivery when a provider reports them out of order.
When it left us, as a count of seconds since 1970, or null for a record written before we kept it. This is the moment the list is ordered by.
When the provider told us it arrived, as a count of seconds, or null when nobody has told us. Null means we have not heard, not that it failed.
When it came back, as a count of seconds, or null when it has not. An email with a moment here reached nobody, whether the receiving server refused it or our provider never managed to send it at all.
When the recipient marked it as spam, as a count of seconds, or null when they have not. It is a separate fact from a bounce: the address works, the person did not want the email.
When the record was written, as a count of seconds. Usually the same second it was sent, and not the same field.
Where to find this record.
The absolute address this record is read from.
Where you are in the collection.
The page this is, counting from 1.
How many one page holds, which is the size that was asked for once it has been brought into the allowed range.
How many emails there are in all, not how many are on this page.
Rate limit
Sixty requests per minute, per user, shared by every key and device. Every answer carries the budget left in X-RateLimit-Remaining.
Keys act as you, with exactly the access you have. Make one per integration so you can revoke it alone.