Black Friday Black Friday: the new LetsBot bundles save up to 60% — until 30 November only. See the bundles See the bundles
LetsBot Menu
Get Started English Language

Verified Meta Tech Provider UK Registered Company

Language

CRM help

CRM API and webhooks: connect your own systems

  • LetsBot Editorial Team
  • 2 min read
  • 149 views
CRM API and webhooks: connect your own systems

The CRM API lets your developers, ERP or website read and update CRM records. Webhooks push a change to your system the moment it happens, so you don’t need to poll. Both are on the API & webhooks page in the CRM settings.

Authentication

  • Create a workspace API key and tick the crm permission. Keys without it can’t reach the CRM, so existing keys are not affected.
  • Send the key in the X-Zapier-Api-Key header.
  • A key acts for the whole workspace: it sees every CRM record, whatever the team permissions are. Keep it on your server, never in a browser or app.

What you can do

ResourceEndpoints under /api/v1/crm
Contactslist, search, schema, create, read, update, add a note
Companieslist, search, schema, create, read, update, delete, link contacts, add a note
Dealspipelines, lost reasons, list, search, create, read, update, delete, move stage, mark won or lost, add a note
Taskslist, create, read, update, delete, complete
Activitieslist, create, read
Quotes and productslist, schema, create, read, update, delete

The page shows your workspace’s base URL and links to the full API reference.

Webhooks

  1. Only the workspace owner can add webhooks. Choose Add webhook.
  2. Enter an HTTPS address on the public internet, for example https://example.com/letsbot/webhooks.
  3. Pick the events: contact, company or deal created, updated or deleted; deal stage changed, won or lost; task created or completed; ticket created; quote sent, viewed or accepted.
  4. Copy the signing secret — it is shown only once.
  5. Use Send test event and check the Delivery log.

Check the signature

Each request carries X-LetsBot-Signature: t=<unix seconds>,v1=<hex>. Compute HMAC-SHA256 of <t>.<raw body> with your secret, compare it with v1, and reject requests whose t is more than 5 minutes old. X-LetsBot-Event names the event.

Retries

If your URL fails, LetsBot retries after about 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours. A webhook that keeps failing, or that answers HTTP 410, is switched off; fix the URL and turn it back on. You can also send any delivery again from the log.

LetsBot Editorial Team
Written by

LetsBot Editorial Team

Editorial & Product Team — LetsBot

The LetsBot editorial team blends our engineering, product, and customer-success teams — every piece is grounded in real performance data from 250+ businesses on the platform across 8 Arab markets.

  • WhatsApp Business API
  • Conversational AI
  • Customer Success
  • E-commerce Integration

From reading to doing

Ready to try LetsBot yourself?

14-day free trial, no credit card, full setup in under an hour.