Authentication

API keys

Every request must carry an API key. Two header forms are accepted:

Authorization: Bearer thn_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

X-API-Key: thn_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Keys look like thn_{env}_{32 characters} where env is live or test. Only the first 12 characters are ever shown again in the admin UI — copy the full key when it is created.

Treat keys as passwords. Never put them in client-side code, public repositories or logs. Revoke and re-create a key if it may have leaked.

Scopes

A key only holds the scopes chosen when it was created. Write scopes do not imply read scopes — pick both if you need both.

Scope	Grants
`members:read`	Read members
`members:write`	Create and update members
`membership_types:read`	Read membership types
`membership_types:write`	Update membership types
`events:read`	Read events
`events:write`	Create and update events
`payments:read`	Read payments and dues
`community:read`	Read posts, comments and groups
`meetings:read`	Read meetings, recordings and minutes
`chapters:read`	Read chapter and association details
`roles:read`	Read roles
`tasks:read`	Read tasks
`tasks:write`	Create tasks
`projects:read`	Read projects and project tasks
`projects:write`	Create project tasks
`fundraising:read`	Read fundraising campaigns and payments
`fundraising:write`	Start donations (hosted checkout links)
`gatherings:read`	Read gatherings, tickets, attendees and orders
`elections:read`	Read elections, questions and published results
`drive:read`	Read Drive file and folder metadata
`drive:write`	Create Drive documents and upload files
`drive:download`	Download Drive files (and meeting recordings/minutes)
`contacts:read`	Read contacts
`contacts:write`	Create contacts
`activity:read`	Read the activity log
`applications:read`	Read membership applications and form templates
`notifications:read`	Read member notifications
`support:read`	Read support requests
`campaigns:read`	Read communication campaigns and delivery stats

A request with a key that lacks a required scope returns 403 insufficient_scope with details.required listing what is needed. Drive creation and uploads require drive:write and the key owner’s Drive permissions. Existing read/download keys do not gain write access automatically. See Create a Drive Document for content creation and Start a Drive Upload for prepared files.

Chapter scope

Keys are created for one chapter, or association-wide by a root-chapter admin. See Chapters for how chapter_id is interpreted for each kind of key.

Expiry and revocation

Keys may be given an expiry date at creation. An admin can revoke a key at any time; revoked or expired keys receive 401 unauthorized immediately.

Example

curl "https://api.transparencyhubnetwork.ai/api/v1/members?limit=5" \
  -H "Authorization: Bearer thn_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

{
  "status": "success",
  "data": [
    {
      "id": 42,
      "title": "Mr",
      "firstname": "Ada",
      "lastname": "Lovelace",
      "email": "ada@example.org",
      "country": "NG",
      "profilepic": null,
      "chapter_id": 9,
      "role_id": null,
      "membership_type_id": 3,
      "status": "active",
      "is_new_user": false,
      "createddate": "2026-01-15T10:00:00Z",
      "lastmodifieddate": null
    }
  ],
  "pagination": { "total": 120, "offset": 0, "limit": 5 }
}

API Reference

Members

Membership Types

Events

Payments

Community

Meetings

Organisation

Tasks & Contacts

Projects

Fundraising

Gatherings

Elections

Drive

Applications

Notifications & Support

Communication Campaigns

API keys

Scopes

Chapter scope

Expiry and revocation

Example

​API keys

​Scopes

​Chapter scope

​Expiry and revocation

​Example

API keys

Scopes

Chapter scope

Expiry and revocation

Example