The platform
Got an audience?
You run the game.
We run the pot.
Game developers, media brands, social channels and charities can all use Plucky to provide real money competitions to their audience — outsourcing payments, the prize handling, the compliance/regulation and the record-keeping, without building any of it.
We call it BaaS (Betting as a Service). You run the competition and the standings; Plucky runs the real money contest.
Registering tells us who you are. It does not create a commercial agreement — we will talk to you before anything goes live.
The integration
Three crossings of the boundary
That is the whole contract. One document we read from you, one link your player follows, one webhook we send you. You never create, close or settle a contest — there is no call that could. Taking the money, holding it, paying by your ranks: all of it happens below the line.
- 01plucky → you
Publish your competition
GET {competitionUrlBase}/{partnerCompetitionId}One document per competition: its state, entrants, closing time and table. We pull it when a player arrives and periodically while a contest is live. The same closed document is fine until the result changes; send intermediate rankings only if you want them displayed in the Plucky app.
- 02your player → plucky
Send a player across
GET /p/{slug}/competitions/{id}A signed link says who the player is on your platform and which competition they came from. Nothing more. We open the contest, take the stake, and remember them through sign-up and verification.
- 03plucky → you
Hear what happened (optional)
contest.entry.paid · contest.payout.completedOne webhook URL, one signed POST per event. When your standings go final we settle by your ranks, pay winners into their Plucky wallet, and tell you we did.
Your competition, our contest
Bring the competition and the audience. Plucky opens the contest, takes the entries, holds the money and pays by your standings.
Built for scrutiny
Every entry, prize and payment is recorded in a double-entry ledger — the same numbers we report on.
Your people, your account
Invite colleagues into your organisation and manage who can act for it.
In numbers
- 5min
- Signed-link window
- 7tries
- Webhook attempts
- 60/min
- Partner API rate
How long a signed link stays valid. We remember the player after that.
One immediate, then a backoff ladder out to 24 hours.
Per key, every route. Over it, a 429 carries Retry-After.