Scenarios

Scanned documents by email

Point an office scanner at drop.media and every scan lands in your library as a private file, with your own code told when it arrives.

What you'll build

Scan → email → private file in drop.media → webhook to your system, which files it against an invoice or a customer record.

  1. Turn on the open address

    A scanner can't send from your verified address, so on the Email page in the app turn on the open address. It accepts mail from anyone who has it, so treat it like a password.

  2. Point the scanner at it, with options

    Scans are usually sensitive, so make them private. Add an expiry if you only need them until they're processed:

    acme.k7q2m9xw4p+private+90d@in.drop.media

    Set this as the scanner's scan-to-email address. Every attachment becomes a file; a multi-page PDF stays one file.

  3. Get told when a scan arrives

    On the Webhooks page, add an endpoint for file.created. Each scan arrives like this, with source set to email:

    Webhook body
    {
        "id": "1f0c6a4e-2b7d-4c1e-9a53-0d6f3e2b8c11",
        "type": "file.created",
        "created_at": "2026-11-18T09:30:00+00:00",
        "data": {
            "file": {
                "id": "7c1e4b2a-5d3f-4a8e-b6c9-0f2d8e4a1b37",
                "url": "https://drop.media/p/7c1e4b2a-5d3f-4a8e-b6c9-0f2d8e4a1b37?ref=4821&expires=\u2026&signature=\u2026",
                "name": "scan_0042.pdf",
                "mime_type": "application/pdf",
                "size": 284113,
                "visibility": "private",
                "source": "email"
            }
        }
    }
  4. Fetch the file in your handler

    The link in a private file's webhook expires after an hour. If you process it later, make a fresh one with the file's id:

    $ curl -X POST https://drop.media/api/v1/files/FILE_ID/link \
        -H "Authorization: Bearer YOUR_API_KEY" -d ttl=15m

    See Run code when a file arrives for a handler that checks the signature.

When something goes wrong

Every email is listed on the Email page with what was added and, if anything wasn't, why: a file type that isn't supported, a file over the plan's limit, too many emails in an hour. Rejected emails are also email.rejected events in Logs.