Developer Platform

Build on the Sell.Do API

Push leads in, pull bookings and ledgers out, subscribe to webhooks, and extend Sell.Do with custom JavaScript, connectors and AI agents — all under OAuth-scoped, permission-aware access.

What you can build

Webhooks

Subscribe to lead, booking and stage-change events in real time, HMAC-signed.

REST API

Full CRUD over leads, inventory, bookings, ledgers, users and reports.

Connectors

Pre-built integrations for portals, telephony, ERP and payments.

Custom JavaScript

Run custom logic on platform events with our sandboxed runtime.

Marketplace apps

Publish and install apps that extend Sell.Do for everyone.

OAuth & scopes

Secure, scoped tokens — enforced against the same RBAC as the UI.

Quickstart

A few lines to your first lead

Authenticate with an OAuth bearer token and POST a lead — Sell.Do deduplicates, assigns and scores it, and (if enabled) the AI voice agent calls it back within 30 seconds.

OAuth 2.0 Rate-limited HMAC webhooks
Request API access
create-lead.sh
curl -X POST https://api.sell.do/v1/leads \
  -H "Authorization: Bearer $SELLDO_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Priya Sharma",
    "phone": "+919812345678",
    "source": "portal",
    "project": "Riverside Residences",
    "budget": "3.0-3.3Cr"
  }'
API reference

Core endpoints

POST/v1/leadsCreate a lead — auto-deduplicated, assigned and scored.
GET/v1/leads/:idFetch a lead with full activity timeline.
PATCH/v1/leads/:idUpdate fields, stage or owner.
GET/v1/inventory/unitsList projects, towers and unit-level availability.
POST/v1/bookingsCreate a booking against a unit and customer.
GET/v1/bookings/:id/ledgerPull the customer ledger, demands and receipts.
GET/v1/reports/:keyRun any saved report and get structured rows.
POST/v1/webhooksRegister an endpoint for real-time events.

Full OpenAPI spec and reference docs are shared with API customers; request access to get your keys and the complete schema.

Webhooks

React in real time

Subscribe to events and Sell.Do pushes HMAC-signed payloads to your endpoint, with retries and a replayable delivery log.

lead.createdlead.stage_changedlead.assignedsite_visit.scheduledbooking.createddemand.raisedpayment.receivedcp.tagged
MCP

Every endpoint is also an agent tool

The same API powers Sell.Do’s MCP server — so beyond REST, your AI agents (Claude, ChatGPT or your own) can read and act on this data, governed by the same OAuth scopes and RBAC.

Developer FAQ

The API uses OAuth 2.0 with scoped bearer tokens. Every call is checked against the same RBAC and field-level security as the product, so a token can never see or do more than the user or app it represents.

Building an integration?

Tell us what you need and we'll get you API keys, the OpenAPI spec and the Postman collection.