Memberships API uses a Bearer token with scope users.readonly. Store credentials securely and rotate keys regularly.
Zapier securely stores and uses your API key or OAuth credentials to authorize requests to the Memberships API; configure the connector with the appropriate permissions.
Endpoint 1: GET /users/ — List all users. Endpoint 2: GET /users/:userId — Retrieve a single user by ID. Endpoint 3+: Not displayed on this page.
Use GET /users/ to monitor for new or updated user records and trigger downstream actions in Zapier.
Actions include provisioning charity access, notifying teams, or updating connected apps.
Primary endpoint: GET /users/:userId to fetch details for a specific user when a trigger fires.
Key fields: userId, email, status, lastLogin.
Lookup by userId or email to pull user data into Zapier.
Actions: create or update user records in downstream apps.
Endpoint: GET /users/:userId
Fields: userId, email, fullName, membershipStatus.
Schedule a periodic pull to sync multiple users across systems.
Actions: batch create or update records in target apps.
Bulk endpoints: GET /users for lists and GET /users/:userId for details as needed.
Key fields: userId, groups, accessLevel.
Automate charity website access provisioning without writing code.
Reduce manual data entry and errors with real-time data sync.
Easily build cross-platform automations using Zapier’s no-code tools.
A concise glossary of authentication, endpoints, triggers, and actions when connecting the Memberships API to the Zapier App Connector.
A set of endpoints and protocols that allow apps to request data and perform actions.
An authorization framework that issues access tokens for secure API access.
A specific URL path that performs a defined action or returns data.
A token used in the Authorization header to prove access rights.
When a new user is added in Memberships, automatically provision access to charity sites via Zapier.
Send alerts to Slack or email when a user’s status changes.
Schedule monthly reports on user activity across connected apps.
Generate API key for Memberships with scope users.readonly and save securely.
Enter the API key in Zapier’s app configuration and set up authentication flow.
Choose a trigger (New or Updated User) and an action (Provision Access or Update Records).
The Memberships API exposes endpoints like GET /users/ to list users and GET /users/:userId to fetch individual user details. In Zapier, you can configure triggers and actions to automate charity website access without writing code. The combination lets you build powerful automations quickly.
Authentication is token-based. Use a Bearer token generated from your Memberships API credentials, with the required scope (users.readonly). Store tokens securely and rotate them regularly. Zapier can manage the secret securely in the app connection settings. Ensure you use HTTPS for all requests.
The primary read endpoints are GET /users/ and GET /users/:userId for reading user data. Depending on your plan, additional write endpoints may exist; check the API docs for available write operations. For read-only use cases, these endpoints provide all user data you need.
Yes—if your Memberships API exposes create or update endpoints (such as POST /users or PATCH /users/:userId). You can map Zapier actions to those endpoints to manage user data automatically.
Webhooks enable real-time updates to your connected apps. If supported, configure a Zapier Webhook URL as the destination to receive events. This lets your workflows react instantly to changes in user data.
Yes. Use Zapier’s built-in task history, filters, and multi-step zaps to audit actions. You can log events and export reports without writing code.
Use Zapier’s Test mode and the Memberships API’s sandbox environment if available. Validate triggers, actions, and data mappings before going live.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
