Clients call the result and the exact score before the window closes. When you settle the match, correct calls pay coins and XP, and the coins spend in the store you already run.
Prediction start, prediction end and kickoff are three separate settings. Open predictions well ahead of a match and close them early, and clients get a reason to come back on your campaign’s schedule instead of the fixture’s.
Before it opens, clients see the match with a countdown to the moment they can call it.
The window closes and every call is locked. Nothing can be entered after this point.
The match time on the client’s card, and what its countdown runs to once calls close. It does not control when predictions open.
You enter the real result. Correct calls pay out.
The form will not save a window that ends after kickoff.
Example fixture. Dates, teams and results are illustrative.
Name the match, choose two teams, set the three times, and publish. Publishing is what makes it visible to clients.
Your own name for the fixture, which is what clients see at the top of the card.
Chosen from the preset list or from teams you have made yourself.
Rich text, for the rules or the context you want beside the match.
Whether extra time counts toward the exact score.
Which tiers and roles can see this fixture.
Each fixture publishes and unpublishes on its own, so one can be pulled without touching the others.
Admin screen redrawn from the product. Example fixture; values are illustrative.
When a fixture settles you can download every prediction it took, however large the field.
The same record is available to a system you run yourself: the API reads back the winners, and every participant with the call they made and the payout they received.
Example: a settled fixture with its entries, calls and payouts. Your own figures will differ.
Two tiers. One for calling the result, one more for calling the exact score. An exact-score winner receives both added together.
Who wins?
Call the score
Score is judged based on the result in regulation time.
Perfect call! You earned
Your prediction: Brazil win 2 – 1
Either tier can carry a reward of your own instead of, or alongside, the coins and XP.
Off by default, so entering costs a client nothing. Turn it on to charge coins per submission; a correct call gets its entry cost back.
Coins land in the balance your clients already spend in your store. A fixture runs as a campaign inside the program you already have.
Example values: 100 coins and 50 XP for the result, 200 coins and 100 XP on top for the exact score. You set your own.
The API creates, updates, publishes, settles and voids fixtures.
A bulk update changes up to a hundred in one request.
Settlement answers at once with a settling state, and your system reads the result back when it finishes.
Create, settle and void take an idempotency key, so a retry returns the original answer instead of running twice.
Updates carry the version they read, so a write based on an old version is refused.
Name a trigger that fires when a client submits a call, a fixture settles, or both. It then appears in your workflows.
The API’s behavior, simplified. The status codes are the ones it returns.
Most of these are settings from earlier on the page, gathered in one place, next to the one thing the product decides for you.
A prediction window cannot end after kickoff. The form refuses to save one, so no call can be entered on a match that is already under way.
Which tiers and roles see it.
Whether entering costs coins.
What a correct call is worth, and in what.
Whether it is published at all.
These describe the controls the product gives you. Whether a program is permitted for a given entity stays your compliance team’s decision.
We set up Match Prediction inside the program you are running. Your team picks the fixtures and enters the results.
Trusted by Axi, Vantage, OANDA, Infinox, IronFX, easyMarkets, GTCFX, M4 Markets, MarketMates, IC Funded, Atmos Funded, and more.