From your first call to the last claim.
A drop on Drop Loop is a loop, not a stampede: entries, a verifiable draw, claims, and automatic standby promotion until everything finds an owner — with your systems told at every step.
- Who acts
- You
- Customers
- Drop Loop
- mono = webhook events your endpoint receives
- 01You
Get a host
We provision a host for your organisation: its tenants, staff roles and branding. From there everything is yours to drive through the admin portal or the API — issue a scoped API key, register a webhook endpoint and send it a test ping, and you are integrated.
Your endpoint receives
- ping
- 02You
Model the item and publish the drop
Describe the item once in your catalog, with variants and stock. Then create the drop: when entries open and close, winners and backups per variant, entry cap per person, claim window, fairness pools and entry rules. Schedule it and Drop Loop opens it on time — inventory permitting.
Your endpoint receives
- item.create
- lottery.create
- lottery.opened
- 03Customers
Customers enter
From your own storefront through the public drop endpoints, or from the hosted one under your brand. Entrants verify a phone number once by SMS — each number belongs to exactly one account, so one person gets one set of odds — and choose how many entries to place, up to your cap.
Your endpoint receives
- lotteryentry.create
- 04Drop Loop
The drawing runs itself
At close, a random seed is committed as a hash and entries lock. The draw picks winners and standbys from that seed across your pools, records the entrant snapshot and every pick, and reveals the seed with the result so anyone can verify it.
Your endpoint receives
- lottery.closed
- lottery.drawn
- 05Customers
Winners claim on a clock
Each winner is notified on every configured channel and gets a time-boxed option to purchase, with a reminder before the window closes. A claim creates an order with their fulfilment choice and decrements stock; payment and shipping stay in your systems.
Your endpoint receives
- lottery.win.claimed
- lottery.win.declined
- 06Drop Loop
Standbys fill every gap
A declined or lapsed claim automatically promotes the next standby by rank, who gets a claim window of their own. The loop continues until your inventory is claimed, and you mark orders fulfilled through the API when they ship.
Your endpoint receives
- lottery.win.expired
- lottery.win.promoted
- order.fulfilled
Then it goes around again.
Most items run on a published cycle rather than a one-off launch. Followers are reminded before the next window, entrants who never won can be given better odds, and every draw leaves a record the next one can be measured against.
Ship your next drop on the API.
Get a host provisioned, an API key issued and a webhook pointed at your stack — then run a real draw end to end.