api reference
dripos is a Mac app first. The backend API exists for account bootstrap, API keys, hosted integration status, OAuth pairing, Stripe OAuth, and email-open sync. The Inbox/person directory, communication timeline, drafts, account signals, and Copilot run against local app/sidecar surfaces. For the full OpenAPI 3.1 spec for public backend routes, see/openapi.json.
CLI
~/.drip-cli/. Source sync and draft state are local unless a specific hosted integration or LLM provider is involved.
HTTP conventions
- Base URL:
https://api.drippay.dev/v1 - Auth:
Authorization: Bearer <key>forsk_*andpk_*API keys; Privy sessions for browser dashboard flows. - Content type:
application/json - Timestamps: RFC 3339 UTC unless a route documents otherwise.
- Errors: JSON
{ error, code, details? }with stablecodestrings.
/v1.
account bootstrap
The Mac app creates a key named
dripos Mac App with owner-level access, stores the one-time secret in macOS Keychain, and uses it for later backend calls.
hosted integration status
Local token bundles are cleared by native app commands when a provider uses local OAuth storage.
OAuth pairing
Google and Slack use pairing flows so provider tokens end up on the Mac instead of staying in the browser callback session. Fathom pairing support may exist in backend/local code, but it is not a normal first-class Integrations card in the current Mac app.
Granola, Circleback, Cal.com, and Calendly use local OAuth/MCP-style flows in the Mac app rather than hosted backend comms install routes. Pocket AI may exist in older local status surfaces, but it is not a normal first-class Integrations card in the current Mac app.
Stripe OAuth
The current Mac app exposes Stripe OAuth, manage, and disconnect. It does not expose the older Stripe restricted-key paste flow.
email opens
drip-cli polls one backend endpoint to reconcile email-pixel opens into its local database.
Query parameters:
Unknown tokens are ignored locally. Mailbox prefetchers can create synthetic opens, so clients should treat open counts as signal rather than proof of human read.
local native surfaces
These are Tauri/native commands or local sidecar surfaces, notapi.drippay.dev routes. They are the current Mac app contract for the Inbox/person detail product.
The current Inbox and Copilot screens do not compose the legacy dashboard customer endpoints for their normal UI.
legacy dashboard surfaces
The billing/dashboard backend still contains routes such as/dashboard/customers/*, /dashboard/customers/:id/drip-cli-*, and /dashboard/copilot/*. Those are dashboard or legacy integration surfaces. They are not the current Mac app contract for the local Inbox person detail page or Copilot chat.
common errors
OpenAPI
Machine-readable schema:https://docs.drippay.dev/openapi.json. Regenerate it from the backend with npx tsx scripts/export-openapi.ts; do not hand-edit the generated JSON.