Settle bets automatically, as the match decides them

Why grading bets yourself is hard

Most odds APIs give you scores and leave the grading to you. That means a rule for every market type: totals and handicaps on every line, both teams to score, halves and periods, correct score, player markets, extra time, abandoned matches, a goal taken back after a video check. Each sport adds its own. One wrong rule pays the wrong customers.

The feed does that work: outcomes get their result from the feed, and you pay on it.

What you get

• A result per outcome: won, lost or void (void and push: stake back). Nothing else in the row: {id, event_id, outcome_id, result}.
• As the match decides it: a market settles once the match decides it, so many settle during play: Over 2.5 once the third goal is in, both teams to score once each side has scored. A market a video check touches waits until the check closes. Player markets settle after the match.
• Pushed and pulled: results arrive on your WebSocket channel as they happen, and /settlements?since= gives every result after the last one you processed, for catching up after downtime.
• Withdrawn results: if a result is taken back, a row with pending tells you to undo that payment; the new result follows as its own row.
• No guessing: nothing is settled because time passed. A postponed or abandoned match stays pending and your own void rules decide.

How you apply it

1. Store the outcome id with each bet when you accept it.
2. Apply each settlement row once, by its id; pay singles on won / lost / void.
3. Grade an accumulator when every leg has a result; a void leg usually counts as odds 1.00.
4. On pending, undo the payment of the result it withdraws.

Details and examples: Settlement guide, socket recipes.