{
"firstname": "Ada",
"lastname": "Lovelace",
"email": "ada@example.org",
"title": "Mr",
"country": "NG",
"membership_type_id": 3,
"answers": {
"profession": "Engineer",
"graduation_year": "2010"
}
}
{
"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": "inactive",
"is_new_user": true,
"createddate": "2026-01-15T10:00:00Z",
"lastmodifieddate": null
}
}
Members
Create Member
Create a member in the chapter.
POST
/
v1
/
members
{
"firstname": "Ada",
"lastname": "Lovelace",
"email": "ada@example.org",
"title": "Mr",
"country": "NG",
"membership_type_id": 3,
"answers": {
"profession": "Engineer",
"graduation_year": "2010"
}
}
{
"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": "inactive",
"is_new_user": true,
"createddate": "2026-01-15T10:00:00Z",
"lastmodifieddate": null
}
}
Create a member in the chapter. If
password is omitted a random one is generated. Executive notifications fire as if the key’s owner had created the member in the app.
Required scope: members:write
Put them through the chapter’s onboarding
Sendmembership_type_id and the new member goes through your chapter’s normal joining process, exactly as if an administrator had added them in the app:
- an application is raised and sits in Admin → Workflow, waiting for payment or for approval (whichever your membership type is set up to do),
- any onboarding dues are created against the member,
- and your chapter administrators are notified of the new application.
membership_type_id out and you get the older behaviour: the person and their chapter link are created, with no application and no dues.
integer
The membership type they are joining. Must belong to the key’s chapter. Supplying it raises the application.
object
Answers to your chapter’s application form, as
{ "question": "answer" }. Defaults to your chapter’s form with empty values. Only used together with membership_type_id.If your chapter’s application form has required questions,
answers must include them — otherwise the call returns 400 naming the ones that are missing. Call GET /v1/application-forms first (see Applications → List application form templates) to see what your form asks for.Email addresses are unique across Transparency Hub. If the address already belongs to somebody — including in another chapter — that person is added to this chapter instead of being created again, and the reply is
200 rather than 201. If they are already in this chapter you get 409 with their member_id. In that case they are simply linked to the chapter and no application is raised, even if you sent membership_type_id — raise it for them through the app.{
"firstname": "Ada",
"lastname": "Lovelace",
"email": "ada@example.org",
"title": "Mr",
"country": "NG",
"membership_type_id": 3,
"answers": {
"profession": "Engineer",
"graduation_year": "2010"
}
}
{
"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": "inactive",
"is_new_user": true,
"createddate": "2026-01-15T10:00:00Z",
"lastmodifieddate": null
}
}
To follow the application afterwards, call
GET /v1/applications?member_id=42 (see Applications → List applications).Authorizations
ApiKeyAuthBearerAuth
Body
application/json
Put the member through the chapter's onboarding for this membership type: an application is raised (awaiting payment or approval, per the workflow), any onboarding dues are created and the chapter admins are notified. Leave it out to create the person without an application.
Answers to the chapter's application form. Defaults to the chapter's form with empty values. Only used with membership_type_id.