arbplay

Greek Bookmaker Odds API (JSON over HTTPS)

The ArbPlay Odds HTTP API serves live and pre-match Greek bookmaker odds as JSON files over HTTPS. Requests go to the origin base URL https://api.arbplay.app and authenticate with an X-API-Key header. There are two endpoints: GET /v1/files lists the filenames your key may download, and GET /v1/data/{filename} returns the odds payload.

What you get

You need odds from licensed Greek bookmakers as structured data — for a scanner, a pricing model, a dashboard or a product of your own. The Odds HTTP API is the origin feed behind ArbPlay's own odds coverage, exposed directly over HTTPS so you can poll it yourself.

The pattern is deliberately plain. You list the files your key is allowed to read, then download the ones you want by filename. Each payload is JSON. The full contract, including schemas and error responses, lives in the OpenAPI specification rather than on this page.

Who it's for — and who it isn't

It is for developers and data buyers who want a bookmaker odds feed: anyone building an odds comparison, a model, a research dataset or a betting-adjacent product that needs Greek market prices as data.

It is not the ArbPlay sure-bet app. If you are a bettor looking for arbitrage opportunities rather than raw odds, you want the ArbPlay dashboard instead — and if you are new to the subject, start with the arbitrage betting guides. This page is about the data API only.

When you use these odds, remember the context you are operating in: betting in Greece is for adults aged 21 or older, and bookmaker terms apply to whatever you build on top of their prices.

Quick start

Every request needs your key sent in a header:

X-API-Key: YOUR_API_KEY

First, ask which files your key can read:

curl -sS -H "X-API-Key: YOUR_API_KEY" \
  https://api.arbplay.app/v1/files

Then download a payload by filename:

curl -sS -H "X-API-Key: YOUR_API_KEY" \
  https://api.arbplay.app/v1/data/site_live_stoiximan.json

Call /v1/files first

Exact filenames are policy-dependent and differ per key and per bookmaker. Always start from GET /v1/files and request only filenames it returns — do not guess paths.

To get a key, see the developer hub — the current signup path is there, along with the Postman collection if you prefer a client to curl.

Bookmakers covered

The API carries odds for the licensed Greek bookmakers ArbPlay covers. Each has its own page with the specifics that differ between them, including the company key and the filename pattern:

Live and pre-match football is the current focus, with more sports on the way. File naming follows the bookmaker and the sport, and Fonbet exposes a single combined live and pre-match file rather than separate ones.

Documentation and agent-readable sources

These are the canonical sources. Plain URLs, so both people and machines can follow them without hunting:

Marketplaces

The same origin API is also listed on third-party marketplaces: RapidAPI, JoJ API and Zyla Labs. If you subscribe through one of them, that marketplace's proxy may also expect its own secret header, and your marketplace key still maps to the same origin API. Prefer the origin documentation above as the source of truth for behaviour.

This guide documents the odds data API at api.arbplay.app. It is separate from the ArbPlay SaaS app JSON routes under arbplay.app/api/auth, /api/arbs, /api/alerts and so on — those serve the consumer product, not the odds feed.

Need an API key?

Start from the developer hub, or get in touch.