Dumpster Controls Now Has a Public API: Connect Your CRM, Funnels and Tools

Dumpster Controls can now be integrated with external software. We shipped a public REST API, complete with signed webhooks, an OpenAPI spec, and the kind of documentation developers actually want to read. Your CRM, your website forms, your GoHighLevel funnels, your reporting spreadsheets: they can all talk to your dumpster operation now. Included free, like everything else on the platform.

What shipped

This was not a minimum-viable endpoint. The full surface, live in production today:

• Read your data as JSON: orders (with filters and pagination), customers, estimates, your dumpster size catalog with pricing, and junk removal jobs. Always and only your own company's data.
• Push leads in: POST /v1/leads takes a prospect from any form or funnel and drops it into your Customers screen with a "new" badge and one-click conversion, with automatic deduplication.
• Real-time signed webhooks: six events (order.created, order.status_changed, payment.received, lead.created, junk_job.created, junk_job.status_changed) POSTed to your server with HMAC-SHA256 signatures, retries with backoff, and automatic endpoint health management.
• Managed like a grown-up API: keys shown once and stored only as fingerprints, per-key revocation and scheduled auto-revocation, per-key rate limits, audit trail on every management action.

What you can build with it

The founding request came from a real customer who wanted his GoHighLevel account connected. That integration is now a fifteen-minute job: the funnel POSTs leads in, and webhooks push orders and payments back into the CRM pipeline. The same building blocks cover the rest of the field:

• A nightly sync that mirrors customers and orders into any CRM or data warehouse.
• Website quote forms that create leads directly, no email inbox in the middle.
• Zapier and Make automations triggered the moment an order is created or paid.
• A Google Sheet that fills itself with the month's orders and junk jobs for reporting.
• Slack alerts on payment.received, so the whole team hears the register ring.

Documentation devs actually enjoy

An API is only as good as its docs, so we wrote them the way we would want to find them:

• dumpstercontrols.io/developers: the quick reference with endpoints, limits, and webhook verification.
• /openapi.json: the machine-readable OpenAPI 3 spec, importable into Postman or any client generator.
• An 11-guide Developer API module in the public manual: get started in five minutes, authentication and key lifecycle, every endpoint with its exact fields, error codes and limits, webhook signature verification with working Node.js and Python code, and integration recipes for GoHighLevel, Zapier, Make and Sheets.

Approval-gated, and money stays on rails

A public API on a free platform has to take security personally, so this one does:

• Human approval first. No key exists until you request access with your use case and our team approves it. The gate is re-checked on every single request, so revocation is instant.
• Keys are hashed, secrets shown once. Nothing recoverable sits in the database, and browser calls are rejected on purpose so keys stay server-side.
• Your data only. Company scoping is applied server-side on every query; the field lists are explicit allowlists that exclude consent records, tokens, GPS and internal state.
• Money is out of scope, permanently. The API cannot charge, refund or reprice anything. Payments keep flowing through the platform's own Stripe-based rails, protected by the built-in risk screening and fraud defenses we have written about before. Your integration brings the demand; the platform keeps handling the money, and tells you about it through webhooks.

Read the full model in the manual: The API security model, explained.

Where this puts the category

Dumpster rental software has historically been a walled garden: your data lives in the vendor's screens and leaves by CSV, if at all. As of August 2026, we found no other major platform in this category (Docket, DRS, iCANS) offering a public, documented, openly requestable API. We think that gap says something about how these platforms are engineered. An open API is not a feature you bolt on; it is what a system looks like when the underlying architecture (row-level security, audited server-side functions, explicit data contracts) was built properly from the start.

And in the spirit of checkable claims: when a competitor ships one, we will update that sentence.

FAQ