/v1. All partner requests use HTTPS and Bearer company API keys. Interactive endpoints live in the API Reference tab (REST + Webhooks). MCP-compatible agents use the same resources and scopes over https://api.curbwaste.com/mcp.
Base URL
/v1.
Authentication
Request format
POST / PATCH bodies are JSON:
Response format
Single resourcePagination
Resource-specific query params (for example
searchTerm on customers) are documented on each endpoint.
Rate limits
Authenticated partner traffic is limited to 100 requests per 60 seconds per company. REST/v1 and POST /mcp share that quota across every API key for your company. Details, 429 handling, and what does not count: Usage.
Versioning
Path-based:/v1/.... Breaking changes ship under a new major path.
Explore the surface
Customers
Hand-written reference for the customer CRUD guides:List customers
GET /v1/customers — customers:readCreate customer
POST /v1/customers — customers:writeGet customer
GET /v1/customers/{id} — customers:readUpdate customer
PATCH /v1/customers/{id} — customers:writeRelated
Usage
Company rate limits for REST and MCP.
Errors
Common HTTP status codes and how to resolve them.
Webhook payloads
Envelope and per-event OpenAPI schemas.
Authentication
API keys, Bearer tokens, and scopes.