See https://dropmail.me/api/ for the most recent version of this document.

Object model

Domain
Domain name, like @dropmail.me or @10mail.org for which you can crate email Addresses.
Session
Is a server-side storage unit. It stores Addresses and incoming Emails. It has limited lifetime - when session expires all its Addresses and Mails are removed from the server. You can create multiple Sessions and attach multiple Addresses to each Session. By default session’s lifetime is 10min and extended each time you access it (by making any query that reads or writes some data to it).
Address
Email address, like user@dropmail.me, wasd@10mail.org. You can only choose Domain of the address, but “login” part (the one that comes before @) is assigned by the server automatically and is always unique and belongs to you only. It’s always attached to one of the Sessions and it is able to receive mail as long as the Session it’s attached to is not expired. If you think you might need to use this address in the future, you should save it’s restoreKey and use it later with restoreAddress operation.
Mail
Incoming email that arrived to one of the Addresses and is stored inside the Session. When Session expires, email is removed from our server completely and forever. You can request different parts of the email (like it’s plain text, headerSubject, attachments etc) or get whole raw MIME mail or downloadUrl to download the raw mail by HTTP.
Attachment
It’s only defined when received Mail has any attachments and we were able to parse it. They can be accessed via Mail.attachments field.

Workflow

Create a Session with single random Address

To create a new sessions, use introduceSession mutation.

Here we create a new session with new random address and asking the server to return session’s id, expiration time and new addresses email address

mutation {
    introduceSession {
        id,
        expiresAt,
        addresses {
          address
        }
    }
}

Fetch the incoming mail

To check for the incoming mail, you need to periodically (eg, once every 10 second) inspect the contents of the Session using session(id) or sessions fields.

Here we are requesting all the mails for a specific session.

query {
    session(id: "U2Vzc2lvbj...aLiPz_XL0lK") {
        mails{
            rawSize,
            fromAddr,
            toAddr,
            downloadUrl,
            text,
            headerSubject
        }
    }
}