Developers
Claim Data API
Programmatic, read-only access to the same source-attributed claims the desk works from — every claim tied to the publication that reported it. Available on the Supporter plan.
Getting a key
API keys are personal access tokens tied to your Supporter account.
- Sign in and open Account → API tokens.
- Create a token and give it a name. The key is shown once — copy it then.
- Send it on every request as a bearer token. Revoke it any time from the same page.
Authentication
Pass your token in the Authorization header. All endpoints are under https://api.hindsite.space.
Authorization: Bearer hindsite_pat_xxxxxxxxMissing or invalid token → 401. Valid token on a non-Supporter account → 403.
Endpoints
GET/api/v1/me
Confirms your token works and your account is entitled. A good first call.curl https://api.hindsite.space/api/v1/me \
-H "Authorization: Bearer $HINDSITE_TOKEN"
{ "email": "you@example.com", "tier": "supporter", "authenticated": true }
GET/api/v1/events/{slug}/claims
The source-attributed claims for an event. slugis the last path segment of an event’s URL on the site. Optional limit (1–1000, default 200).curl "https://api.hindsite.space/api/v1/events/some-event-slug/claims?limit=50" \
-H "Authorization: Bearer $HINDSITE_TOKEN"
{ "event_slug": "some-event-slug", "count": 12, "claims": [ … ] }
Notes