Who it is for
These docs use a few terms consistently:- Partner — you, the company or developer building an integration with CurbWaste.
- Customer — the CRM record under
/v1/customers, meaning one of the accounts your business serves. It is not the company calling the API. - Developer Platform — the web app at platform.curbwaste.com where people on your team create API keys and register webhook endpoints.
What you can do today
Common integrations start with customers:- Keep your CRM in sync — create and update customer records from your own system, and store the CurbWaste id as the join key.
- React when data changes — get notified when a customer or location is created or updated, without polling.
- Give an AI agent access — let an MCP-compatible agent look up or update CurbWaste data with the same permissions as your API key.
How the pieces relate
Create API keys and webhook endpoints in the Developer Platform. The same key works for REST and MCP. When something changes in CurbWaste, webhooks notify your systems so you do not have to poll. Details for each piece live on their own pages below.Read next
- Authentication — key lifecycle, scopes, and auth errors
- Customers — identifiers and how customers connect to other domains
- Webhooks — event catalog, envelope, and signature verification
- MCP — connect an AI client and which tools each scope unlocks
Quickstart
Create a key, create a customer, and fetch it back in a few minutes.