Integrations

API, Webhooks & Web Tracking

Build on Sell.Do — open REST API, HMAC webhooks, and first-party web/visitor tracking.

app.sell.do
API, Webhooks & Web TrackingBuild on top of Sell.DoAPI keysREST APIOpenAPI 3.1POST/v1/leads{"name": "Anjali Naik","phone": "+9198XXXXXX21","source": "microsite","utm_campaign": "pune_3bhk"}201 Created · lead_id 88421Webhookssigned, retriedlead.createdlead.stage_changedbooking.createdpayment.receiveddemand.raisedunit.status_changedHMAC-signed · 3 retries · DLQWeb trackingA JavaScript snippet ties anonymous website sessions to the lead once they enquire — so you see every page they read before they called.Also availableMCP server for AI agents, OAuth apps for the marketplace, and a sandbox tenant for every integration partner.

The problem teams live with

The integration you need does not exist yet, and the vendor's answer is a roadmap. So your team builds a nightly CSV export, someone forgets to run it, and the microsite that should create leads instantly emails them to an inbox instead.

How Sell.Do solves it

Sell.Do is an API first and a screen second. A documented REST API covers leads, inventory, bookings, ledgers and reports; HMAC-signed webhooks push events as they happen, with retries and a replayable delivery log; and a JavaScript snippet ties anonymous website sessions to the lead once they enquire. Everything the interface can do, a token can do — under the same permissions.

How it works

API, Webhooks & Web Tracking, step by step

  1. 1Open REST API & tokens
  2. 2HMAC-signed webhooks
  3. 3First-party website visitor tracking
  4. 4Elasticsearch-powered search & listing

REST API, signed webhooks and web tracking — governed by the same permissions as the product.

What you get

Built for the real workflow

  • Open REST API & tokens
  • HMAC-signed webhooks
  • First-party website visitor tracking
  • Elasticsearch-powered search & listing
Jarvis AI

Every endpoint is also an agent tool

The same API powers the Sell.Do MCP server, so your AI agents read and act on this data under the same OAuth scopes and role permissions as a human — no shadow access path.

OAuth 2.0
Scoped, RBAC-enforced
HMAC
Signed webhooks, replayable
Same rules
For humans, apps and agents

Frequently asked questions

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

See API, Webhooks & Web Tracking on your own pipeline

Book a 30-minute walkthrough tailored to your projects, team and process.