Events
file.created: a file was added to the library. Includes the file and its link.file.shared: a share link was made, and whether that was on the website, through the API or by an agent.file.deleted: a file was deleted.file.expired: a file was removed because its expiry passed.
POST /hooks/drop
Drop-Event: file.created
Drop-Delivery: 6f1c…
Drop-Signature: t=1795080600,v1=5d2e…
{"id": "6f1c…", "type": "file.created", "created_at": "2026-11-18T09:30:00+00:00",
"data": {"file": {"id": "…", "name": "SKU-10442-front.jpg", "url": "https://cdn.drop.media/acme/…"}}}
Why it's useful
Combined with email and SFTP, webhooks turn drop. into an intake point for files from anywhere. A photo studio uploads over SFTP, a supplier emails a spec sheet, an agent generates a banner. Your endpoint gets the same file.created event each time and can:
- attach the image to a product in your store or PIM,
- import a CSV export into your own database,
- post a message in your team chat,
- or pass the file to an automation tool that accepts webhooks.
Verifying and retrying
Each endpoint has its own signing secret. The Drop-Signature header holds an HMAC-SHA256 of the timestamp and raw body, so check it before you trust the payload and reject old timestamps. Reply with any 2xx status within 10 seconds. Anything else is retried after 1 minute, 5 minutes, 30 minutes, 2 hours, 6 hours, 12 hours and 24 hours. Retries carry the same Drop-Delivery ID, so you can ignore duplicates.
[$t, $sig] = sscanf($request->header('Drop-Signature'), 't=%d,v1=%s');
$expected = hash_hmac('sha256', $t.'.'.$request->getContent(), $secret);
abort_unless(hash_equals($expected, (string) $sig) && abs(time() - $t) < 300, 400);
The Developers page shows recent deliveries, lets you retry one by hand, and can send a test ping event.