What is the Zemers Developer API?

A read-only REST API that exposes your Zemers business data — leads, customers, products, orders, subscriptions, analytics and an event feed — so you can sync it into your CRM, email marketing, data warehouse, or a custom internal dashboard.

Is the Zemers API free?

Yes. Developer API access is included with paid Zemers plans. You can generate API keys from your creator dashboard.

What is the base URL of the Zemers API?

All requests go to https://dev.zemers.com/api/v1.

Does the Zemers API support webhooks?

Not yet. The MVP is read-only. For near-real-time integrations, poll GET /events with the cursor returned in the previous response. Webhooks are on the roadmap.

How do I authenticate to the Zemers API?

Send your API key in the Authorization header as a Bearer token. Each key is scoped to a single tenant (one creator business).

Zemers Developer API

Your business data, connected to the tools you already use.

The Zemers API gives you programmatic, read-only access to the data your store generates — leads, customers, products, orders, subscriptions, analytics, and an event feed. Use it to sync data into your CRM, email marketing, data warehouse, or build a custom internal dashboard.

Quick links

Getting started — make your first request in 5 minutes
Authentication — API keys, headers, error codes
Endpoints — full reference
Rate limits
Errors

Base URL

https://www.zemers.com/api/v1

Status

Read-only MVP. Write endpoints (POST/PATCH/DELETE) and webhooks are on the roadmap. For real-time-ish use cases today, poll GET /events with the cursor from the previous response.

This API is read-only. Do not attempt to create, update, or delete Zemers resources through this API.

Important concepts

Tenant — the creator business. Every API key is scoped to one tenant.
Lead — a person captured before purchase, usually through storefront activity, forms, waitlists, free opt-ins, or other lead capture flows. A lead row is preserved after conversion (with converted_at set) so acquisition source survives the lead → customer transition.
Customer — a person who bought, claimed access, or has at least one purchase/access relationship with the creator. A customer may also have a lead row (with converted_at != null) when their relationship started as a lead.
Product — what the creator sells or gives access to.
Order — a purchase or checkout-related record for a product.
Subscription — a recurring purchase or recurring access relationship.
Event — a timestamped activity from the creator's store, useful for polling integrations.
Marketing consent — per-creator GDPR opt-in for marketing communications. Captured at sign-in / lead capture / checkout. Exposed on /v1/leads and /v1/customers via the marketing_consent object with status granted | withdrawn | none. Only contacts with status: "granted" are eligible for marketing emails — your CRM/ESP integration must respect this flag. Every grant or withdrawal is audit-logged with timestamp, IP, policy version, and the surface that captured it.
Archived contact — a lead or customer the creator soft-archived from their dashboard. The user account, purchases, and access stay intact in Zemers — only the creator's view is hidden. Archived contacts are excluded from /v1/leads and /v1/customers by default; pass ?include_archived=true to include them.