API access
Tell us about the drop
Your organisation, what you’re dropping and roughly how many entrants you expect — and whether you’ll use the hosted storefront, build your own, or go headless.
API access for your organisation, an integration question, or a demo of a real draw — it all starts with one email, and it is answered by the people who built the platform.
What happens next
Within one business day, from an engineer who can actually act on it — not a ticket bot.
Tenants, staff roles and branding, then your first scoped API key and a webhook endpoint pointed at your stack.
End to end: entries, the committed seed, the draw, claims and standby promotion — verifiable from the first one.
Never send API keys, passwords or codes — Drop Loop will never ask for them.
A little context up front turns one reply into the answer.
API access
Your organisation, what you’re dropping and roughly how many entrants you expect — and whether you’ll use the hosted storefront, build your own, or go headless.
Integration
The endpoint or event name and, for a webhook, the delivery ID from its header — every delivery is stored exactly as sent, so we can trace it.
A draw
The drop’s name and roughly when it ran. Every draw keeps its audit record, so we answer from the record rather than from memory.
Most first questions are covered in one of these three places.