PadBets Data & Markets: two APIs, different jobs

PadBets Data supplies information about padel. PadBets Markets supplies model probabilities & fair prices. The distinction helps a business choose the right input for its product.

Data: records you can build with

The Data API covers fixtures, scores, results, players, rankings, bookmaker odds & historical data. A publisher might use it to build match pages; an operator might connect it to a research view or its own reporting.

Begin with the fields your product needs: the event & player identifiers, match status, score, observation time & the way corrections are delivered.

Markets: probabilities & fair prices

The Markets pricing API covers match winner, set betting, total games & game handicaps. It supplies model probabilities & fair prices, with operators applying their own margin.

A fair decimal price is the reciprocal of the probability. For example, an illustrative 50% model probability gives a fair price of 2.00: 1 ÷ 0.50. This is a model estimate before an operator adds margin, not a bookmaker quote.

Choose a concrete first use

Suppose a media site wants fixtures & results for a tournament. Data supplies the records. If it wants an embeddable display, Widgets provides a separate route for scores, fixtures & odds.

An operator building a pricing workflow has different questions for Markets: which markets & lines it needs, when prices update, how estimates are identified & how its margin will be applied.

Agree the practical details

• Coverage: the competitions, fields & markets required.
• Freshness: collection times, update intervals & delayed-data behaviour.
• Identity: consistent player, event & selection identifiers.
• Delivery: access limits, support & correction handling.
• Usage: what the agreement allows you to store, display or redistribute.

Explore PadBets Data & PadBets Markets. A sample response & one agreed test journey make a useful starting brief.