Membber Developers
Membber runs membership, loyalty, orders, bookings and analytics for real-world businesses. All of it sits on one versioned API: the same surface our own apps run on. The reference you read here is generated from the live contract, so it is never out of date.
Every operation with full request and response schemas, auth scopes, and copyable cURL, TypeScript and Swift examples.
SDKsTyped TypeScript and Swift clients, generated from the same contract as the API so they cannot drift.
GuidesAuthentication, errors, idempotent retries, rate limits and versioning. Short, precise, honest.
Quickstart
One client, one Bearer token, typed results. Reads return data shaped exactly as the reference shows; writes take an idempotency key so retries are always safe. Start with the public /api/v1/system/ping probe, no auth required, then sign in and go.
import { createMembberClient } from "@membber/sdk-ts";
const membber = createMembberClient({
getAccessToken: () => process.env.MEMBBER_TOKEN,
});
const { data, error } = await membber.raw.GET(
"/api/v1/customers",
{ params: { query: { store_id: "<store-id>" } } }
);What people build
Merchant integrations
Sync members, visits, orders and reports into the tools a business already runs on.
AI agents
Scoped agent keys let an agent work the front desk, look up members, grant stamps, move orders forward, and nothing more.
Branded apps
A merchant's own app, powered end to end by the same contract our apps use. Nothing second-class.
A plain-language page on what an open platform means for your business: your data stays yours, your tools connect, and AI can help at the counter on your terms.
Building something?There is no self-serve key flow yet, deliberately. Tell us what you are building and we will set you up with the right credential.