Introducing the PLLAY Partner API: Infrastructure for Platforms, Not Just an App
The logic that makes a PLLAY prediction pool work was never actually specific to PLLAY's own interface. This is the start of making it reusable.
PLLAY started as an app: a place where a creator runs a prediction pool and their audience plays. But the logic that makes a pool work — accepting entries, weighting them by skill, settling against a real outcome, splitting revenue, paying out — was never actually specific to PLLAY's own interface. It's infrastructure, and this month we started building the API surface that lets another platform use it.
This is early. What shipped is the scaffolding — the internal groundwork for a partner-facing API and the beginnings of the abstraction layer that will let it work across payment providers and, eventually, across regions — rather than a finished, publicly documented integration a partner can pick up today.
The reason to build it this way, foundation-first, is that the hard part of a partner API isn't the endpoints — it's making sure the guarantees underneath them (a pool settles correctly, fraud gets caught, money moves to the right account) hold up for a partner's traffic the same way they hold up for PLLAY's own. We built and hardened those guarantees for our own app first; the API work is what makes them reusable.
Alongside the API scaffolding, we also started laying groundwork for supporting creators and audiences outside the U.S. — compliance and localization work that has to exist before a partner integration can go beyond a single market.
None of this changes what a PLLAY creator sees today. It's the first step toward PLLAY being something a platform can build on, not just something a fan visits — and it'll stay foundational work, visible mostly in what becomes possible later, for a while yet.