For researchers and agents

Find. Compare.
Keep the evidence.

Use published product profiles in your research workflow. The read-only API returns stable product IDs, canonical profile URLs, source records and explicit gaps in the evidence.

Build a shortlist Try the product API OpenAPI specification →

A research workflow

Find a product type and inspect its comparison criteria.
Search products by type, supplier or words in their public profile. Follow the pagination links to continue.
Read each product’s facts and linked evidence. Keep unknown values separate from negative findings.
Compare up to three products of the same type, then export the comparison as JSON or CSV.

In the browser, you can save products and supplier profiles, write requirements, and export your shortlist with its source records. A shared shortlist opens as a separate view until you explicitly save it. Requirements are stored in your browser; the share link includes them when you choose to share.

Endpoints

Base URL: https://igamingdiscovery.com/api/discovery/v1. No API key is needed. Only GET, HEAD and OPTIONS are supported.

Endpoint	Purpose
`/product-types`	Published product types, canonical URLs and comparison criteria.
`/products`	Search with `q`, `type`, `supplier`, `sort`, `page` and `limit`. Fetch a selection using comma-separated `slugs`.
`/products/{slug}`	One published product with facts, sources and review dates. An unavailable profile returns 404.
`/suppliers`	Supplier summaries. Filter by `q`, `category` or `slugs`; use the same pagination parameters.
`/compare`	Pass `type` and 1–3 comma-separated `products`. Use `format=json` or `format=csv`.

Try a query

GET /api/discovery/v1/products?type=crm-platforms&limit=3

GET /api/discovery/v1/products/gamanza-engage-crm

GET /api/discovery/v1/compare?type=crm-platforms
    &products=gamanza-engage-crm,solitics-customer-retention
    &format=csv

Lists default to 24 items and accept a maximum of 50 per request. Page numbers start at 1. Use the response’s pagination.next URL until it is null. Product sorting accepts popularity, name or supplier; suppliers accept popularity, name or updated. An explicit slug selection follows the requested order.

How to read the evidence

id is the stable catalogue product ID. Use canonicalUrl when citing the profile and source URLs when attributing a supplier claim.
Each fact has status: recorded or not_recorded. Missing values are null; they do not mean a feature is unavailable.
A recorded value is an editorial record, not a certification or independent product test. Check the scope and limitations in the value and source record.
sourceUrl identifies the evidence linked to a fact. It can be null for editorial summaries. A profile’s source list does not imply that every source supports every fact.
sources[].checkedAt records when a source was reviewed. reviewedAt is the profile review date; partial fact updates can have later source dates.
Popularity describes estimated supplier commercial reach. It is not product quality, customer satisfaction or adoption of that particular product.

CSV exports contain one row per product, criterion and linked source record, including gaps. Text that could be interpreted as a spreadsheet formula is prefixed with an apostrophe.

Invalid parameters return 400. Temporary catalogue failures return 503; retry with backoff. The API exposes published records only. Saved exports are snapshots and should be refreshed before a purchasing decision.

Read the comparison method →