API Introduction

The public API lets association and chapter admins integrate their own tools (CRM, website, Zapier, spreadsheets) with Transparency Hub. It is authenticated with API keys that admins create in Settings → API Keys (see Managing API keys).

Base URL

https://api.transparencyhubnetwork.ai/api/v1

Test environment:

https://testapi.transparencyhubnetwork.ai/api/v1

Keys are environment-specific: a thn_test_… key only works against the test base URL and a thn_live_… key only against production.

Try it from these docs

Every endpoint page has a Try it panel. Pick the server (production or test) at the top of the panel, paste an API key into the X-API-Key field, fill in any parameters and press Send. The key is only held in your browser for the session. Use a thn_test_… key with the test server and a thn_live_… key with production.

Response format

Every response is JSON. Successful responses use one envelope:

{ "status": "success", "data": { ... } }

List endpoints add pagination metadata:

{
  "status": "success",
  "data": [ ... ],
  "pagination": { "total": 150, "offset": 0, "limit": 50 }
}

Errors always carry a machine-readable code:

{
  "status": "error",
  "code": "insufficient_scope",
  "message": "Key lacks required scope",
  "details": { "required": ["members:write"] }
}

Error codes

HTTP	`code`	Meaning
`400`	`validation_error`	Missing or malformed parameters or body (`details.missing` lists absent required fields).
`401`	`unauthorized`	Missing, unknown, revoked or expired API key. The response never says which.
`403`	`insufficient_scope`	The key does not hold every scope the operation needs (`details.required`).
`403`	`chapter_forbidden`	The key is not scoped to the requested `chapter_id`.
`404`	`not_found`	The resource does not exist in the key’s chapter.
`429`	`rate_limited`	Too many requests; retry after `Retry-After` seconds.
`4xx`	`request_failed`	The operation was rejected by business rules (message explains why).
`500`	`internal_error`	Unexpected failure. Nothing about the failure is echoed back.

Chapters

A key is either chapter-bound or association-wide:

Chapter-bound keys act on their chapter. chapter_id may be omitted; if sent it must match the key’s chapter.
Association-wide keys must send chapter_id (query parameter on reads, body field on creates) naming a chapter inside the association.

Pagination

Parameter	Type	Default	Description
`offset`	integer	0	Records to skip (≥ 0).
`limit`	integer	50	Records to return (1–200).

Rate limiting

Each key may make 100 requests per minute. Every response after authentication carries X-RateLimit-Limit and X-RateLimit-Remaining; a 429 rate_limited response also carries Retry-After (seconds until the window resets).

Timestamps

All timestamps are ISO-8601 in UTC with a trailing Z, e.g. 2026-09-14T10:00:00Z. Timestamps you send may carry any offset.

API Reference

Members

Membership Types

Events

Payments

Community

Meetings

Organisation

Tasks & Contacts

Projects

Fundraising

Gatherings

Elections

Drive

Applications

Notifications & Support

Communication Campaigns

Base URL

Try it from these docs

Response format

Error codes

Chapters

Rate limiting

Timestamps

​Base URL

​Try it from these docs

​Response format

​Error codes

​Chapters

​Pagination

​Rate limiting

​Timestamps

Base URL

Try it from these docs

Response format

Error codes

Chapters

Pagination

Rate limiting

Timestamps