Public data API

Read-only casino intelligence endpoints

The Dynamite Idea API is built for citations, research references and transparent reuse of public community intelligence. It exposes cached GET endpoints only: casino trust scores, relationship graph edges and aggregated demo-sentiment data.

No API key required GET only Cached responses Aggregate-only survey data

Casino trust scores

Public casino trust aggregates, including overall, withdrawal, bonus fairness and support ratings with review counts.

Collection endpoint https://dynamiteidea.com/wp-json/dynamite/v1/trust-scores?limit=10 Single-object endpoint https://dynamiteidea.com/wp-json/dynamite/v1/trust-scores/{casino_id_or_slug}

Entity relationship graph

Relationship-backed graph edges for one casino, provider, Ambassador or game. Optional rel filtering is supported.

Collection endpoint https://dynamiteidea.com/wp-json/dynamite/v1/relationships/di_casino/{casino_id_or_slug} Single-object endpoint https://dynamiteidea.com/wp-json/dynamite/v1/relationships/di_provider/{provider_id_or_slug}?rel=carries

Demo sentiment aggregates

Thresholded player demo sentiment for games, with individual survey responses hidden and tiny samples suppressed.

Collection endpoint https://dynamiteidea.com/wp-json/dynamite/v1/demo-sentiment?limit=10 Single-object endpoint https://dynamiteidea.com/wp-json/dynamite/v1/demo-sentiment/{game_id_or_slug}

Methodology

What the API will and will not expose

Trust scores are casino-level aggregates from published player reviews. Relationship data comes from the same canonical graph that powers profile discovery. Demo sentiment is aggregated and thresholded; individual survey answers, free-text notes and user-level session trails are never exposed.

Usage notes

Rate limits and caching

Endpoints are unauthenticated but rate-limited. Default cache freshness is five minutes, and responses include cache headers so third parties can cite stable public aggregates without hammering the site.