Use a secure API key with the scope users.readonly to authenticate requests to the Memberships API. Store credentials safely and rotate them regularly.
In the 123FormBuilder integration, paste your Memberships API credentials and configure OAuth or API key handling as required. Ensure credentials are scoped to read-only user data for safety.
GET /users/ — Retrieve a list of users from Memberships API. Use this to sync all members into 123FormBuilder on a schedule or through a trigger. This endpoint returns an array of user objects with id, email, name, and status.\n\nGET /users/:userId — Retrieve a single user by ID from Memberships API. Use this to fetch details for a specific member when updating a form or triggering an action. Returns a user object with id, email, firstName, lastName, and profile information.
Trigger a bulk sync to pull the latest user directory into 123FormBuilder when you need a fresh view of members.
Actions: Call GET /users/ to retrieve users, then map fields (id, email, name) to your form or CRM fields and update records automatically.
GET /users/
id, email, firstName, lastName
Triggered when you need details for a specific member, such as during form submission or verification steps.
Actions: Call GET /users/:userId and map relevant fields to the app records.
GET /users/:userId
id, email, status, profile
Triggered for batch cleanups, migrations, or periodic audits of member data.
Actions: Use paginated GET /users/ calls, map fields across records, handle errors and retries.
GET /users/ (paginated)
id, lastLogin, status
Automates member data syncing without code, keeping your form submissions and CRM in sync.
Reduces manual data entry by pushing Memberships data into 123FormBuilder workflows and forms.
Scales with your growth: add more endpoints and mappings without touching code.
Key elements include authentication, endpoint usage, data mapping, triggers, actions, and error handling in the integration.
A defined URL you call to access a server resource in an API.
The method used to prove identity and gain access to an API (e.g., API key or OAuth).
Technique to split large results into smaller pages for easier processing.
An HTTP callback that sends data when a specific event occurs in the system.
Automatically create or update a contact in 123FormBuilder when a new user is created in Memberships API.
Fetch the user by GET /users/:userId to verify status or tier before allowing form submission.
Regularly pull the user list and clean up records in 123FormBuilder forms to maintain data hygiene.
Create credentials in the Memberships API console and configure redirect URIs for secure access.
Enter the endpoints GET /users/ and GET /users/:userId and set up data mappings to match your forms.
Run end-to-end tests, verify data integrity, and deploy to production.
No heavy coding is required to connect Memberships API with 123FormBuilder. This guide walks you through configuring the connection, selecting endpoints, and mapping fields using the visual builder. You can automate data flows without writing custom scripts. Two paragraphs will help you understand the setup steps and best practices.
You should typically start with GET /users/ to fetch the full user directory and GET /users/:userId to work with individual records. These endpoints cover common use cases like syncing contacts and verifying a user’s status. If your project requires more endpoints, you can add them later.
Map fields from the Memberships API to the corresponding fields in 123FormBuilder. Use data mappings to align id, email, name, and status. This ensures data flows into forms and automations accurately.
API key with the users.readonly scope is a safe default for read-only integration. Depending on the API, OAuth can also be used. Store credentials securely and rotate them regularly. Always follow best practices for authentication.
Yes, you can paginate through users if there are many. Use the endpoint GET /users/ with pagination parameters to fetch pages until you have all records. This helps avoid timeouts and keeps your app responsive.
Most APIs enforce rate limits. Plan requests to avoid hitting quotas, implement exponential backoff, and cache results when possible. The Memberships API docs outline the exact limits.
The Memberships API documentation is available in your API provider portal and includes endpoint references, authentication details, and example requests. If you’re using 123FormBuilder’s connector, consult the integration docs for step-by-step setup.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
