canonical: https://jentic.com/apis/mobilize.io/mobilize-io

# Mobilize API

Mobilize, now Journey by Forj, is a community management platform used by professional associations, alumni networks, and customer communities to organise members into groups and run engagement activities. The API provides 19 endpoints for managing groups, users, group members, webhooks, and activity logs under https://api.mobilize.io/v1. Authentication uses HTTP basic auth, so callers send a base64-encoded username:password pair on every request.

## For AI agents

Manage Mobilize community groups, users, group memberships, webhooks, and activities through 19 endpoints under api.mobilize.io/v1.

## Scope

Does not handle email delivery, billing, or content publishing - use for Mobilize community groups, users, members, webhooks, and activities only.

## Capabilities

- Create and update groups in a Mobilize community via /groups
- Bulk-create groups in a single call with `/groups/bulk`
- Add and remove members from a specific group through `/groups/{id}/members`
- Search and retrieve user records via /users and `/users/search`
- Register webhooks for community events at /webhooks
- Read activity logs for engagement reporting via /activities

## Use cases

### Member onboarding automation

Community managers automate new member onboarding by creating the user via /users, adding them to the appropriate group with `/groups/{id}/members`, and subscribing a webhook through /webhooks to fire downstream tasks like welcome emails. The flow keeps the Mobilize community as the source of truth for membership while letting external systems react in real time.

Example prompt: Create a user at /users for 'jane@example.com', POST to `/groups/42/members` to add her to group 42, and register a webhook at /webhooks pointed at the onboarding handler URL.

### Bulk migration into Mobilize

Associations migrating from another platform use `/groups/bulk` to create dozens of groups in a single call, then iterate over `/groups/{id}/members` to seed memberships. This drastically shortens the migration cutover compared to the per-record /groups endpoint and is the recommended path for an initial load.

Example prompt: POST a list of 25 group definitions to `/groups/bulk`, capture the returned group IDs, then iterate over each ID and POST member rows to `/groups/{id}/members.`

### Engagement reporting

Customer success teams pull /activities to build engagement dashboards that show how active each group is over time. Combined with /groups and /users, the activity stream lets the team identify dormant groups and trigger re-engagement campaigns from outside Mobilize.

Example prompt: GET /activities for the last 30 days, group results by group ID, and return the bottom-quartile groups by activity count for follow-up.

### Agent integration via Jentic

An AI assistant for a community team can search Jentic for 'add a member to a Mobilize group', load the `/groups/{id}/members` schema, and execute the call without exposing the basic auth credentials. The agent can then chain into webhook registration to keep downstream systems in sync.

Example prompt: Search Jentic for 'add a member to a Mobilize group', load the `/groups/{id}/members` schema, and execute it with group_id 42 and a new member email.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/groups` | List groups in the community |
| POST | `/groups/bulk` | Bulk-create groups |
| GET | `/groups/{id}/members` | List members of a group |
| GET | `/users` | List users in the community |
| GET | `/users/search` | Search users by attribute |
| GET | `/webhooks` | List registered webhooks |
| GET | `/activities` | List recent community activities |

## Key resources

- **Groups** — Create, list, retrieve, and bulk-create community groups
- **Users** — List, retrieve, and search Mobilize users
- **Members** — Add and remove users from specific groups
- **Webhooks** — Register endpoints to receive community event notifications
- **Activities** — Read engagement activity logs across the community

## Why Jentic

- **Setup:** Wiring the Mobilize API by hand means handling its basic auth, mapping group ids into member and invite calls, and coding bulk group operations yourself. Through Jentic you install once, import the Mobilize API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Mobilize puts the group id in the URL path (`/groups/{id}/members`), so a rule can pin your agent to one group: it can read that group's members, users, and activities. You choose the operations it may call, so bulk group creation and webhook changes are not included unless you add them.
- **Credential handling:** Your Mobilize credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list a Mobilize group's members' or 'search community users', and Jentic returns the matching Mobilize operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Circle API** — Modern community platform with spaces, posts, and members
- **Discourse API** — Open-source forum and discussion platform
- **SendGrid Mail API** — Send transactional emails to Mobilize members fetched via the API

## FAQ

### What authentication does the Mobilize API use?

Mobilize uses HTTP basic auth: send a base64-encoded username:password pair in the Authorization header on each request to api.mobilize.io/v1. Through Jentic, the basic auth credentials live in your Jentic One instance and are injected at execution time.

### Can I bulk-create groups in Mobilize?

Yes. POST to `/groups/bulk` with an array of group definitions in a single request. This is the recommended path for migrations and large community setups instead of looping over /groups.

### What are the rate limits for the Mobilize API?

The OpenAPI specification does not declare rate limits. Refer to the Mobilize developer documentation at mobilize.readme.io for current limits and back off on HTTP 429.

### How do I add a member to a Mobilize group through Jentic?

Run pip install jentic, then search Jentic for 'add a member to a Mobilize group', load the `/groups/{id}/members` schema, and execute it with the group ID and member email. Jentic injects basic auth automatically.

### Does the Mobilize API support webhooks?

Yes. Register webhook endpoints via POST /webhooks to receive notifications when community events occur, and manage existing subscriptions through the webhooks resource.

### Is the Mobilize API free to use?

Mobilize (Journey by Forj) is a commercial community platform. API access is bundled with a Mobilize subscription. There is no public free tier. Get started with Jentic One, the self-hosted execution layer.

### Can I limit what my agent is allowed to do with the Mobilize API?

Yes. Because you run Jentic One yourself, your own rules decide which Mobilize operations and credentials the agent may use. Since the group id sits in the URL path (`/groups/{id}/members`), you can pin the agent to a single group so it only reads that group's members, users, and activities. Higher-impact calls such as bulk group creation at `/groups/bulk` and webhook changes stay off unless you explicitly add them to the agent's allowed operations.