To access data, authenticate using OAuth 2.0 with the users.readonly scope to read user information from the Memberships API.
In Zapier, configure a connected account that uses OAuth 2.0 credentials or an API key, scoped to read user data from the Memberships API.
– GET /users/ — list users – GET /users/{userId} — get a user by ID
Trigger: New or updated user records in Memberships
Actions: Retrieve user data, create or update contacts in connected apps, and map fields
GET /users/
userId, email, name, status, lastLogin
Trigger: Fetch a specific user on demand
Actions: Retrieve details for a given userId and format for Zapier
GET /users/{userId}
userId, name, email, membershipLevel
Trigger: Periodic export of user data
Actions: Sync or append user records to destinations
GET /users/
userId, email, status, updatedAt
Build automations without writing code to move membership data between apps
Speed up workflows with instant triggers and actions
Secure access with OAuth scopes and centralized credentials
This glossary covers API endpoint, authentication, trigger, action, and field mapping terms used throughout this guide.
A specific URL path and HTTP method that lets a client access a resource in the Memberships API.
The process of verifying identity and permissions to access API data.
An event that starts a workflow in Zapier when data changes in the source system.
Associating API data fields with Zapier fields to transfer data between apps.
Set up a Zap that automatically creates a member in Memberships when a new contact signs up elsewhere.
Route members by plan type into tailored campaigns or access levels.
Log changes to keep an audit trail and simplify reporting across apps.
Register the Memberships API in Zapier, authorize the connection, and select the users.readonly scope.
Add actions that pull /users/ and /users/{userId} data and map to Zapier fields.
Test end-to-end to ensure data flows correctly between Memberships API and your apps.
You’ll typically need a read-only scope (users.readonly) to fetch user data from Memberships. Ensure your OAuth app permissions are configured correctly. If using API keys, store them securely and rotate credentials regularly.
Yes. The Zapier App Connector lets you connect Memberships API without custom code by using triggers, actions, and field mappings. For complex flows, you can build multi-step Zaps.
Key endpoints for user data include GET /users/ and GET /users/{userId}. Additional endpoints can be added as you scale your integration.
Use Zapier’s built-in field mapping to align Memberships API data to your destination fields. Test mappings to ensure data types align.
OAuth 2.0 is the recommended method for secure, scalable access. If the API offers API keys, store securely and limit scope to read-only.
Sync frequency depends on your needs and API rate limits. You can trigger on events or schedule periodic pulls in Zapier.
Refer to the official Memberships API documentation and the Zapier app connector guide for endpoint details and authentication steps.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
