Skip to main content

Monk API

The Monk API provides programmatic access to your billing infrastructure, enabling you to build and manage usage-based billing, subscription management, and payment collection.

Base URLs

Monk has two separate APIs hosted on dedicated infrastructure:
ProductionSandbox
Monk APIapi.monk.com/v1api-sandbox.monk.com/v1
Monk Events APIevents-api.monk.com/v1events-api-sandbox.monk.com/v1
The Monk API handles customers, meters, pricing, plans, contracts, invoices, and credits. The Monk Events API is a high-throughput endpoint for usage event ingestion and queries.

What You Can Do

Meters

Define billable metrics for usage-based pricing

Pricing

Create flat, tiered, and usage-based pricing configurations

Plans

Bundle pricing into reusable subscription templates

Contracts

Subscribe customers to plans

Events

Ingest usage data for metered billing

Customers

Manage customer records and metadata

Invoices

Access invoice data and payment status

Webhooks

Receive real-time notifications for billing events

Quick Start

1. Get your API key

Generate an API key from Settings → API Keys in your Monk dashboard. API keys have granular scopes — select only the permissions you need.

2. Make your first request

curl -X GET "https://api.monk.com/v1/customers" \
  -H "Authorization: Bearer mk_live_your_api_key"

3. Set up usage-based billing

For usage-based pricing, the typical flow is:
Meter → Pricing → Plan → Contract → Events → Invoice

                        Credit Wallet (optional prepaid balance)
  1. Create a meter to define what you’re measuring (e.g., API calls, tokens)
  2. Create pricing linked to the meter with your rate structure
  3. Create a plan bundling your pricing into a subscription template
  4. Create a contract to subscribe a customer to the plan
  5. Send events as customers consume resources
  6. Invoices are automatically generated with aggregated usage (minus credits)

How Usage-Based Billing Works

Understand how meters, pricing, plans, contracts, and credits fit together — with diagrams and FAQs
New to usage-based billing? Start with our Billing for SaaS guide for an end-to-end walkthrough.

Authentication

All requests require a Bearer token in the Authorization header:
Authorization: Bearer mk_live_your_api_key
API keys are scoped to specific operations. Common scopes include:
ScopeDescription
usage:writeIngest usage events
usage:readRead usage data
customers:readRead customer data
customers:writeCreate and update customers
invoices:readRead invoices
contracts:readRead contracts
contracts:writeCreate and manage contracts
plans:readRead plans
plans:writeCreate plans
meters:readRead meters
meters:writeCreate meters
pricing:readRead pricing configurations
pricing:writeCreate pricing configurations

Authentication Details

Learn more about API keys, scopes, and test vs live modes

Need Help?

Guides

Step-by-step tutorials for common workflows

Support

Contact our support team