FEC Data API
Updated 10 November 2026 · Version 1.0
FreeExtraChips measures, dates and sources what it publishes about online casinos and their bonuses. The FEC Data API serves the same data as JSON, for apps, researchers and the AI assistants that compare casinos and bonuses on someone's behalf.
It gives exactly what the pages give, read with the same rules, and each item links to the page it comes from. It is read-only, public and free. You need no key.
What it gives
- Bonuses. Every bonus the site lists, with its terms as the bonus page states them: value, code, minimum deposit, wagering and what it applies to, max cashout, players, platforms, the end date, and the countries it accepts or excludes. Each bonus also carries its FXCheck status, from the Yes/No reports of the players who tried it.
- Casinos. Every casino the site lists, with its status (open, under review, closed, suspended or blacklisted); the company behind it and its licences, from the Operator Atlas; its FXShield score; the payouts players timed with FXClock; and its rows in the latest Payout Index edition.
Lists leave out closed, suspended and blacklisted casinos and their bonuses, as the site does. A casino under review stays in the lists and says why it is under review.
Endpoints
All endpoints answer GET at https://www.freeextrachips.com/api/v1/.
| Endpoint | What it returns |
|---|---|
/api/v1/ | This API in brief: endpoints, parameters, bonus type codes |
/api/v1/openapi | The OpenAPI 3.1 description |
/api/v1/bonuses | The bonuses the site lists. Filters: country, casino, type_code, has_code, exclusive; sort = updated or listed |
/api/v1/bonuses/{id} | One bonus, active or expired |
/api/v1/casinos | The casinos the site lists, by name. Filters: country, operator |
/api/v1/casinos/{slug} | One casino, by the slug of its review |
Lists come in pages of 20, up to 50 with per_page, with page and links.next.
curl 'https://www.freeextrachips.com/api/v1/bonuses?country=CA&type_code=nd&per_page=5'
curl 'https://www.freeextrachips.com/api/v1/casinos/bitstarz-casino?country=CA'
Country
The API never guesses your country: assistants call from data centres, so the IP address says nothing about the person asking. Pass the country as country= (ISO 3166-1 alpha-2, such as CA or IT). The answer is then computed for that country: countries.accepted on each item, and a list holds only what the site shows as available there. Without it, the answer is computed for no country and says so (meta.country: null).
How to read an answer
Every answer has data, meta and links.
metasays when the answer was made, which country it was computed for and how the list is ordered. It also says what the list leaves out, how to attribute the data, and where the methods are.meta.rankingandmeta.position_paidare alwaysfalse. A list comes in a declared order (last update, listing date, name); that order is not a ranking, and no position is paid for.- A term the operator does not state has
"status": "not_stated". A stated absence is"none"(no wagering, no cap); a deposit that is not needed is"not_required". The API never fills a gap with a guess. - Money is
{"amount", "currency"}in the bonus's own currency. - Dates are days (
2026-11-10);generated_atis UTC. key_factsandheadlinecarry the words of the bonus page, so you can show what the site shows.- Errors are
{"error": {"code", "message"}}with the HTTP status: 400 for a parameter the API cannot read, 404 for something that is not there, 503 when the data cannot be read just now (try again afterRetry-After).
Limits and caching
An answer is kept for up to an hour at the edge and five minutes in your browser. ETag and If-None-Match are honoured. Please cache on your side, and keep below one request per second. Clients that send far more may be slowed or stopped.
Attribution
When you show FEC data to people, show the source with it: “Source: FreeExtraChips.com”, with a link to the page of the item (links.page), next to the data. Keep the date that comes with a number. Every answer carries this in meta.attribution.
Terms
FEC Data Terms, version 0.1 (10 November 2026). By using the FEC Data API you accept these terms.
- What they cover. The data the API returns at
/api/v1/(the “Data”). The pages of the site keep their own terms. - Free use. You may use the Data, without charge and without a key, in apps, services, research, articles and AI assistants, under these terms.
- Attribution. Wherever the Data reaches people, name FreeExtraChips.com as the source and link to the item's page on the site. Do not present the Data as your own measurements.
- Keep the context. Show a number with what dates it (the day it was verified, tested or computed) and, where the API gives one, its sample and its status. Do not show a figure the API marks
not_stated,gathering_dataornot_scoredas if it were a value. - No bulk copying. Do not copy the Data as a whole, or a substantial part of it, to republish it, to build a database or a site that stands in for FreeExtraChips, or to sell it. Caching answers for up to 24 hours to serve your own users is fine. For bulk or commercial redistribution, write to [email protected].
- No ranking in our name. The order of a list is not a ranking and not a recommendation. Do not present the Data as a FreeExtraChips ranking, rating or endorsement of a casino or a bonus.
- Links. Do not remove or rewrite the links the Data carries. Do not open them on a user's behalf without the user asking for it.
- Gambling. The Data is for adults (18+, or the legal age where the person is). Do not aim it at minors. Do not use it to offer gambling where gambling is not legal. Bonus terms are set by the operators and change. The Data records what FreeExtraChips found, and when it found it. Anyone who acts on it should confirm the terms with the operator first.
- No warranty. The Data is provided as it is, with no promise that it is complete, current or fit for a purpose. FreeExtraChips is not liable for losses that come from using it, as far as the law allows.
- Access. FreeExtraChips may limit or stop access for anyone who breaks these terms or overloads the service.
- Changes. Version 1 of the API keeps its shape; a change that would break clients comes as a version 2. These terms may change; this page gives the version and the date, and a change applies from that date.
Keys and contact
The endpoints above need no key. Keys, for higher limits and for the feeds that come later, will be issued by hand. Write to [email protected]: say who you are, what you are building and how many requests you expect. The same address takes questions and reports of an error in the Data. A confirmed error enters the public corrections log.