Join a chapter as the current user, batch-add other people, look up or remove members, manage the chapter team, and submit or list chapter application survey entries through the public API.

Use this page when you add people to a chapter, manage the chapter team, or work with chapter application surveys through the public API. Shared base URL, authentication, status codes, and account rate limits stay in Using public Bevy APIs. Parameter and field details stay in Bevy API Reference.

Permissions you need

These permissions are chapter-scoped. Without the permission, Bevy returns 403.

Join as the current user versus batch-add others

Self-join means the authenticated caller asks Bevy to add themselves as a chapter member (POST /api/chapter/{chapter}/member/). It does not add someone else. That path only works when the chapter allows open join. Some chapters do not:

• Application required — the person must apply and get approved before they become a member.
• Invite only — an organizer must invite them; they cannot join themselves through this call.

For those chapters, Bevy returns 403 on the self-join path (for example, that the chapter requires an approved application or is invite only). Do not treat that as a transient failure and retry the same join call.

When the chapter requires an application, use the chapter application survey instead:

1. Get the form: GET /api/chapter/{chapter_pk}/survey/chapter_application/
2. Submit answers: POST /api/chapter/{chapter_pk}/survey/chapter_application/entry/

That creates a pending application. An organizer still reviews it before the person becomes a member. Submitting the survey is not the same as joining. Invite-only chapters need an invite or an organizer to add the person (for example through batch-add with chapters.add_chaptermember).

Batch-add chapter members

Send a JSON body with a members array. Each person needs email, first_name, and last_name. Set async to control how Bevy processes the import:

• async: false (default) — creates members in the same request and returns the member rows.
• async: true — preferred for larger imports. Returns a chapter_member_import_id and a status_url you can poll.

When you assert consent for the people you import, include signup_consent: true and a consent_reason string. Full request fields stay in Bevy API Reference.

POST /api/chapter/12/members/
Content-Type: application/json

{
  "async": true,
  "signup_consent": true,
  "consent_reason": "Imported from partner CRM with confirmed opt-in",
  "members": [
    {
      "email": "jordan.lee@example.com",
      "first_name": "Jordan",
      "last_name": "Lee"
    }
  ]
}

Batch-add calls share a dedicated ceiling of 50 requests per hour per authenticated user (scope chapter_member_create), in addition to account-wide limits in Using public Bevy APIs. When you exceed a limit, Bevy returns 429 with a Retry-After header.

Look up and remove members

• List: GET /api/chapter/{chapter}/member/
• Get one: GET /api/chapter/{chapter}/member/{id}/
• Leave yourself: DELETE /api/chapter/{chapter}/member/ — marks the caller’s active membership as departed.
• Remove another member: DELETE /api/chapter/{chapter}/member/{id}/ — requires chapters.delete_chaptermember.

Manage the chapter team

Team endpoints live under /api/chapter/{chapter}/team/. Send one team member object per create — not an array.

On create, provide an existing user ID, or an email (with optional first_name / last_name) so Bevy can create a prospective user when needed. If you send both user and email, the email must match that user. You can set a visible title and a chapter role. Full fields stay in Bevy API Reference.

POST /api/chapter/12/team/
Content-Type: application/json

{
  "email": "alex.nguyen@example.com",
  "first_name": "Alex",
  "last_name": "Nguyen",
  "title": "Chapter Lead"
}

PATCH /api/chapter/12/team/
Content-Type: application/json

{
  "order": [45, 12, 88]
}

Team create calls are limited to 100 requests per hour (scope chapter_team_create_any). When the request also sends welcome emails (send_chapter_team_emails truthy), a tighter ceiling of 30 requests per hour (scope chapter_team_create) also applies — Bevy uses the stricter of the two.

Chapter application surveys

Use survey type chapter_application in the path:

• Get the survey (questions and fields): GET /api/chapter/{chapter_pk}/survey/chapter_application/
• Submit an application entry: POST /api/chapter/{chapter_pk}/survey/chapter_application/entry/
• List entries (organizers): GET /api/chapter/{chapter_pk}/survey/chapter_application/entry/ — requires chapters.add_chaptermember. Anonymous and non-manager callers receive 403.

Submitted entries land as pending. Organizers review them in Bevy; listing entries does not accept or decline an application by itself. Unauthenticated submissions share a dedicated ceiling of 10 requests per hour (scope chapter_application_anon).