canonical: https://jentic.com/apis/api.mobilize.io/mobilize # Mobilize API Jentic publishes the only available OpenAPI specification for Mobilize API, keeping it validated and agent-ready. Mobilize (now Journey by Forj) is a community engagement platform for member-based organisations such as professional associations and alumni networks. The API exposes 19 endpoints covering groups, group members, users, user search, webhooks, and activity logs. It is well suited for syncing member directories, automating group membership changes when CRM data updates, and feeding engagement events into analytics pipelines. ## For AI agents Manage Mobilize community members, groups, and activity: list and create groups, add and remove members in bulk, manage users, and read activity logs and webhook configurations. ## Scope Does not handle event ticketing, payments, or email campaign delivery - use for community user, group, and activity management only. ## Capabilities - List, create, retrieve, and update groups individually or in bulk batches - Add, update, and remove members within a specific group with per-member detail - List, create, retrieve, update, and remove users in the community directory - Search the user directory by name or other profile attributes - Read existing webhook configurations to confirm where Mobilize events are delivered - Pull user activity logs to feed engagement scoring and analytics dashboards ## Use cases ### Member Directory Sync Sync a Mobilize community directory with the source-of-truth CRM (HubSpot, Salesforce) so that joining or leaving the organisation triggers the right group membership in Mobilize. Use /users to maintain the user record and /groups/{id}/members to attach group membership. Most teams ship the sync in 3 to 5 days with bulk endpoints to handle backfills. Example prompt: Pull the latest member list from the CRM, call PUT /groups/bulk to update Mobilize groups, then for each new member call POST /groups/{id}/members to attach them to their chapter group. ### Engagement Analytics Pipeline Pull user activity logs via /activities and load them into a data warehouse to compute engagement scores, churn risk, and chapter health metrics. Combine activity counts with /users data to attribute engagement to specific cohorts. Effort is typically a week including incremental loading. Example prompt: Pull /activities for the last 24 hours, group rows by user_id, and write the daily engagement counts to a BigQuery table for dashboarding. ### Bulk Chapter Reorganisation When an association reorganises chapters, use POST /groups/bulk and PUT /groups/bulk to create or rename groups, then move members between them via /groups/{id}/members. The bulk endpoints make a one-shot reorganisation tractable without rate-limit issues. Example prompt: Call POST /groups/bulk to create the 12 new chapter groups, then for each affected member call POST /groups/{id}/members on the new group and DELETE on the old group. ### AI Community Manager An AI agent acting as a community manager can answer questions like 'how many active members in the Boston chapter' or 'add this batch of new members' through Jentic. Mobilize Basic Auth credentials live in your Jentic One instance and never enter agent context. Setup is under an hour. Example prompt: Use Jentic to search for 'add members to a group', load the POST /groups/{id}/members schema, and execute it for each new member parsed from the user-supplied CSV. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /groups | Retrieve all groups | | POST | /groups | Create a single group | | POST | /groups/bulk | Create multiple groups | | POST | /groups/{id}/members | Add a member to a group | | DELETE | /groups/{id}/members/{memberId} | Remove a member from a group | | GET | /users/search | Search users in the community directory | | GET | /activities | Get user activity logs | ## Key resources - **Groups** — List, create, update individually or in bulk, plus single-group fetch - **Group Members** — Add, update, and remove members within a specific group - **Users** — List, create, retrieve, update, and remove community users - **User Search** — Search the user directory by name and profile attributes - **Webhooks** — List webhook configurations for Mobilize events - **Activities** — Retrieve user activity logs for analytics and engagement scoring ## Why Jentic - **Setup:** Wiring the Mobilize API by hand means setting up its HTTP basic auth and coding your own calls to the groups, members, and activities endpoints. 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 and member id in the URL path (/groups/{id}/members, /groups/{id}/members/{memberId}), so a rule can pin your agent to one group. You choose the operations it may call, so removing a member is not included unless you add it. - **Credential handling:** Your Mobilize basic auth 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 community groups' or 'add a member to a group', 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 - **Google Workspace Admin API** — Manage Google Workspace users and groups for organisation directories - **CiviCRM REST API** — Open-source CRM popular with non-profits and associations - **Action Network API** — Engagement platform for advocacy organisations and campaigns ## FAQ ### Why is there no official OpenAPI spec for Mobilize API? Mobilize does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Mobilize API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Mobilize API use? Mobilize uses HTTP Basic Authentication with a username and password issued by Mobilize support. Through Jentic, those credentials live encrypted in your Jentic One instance and the agent receives only a scoped session at execution time. ### Can I update many groups at once with the Mobilize API? Yes. POST /groups/bulk creates many groups in a single call and PUT /groups/bulk updates many groups at once. Pair these with POST /groups/{id}/members to populate the new groups efficiently during a bulk reorganisation. ### What are the rate limits for the Mobilize API? Mobilize does not publish a public rate limit policy in its developer documentation. Limits are set per integration - contact Mobilize support to confirm the per-second and per-day caps that apply to your API user. ### How do I sync members to a Mobilize group through Jentic? Run pip install jentic, then search for 'add members to a group'. Jentic returns the POST /groups/{id}/members operation schema. Execute it with the group ID and member payload for each new member, ensuring the source-of-truth CRM is the trigger. ### Does the Mobilize API expose user activity logs? Yes. GET /activities returns user activity events that can be used to drive engagement scoring and chapter health metrics. Pair the response with /users to attribute activity to specific cohorts. ### Can I limit what my agent is allowed to do with the Mobilize API? Yes. Jentic One is self-hosted, so your own rules decide which Mobilize operations and credentials the agent may use. Because Mobilize puts the group and member IDs in the URL path, such as /groups/{id}/members and /groups/{id}/members/{memberId}, a rule can pin the agent to a single group. You also choose the operations it may call, so an action like removing a member is available only if you add it, letting you allow reads and additions while withholding deletes.