RevKeenDocs

Developers

Build on RevKeen with the REST API, CLI, official SDKs, webhooks, terminal flows, and MCP tools

Build on RevKeen

Use the RevKeen API, CLI, official SDKs, webhooks, terminal flows, and MCP tools to build billing, payments, subscriptions, terminal, and automation workflows.

API Reference · Quickstart · SDKs · CLI · MCP

Developer surfaces

Choose the right surface

If you are building...Start hereWhy
Application codeSDKsTyped clients with retries, pagination, and webhook helpers
Raw HTTP integrationsAPI ReferenceCanonical request and response contract
Terminal workflowsCLIFast operator tasks and interactive prompts
AI agentsMCPOAuth-scoped tools over remote MCP

Common build paths

Core concepts

  • Authentication Use x-api-key on server-side REST requests. Use live keys in production and rk_sandbox_* keys in staging. Read authentication
  • Environments RevKeen separates production, staging, and mock so you can choose the right level of safety and realism for each task. Read environments
  • Idempotency Add Idempotency-Key on write requests that must be safe to retry without creating duplicate financial state. See the API reference
  • Webhooks RevKeen pushes billing and payment events to your systems. Consumers should verify signatures and deduplicate by event ID. Read webhook guidance
  • Errors and rate limits Handle 4xx, 5xx, and 429 responses explicitly and log request IDs so you can trace issues quickly. See the API reference

Tools and downloads

Production checklist

  • Use staging first before sending any live traffic.
  • Verify webhook signatures before processing events.
  • Make webhook consumers idempotent and deduplicate by event ID.
  • Rotate live secrets and keep keys server-side only.
  • Monitor failures, retries, and rate-limit responses.