Go to Settings > System Settings > API Tokens to create the credentials your integration will use.
Members One exposes a REST API so your developer can build custom integrations on top of your account, reading and updating your customers, memberships, orders and products from your own systems. This page is an orientation for developers: it explains how access and authentication work, what the API covers, and where to find the full interactive reference. It is not a complete endpoint list, so treat it as a starting point rather than a specification.
If you only need to connect a WordPress/WooCommerce or Shopify store, you do not need the API directly. That is handled by the built in integrations, and you can follow the relevant guides in Getting Started instead.
How Access Works
API Tokens
- To call the API from your own application, generate an API token under Settings > System Settings > API Tokens. Each token can be set to Read-only or Full Access and given an expiry of 30, 90 or 365 days, or set to never expire.
- A token is shown in full only once, at the moment you create it, so copy it somewhere safe straight away. You can hold up to five tokens at a time, and any token can be revoked immediately if it is no longer needed.
Authentication
- The API uses Laravel Sanctum bearer tokens. Send your token in the
Authorizationheader on every request, for exampleAuthorization: Bearer 770|abc123.... - Requests should also include an
Accept: application/jsonheader so responses come back as JSON.
Identifying Your Account
- Members One is multi-tenant, so each request must tell the API which vendor account it is for. Include your vendor ID in the
X-Tenantheader, for exampleX-Tenant: your-vendor-id. - A request without a valid token or the correct
X-Tenantvalue will be rejected, which keeps your data isolated from every other vendor on the platform.
Client ID and Client Secret
- Your Client ID and Client Secret are a separate set of credentials used to connect an eCommerce store to Members One, not to authenticate custom API calls. If you are looking for those, see How to find Client ID and Client Secret.
What the API Covers
The API mirrors much of what you can do in the Vendor Panel. At a high level it spans the following areas. The interactive documentation below lists the exact endpoints, parameters and responses for each.
| Customers | Look up and manage customer records, along with their orders, groups, notes and loyalty club membership. |
| Memberships | Read and manage memberships, including their items and status. |
| Scheduled Orders | Work with upcoming recurring orders, including their statuses and payment states. |
| Orders | Access order history and order detail records. |
| Products and Inventory | Read your product catalogue and internal inventory levels. |
| Clubs and Loyalty | Manage subscription clubs, loyalty clubs and promotions. |
| Contact Types and Groups | Read customer groups and contact types used for segmentation. |
| Settings and Users | Access account settings, users, roles, activity logs and dashboard summaries. |
Please note: A Read-only token can only make GET requests. Creating, updating or deleting records requires a Full Access token.
Interactive Documentation
The complete, always up to date reference lives in the Swagger UI at api.members-one.com/api/documentation/vendor. This documentation is public, so you can browse it without logging in. It groups the endpoints by area, shows the required headers and parameters, and lets you try requests directly from the page once you supply a token.
Need a Hand?
If you are planning an integration and want to confirm which endpoints suit your use case, or you need help generating a token, please get in touch with our support team.