Mobilize (Journey by Forj) API

Name: Mobilize (Journey by Forj) API API
Brand: Mobilize (Journey by Forj) API
Availability: InStock

✓ Official Vendor SpecCRMCustomer Successbasic34 EndpointsREST

For Agents

Manage Mobilize community groups, members, users, custom field definitions, webhooks, and activities through 34 endpoints under api.mobilize.io/v1.

Connect the Mobilize (Journey by Forj) API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mobilize (Journey by Forj) API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Mobilize (Journey by Forj) API API.

Create, list, and bulk-create groups via /groups and /groups/bulk

Invite members to a group through /groups/{id}/invite

Search group members and run bulk member operations on /groups/members/bulk

Define and update custom field definitions for users and groups

GET STARTED

Start building with Mobilize (Journey by Forj) API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Mobilize (Journey by Forj) API API for, with concrete tasks.

★ Group invite-driven onboarding

Community managers automate onboarding by sending an invite to /groups/{id}/invite for each new member, then registering a webhook on /webhooks to receive notification when the invite is accepted. The flow keeps Mobilize as the system of record for membership while letting external tools react to acceptance events in real time.

POST to /groups/42/invite with the new member's email and role, then GET /webhooks to confirm an acceptance webhook is registered for that group.

Custom field-driven segmentation

Associations use the field definition endpoints to add custom attributes to user and group records, then drive segmentation queries off those fields. This keeps domain-specific data inside Mobilize so reporting tools and downstream agents can filter members by chapter, graduation year, or membership tier without bolting on a separate database.

POST a new field definition for 'graduation_year' against the user resource, then update existing users with the value via the user endpoints.

Bulk migration with status tracking

When migrating a community into Mobilize, operators submit bulk jobs through /groups/bulk and /groups/members/bulk and poll /groups/bulk/status and /groups/bulk/groups-status until completion. This pattern handles large imports without timing out and gives a clear retry surface when a row fails.

POST a bulk job to /groups/bulk with 50 group definitions, capture the job ID, then poll /groups/bulk/status until the job is complete and report any failed rows.

Agent integration via Jentic

An AI assistant for a community team can search Jentic for 'invite a member to a Mobilize group', load the /groups/{id}/invite schema, and execute the call without exposing the basic auth credentials. The agent can then chain bulk member operations and webhook checks to manage the rollout end to end.

Search Jentic for 'invite a member to a Mobilize group', load the /groups/{id}/invite schema, execute it for group 42 and email 'newmember@example.com', and return the invite ID.

Key Endpoints

34 endpoints — mobilize, marketed as journey by forj, is a community management platform for professional associations, alumni networks, and customer communities.

METHOD

PATH

DESCRIPTION

GET

/groups

List groups in the community

POST

/groups/bulk

Bulk-create groups

GET

/groups/bulk/status

Check bulk job status

POST

/groups/{id}/invite

Invite a user to join a group

GET

/groups/{id}/members/search

Search members of a group

POST

/groups/members/bulk

Bulk member operations across groups

GET

/groups

List groups in the community

POST

/groups/bulk

Bulk-create groups

GET

/groups/bulk/status

Check bulk job status

POST

/groups/{id}/invite

Invite a user to join a group

GET

/groups/{id}/members/search

Search members of a group

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Mobilize basic auth credentials are stored in the Jentic MAXsystem vault. Agents never see the username or password; Jentic injects the Authorization header on each call.

Intent-based discovery

Agents search Jentic for intents like 'invite a member to a Mobilize group' or 'list Mobilize activities' and Jentic returns the matching /v1 operation with its input schema.

Time to first call

Direct Mobilize integration: 2-4 days to model basic auth, 34 endpoints, custom fields, and bulk job polling. Through Jentic: under 1 hour for first call once credentials are vaulted.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Mobilize API

Earlier, smaller Mobilize spec covering 19 endpoints

Use the mobilize.io spec for the simpler core surface; use this expanded mobilize spec when you need invites, bulk status, and custom field definitions.

Alternative

Circle API

Content-led community platform with spaces and posts

Choose Circle for content-driven communities; choose Mobilize for membership and group-driven networks like associations and alumni.

Alternative

Discourse API

Open-source discussion forum platform

Use Discourse when the community runs on threaded conversations; use Mobilize when group membership and engagement reporting are the priority.

FAQs

Specific to using Mobilize (Journey by Forj) API API through Jentic.

What authentication does the Mobilize (Journey by Forj) API use?

The API uses HTTP basic auth. Send a base64-encoded username:password pair in the Authorization header on every call to api.mobilize.io/v1. Through Jentic, those credentials are stored in the MAXsystem vault and never exposed to the agent.

Can I run bulk operations against Mobilize groups and members?

Yes. /groups/bulk and /groups/members/bulk accept array payloads, and /groups/bulk/status and /groups/bulk/groups-status let you poll job progress so you can handle large migrations without timing out.

What are the rate limits for the Mobilize API?

The OpenAPI specification does not declare rate limits. Consult the Journey by Forj developer documentation for tenant-specific quotas and back off on HTTP 429.

How do I invite a user to a Mobilize group through Jentic?

Run pip install jentic, then search Jentic for 'invite a member to a Mobilize group', load the /groups/{id}/invite schema, and execute it with the group ID and invitee email. Basic auth is injected automatically.

Can I add custom fields to Mobilize user records?

Yes. The FieldDefinitions endpoints let you define custom attributes on users and groups, after which those fields can be set on individual records and used for segmentation in queries and webhooks.

Is the Mobilize API free to use?

Mobilize (Journey by Forj) is a commercial community platform. API access is bundled with a paid subscription. There is no public free tier. Get started with Jentic at https://app.jentic.com/sign-up.