Member and course activity reaches your CRM as it happens.
Pro Lockers give your other systems a scoped API key and a signed webhook, so the record in your CRM matches the one in your community.
Integrations are part of Pro. Your first Locker starts with a 14-day Pro trial, no card.
- 4workflow presets
- Signedoutbound webhooks
- ZIPexport of your content
- Proplan required
One key per tool, with a preset, a request rate, and an expiry.
A key is created in Admin under Integrations and named after the system on the other end. A preset such as CRM sync grants members, contact data, enrollments, and completions, and the key gets a request rate per minute and an expiry date. The key is shown once and stored hashed, and it stops working on the expiry date.
- Presets for CRM, calendar, invitation, and content draft tools
- Stored hashed, shown once, rotated without losing the connection
- Every request rechecks the plan, the key, and the admin who issued it
Each key is limited to the permissions and courses you grant it.
A preset is a starting point, and Custom clears any permission the tool has no use for. Member contact data is its own permission, so a key can be limited to enrollment counts with no access to email addresses. A key can also be restricted to named courses, and the rest of the classroom is then unavailable to it.
- Course restrictions narrow course, enrollment, and completion access only
- Audience notes, tags, saved views, and follow-up dates are not granted by any permission
A signed webhook fires when a member joins or finishes a course.
When a member joins, finishes a course, or an event is published, Lockers signs the event and posts it to the endpoint you registered. A connected email tool can move a learner into a sequence the moment their completion is recorded, with no polling. Failed deliveries retry with the same event ID, and a row can be replayed from Admin.
- Member, course, enrollment, completion, event, invitation, and post events
- HMAC-SHA256 signature in the X-CS-Signature header on every delivery
- Failed deliveries retry with the same event ID, and one row can be replayed from Admin
Export the whole community as a ZIP, in resumable parts.
Every Locker can download supported community records and uploaded files as a ZIP archive, and a large one arrives as numbered parts that pause and resume. Private messages, private learning and Audience records, and billing data are excluded, and native video is listed as a reference.
A REST API with an OpenAPI contract and a Postman collection.
A GET to the members endpoint with a bearer token returns JSON containing the fields that key is allowed to see, and the same is true of courses, enrollments, completions, events, and posts. Requests always go to lockers.social, whatever domain your members use, so connecting a domain later never breaks an integration. The OpenAPI contract, the Postman collection, and an example Node client are published on lockers.social.
- Base URL https://lockers.social/api/v1, bearer token authorization
- Invitations can be created, inspected, and revoked; drafts can be written and published
What members see
Keeping two systems in agreement is the owner's work. A member enters their details once, in Lockers.
Asked once
When a member accepts an invitation created through the API, their record is available to the CRM from that moment, with nothing to fill in twice.
Follow-up that matches
When a member finishes a course, the next message they get from a connected email tool refers to that course, because the completion reached the tool when it was recorded.
Messages and notes stay outside the API
Direct messages, staff notes, and the tags on a member record are outside the API.
What Free and Pro include
Any Locker can get its content out. Connecting another system to live member, course, and event activity is a Pro capability, and each Locker has its own plan.
per Locker, forever
- Community content export
Download supported community records, including the member list with names and emails, and uploaded files as a ZIP archive.
Details
Excludes private messages, private learning and Audience records, and billing or security data. Native videos and other externally hosted media are listed as references; video files are not bundled. Large exports use resumable numbered ZIP parts.
- Member invitations
Invite people with a community link or send individual invitations from Admin.
- Audience member management
Organize members with tags, private staff notes, saved filters, and follow-up dates.
Details
Owners and admins share these tools. Follow-up dates are tracked in Admin and do not send automated reminders.
- API keys and webhooks
Available on Pro. A Free Locker can still export everything it holds.
$49 a month or $470 a year per Locker
- API and webhooks
Connect other tools to member, course, event, and post activity.
Details
Use API keys for supported data and actions, or signed webhooks to notify connected tools when activity changes. A compatible tool or custom integration is required.
- Scoped permissions
Give each key the exact permissions its tool needs, with an optional course restriction.
- Expiry and rotation
Set how long a key lives and replace it without rebuilding the connection.
Details
Rotation issues a new key while the connection keeps its identity, so drafts, invitations, and webhook bindings made through it stay attached.
- Developer files
An OpenAPI contract, a Postman collection, and example clients on lockers.social.
Keys and deliveries need an active Pro plan. If Pro ends, existing keys go inactive and stay listed, and you can still revoke them or export your content.
What integrations do not include
We do not publish a Zapier or Make app, and there is no marketplace of one-click connectors, so the connected tool has to call the API or receive a webhook. Webhooks are outbound only; nothing pushes data into your Locker over a hook, and there is no inbound endpoint to point a tool at. No key reaches private messages, Audience notes, tags, or billing.
The questions asked most often
Do I need a developer?
Not for a tool that can call an HTTP API with a bearer token. Create the key, paste it and the base URL into that tool, and use Test the connection to confirm it reaches your community. For anything custom, a developer gets the OpenAPI contract, the Postman collection, and the example Node client and webhook receiver at lockers.social/api.
What can a connected tool read and write?
It reads members, courses, enrollments, completions, events, and posts. It can create, inspect, and revoke invitations, and it can write drafts that your team publishes, or publish them itself when you grant that separately. Payment amounts and purchase history stay with the owner in Admin, outside every key.
What happens to my integrations if I leave Pro?
Existing keys go inactive and deliveries stop, and nothing is deleted. You can still revoke a key or download your export from a Free Locker. Subscribing again brings the same connections back with their drafts, invitations, and webhook bindings intact.
Does the API work with my own domain?
Requests always go to lockers.social/api/v1, even when members reach the community at your own address. That address never moves, so a tool built before you connected a domain keeps working after.
Other feature pages
Connect your first tool on Pro
Start a Locker and turn on Pro. Then create a key with only the permissions the tool needs.