-Reference for every endpoint used by the Memoket integration on automation
-platforms such as Zapier — OAuth authentication, webhook subscriptions, event
-delivery, and signature verification.
+
-- **Base URL:** `https://api.memoket.ai`
-- **Auth:** OAuth 2.1 Bearer token (or a personal API token) — scoped to one account
-- **Access:** read-only — this API only ever *sends* account data out; it cannot
- create, edit, or delete recordings or account data.
+
Memoket API
-### Endpoints used by the Zapier integration
+### Turn finished conversations into reliable workflows.
+
+Authorize one account, subscribe to the moments you care about, and receive
+recording data in signed webhook events with observable delivery attempts.
+
+
+
+
+
+
+
+
+
+## 🚀 Quick Start
+
+### 1. Discover the authorization server
+
+```bash
+curl https://api.memoket.ai/.well-known/oauth-authorization-server
+```
+
+Register an OAuth client, send the user through Authorization Code + PKCE, and
+exchange the code for an access token. The full flow is in
+[Authentication](#1-authentication).
+
+### 2. Subscribe to completed summaries
+
+```bash
+curl --request POST https://api.memoket.ai/v1/webhooks \
+ --header "Authorization: Bearer $MEMOKET_ACCESS_TOKEN" \
+ --header "Content-Type: application/json" \
+ --data '{
+ "url": "https://your-app.example.com/hooks/memoket",
+ "events": ["summary.completed"]
+ }'
+```
+
+Store the returned `secret` immediately. It is shown only once and is required
+to verify deliveries.
+
+### 3. Verify before processing
+
+Compute `HMAC_SHA256(secret, timestamp + "." + raw_request_body)`, prefix the
+hex digest with `sha256=`, and compare it with `X-Memoket-Signature` using a
+constant-time comparison. Keep the raw request bytes intact.
+
+### 4. Acknowledge and de-duplicate
+
+Return a `2xx` response within 5 seconds. Deliveries may be retried and arrive
+more than once, so de-duplicate on the event envelope's `id`.
+
+
+
+## 📚 API Reference
+
+This is the public reference for the Memoket automation and webhook surface:
+OAuth authentication, subscription management, event delivery, and signature
+verification. Recording-derived data is read-only; management endpoints only
+change webhook subscriptions.
+
+### Endpoint map
| Purpose | Endpoint |
|---|---|
@@ -43,7 +141,9 @@ in Sections 2.5–2.7.
## 1. Authentication
-Every request carries a Bearer token identifying the account:
+Every protected webhook-management request carries a Bearer token identifying
+the account. OAuth discovery, registration, authorization, and token exchange
+use their own protocol-specific authentication rules.
```
Authorization: Bearer