The Power Plugin (TPP) developer resources
REST API, OpenAPI and MCP for iGaming rewards: customers, catalogs, stores and orders. The linked references use the sandbox; production access is configured during onboarding.
Paste one line. Your agent writes the integration.
It installs the TPP skill — keys, wire rules, the five calls, webhooks and the hosted storefront — and reads the live OpenAPI contract before writing a single call.
Click to copy. The skill is public and carries no credentials: your agent asks you for a sandbox key when it needs one.
- 01
You paste
One public URL into Claude Code, Cursor, Codex or Gemini CLI. Nothing to install first.
- 02
It reads the contract
Step zero of the skill is fetching the live OpenAPI spec, so the agent never invents an endpoint or a field.
- 03
It writes the calls
Onboard a player, credit coins, browse the catalog, reserve an order, capture the address. Idempotency and scopes come with it.
Machine-readable
Everything an agent or engineer needs to call TPP.
OpenAPI specification
The commercial rewards API contract: typed operations, parameters and responses. Published from the rewards sandbox at /api/v1/openapi.json.
https://demo-api.thepowerplugin.com/api/v1/openapi.jsonREST API reference
Integration guide for customers, catalogs, products, stores, orders and coin balances. Use the documented scopes and sub-brand API key.
https://demo-api.thepowerplugin.com/api/v1/guideAuthentication
Bearer API keys are scoped to a sub-brand and explicit permissions, with separate test and live keys. Keep credentials on your server. Production hosts and access are confirmed during onboarding.
Scripting without a packaged CLI
Use curl with the rewards OpenAPI specification or connect an MCP client to the documented sandbox endpoint. There is no packaged TPP CLI.
Need a token or a walkthrough?
Book a demo and we issue keys, map scopes and connect your first agent.
