MB SuiteMB Suite
Menú

Referencia de la API · CRM

Registro de webhooks entrantes

crm · webhook_logs · 2 operaciones

GET/v1/crm/lead-sources/{source_id}/logsPOST/v1/crm/webhook-logs/{log_id}/retry
GET/v1/crm/lead-sources/{source_id}/logs

List the webhook deliveries of a lead source

crm.webhook_logs.list

LecturaIdempotenteDesde 2026-11-01

Lists what a lead source received through its webhook, newest first and paginated by cursor (limit up to 200): status (success, duplicate, error, rate_limited), the error, the stored payload, the lead created or matched (lead_id, with lead_kind: deal or prospect) and the person, and the retry state. Use it to find out why a lead did not arrive and which error entries can be retried with crm.webhook_logs.retry. Not found for deleted sources. Requires manage_sources (the entries carry the raw lead data). With Google Ads, LinkedIn or TikTok, their terms limit it through the API and the MCP: what they do not allow answers 403 platform_terms_restricted, and their fields are left out of the response (the permissions guide lists what each platform allows).

Alcance
crm:read
Permiso
Ver el módulo · Acción del CRM: manage_sources
Tool del MCP
crm_webhook_logs_listEn la superficie completa; en la compacta, mb_execute_operation con id: "crm.webhook_logs.list".

Costo declarado: hasta 603 lecturas y 0 escrituras por llamada (cuentan en el cupo diario).

Parámetros

source_idstringrutarequerido

The lead source: an id of crm.lead_sources.list.

limitintegerqueryopcional

How many items this page brings at most (see the maximum and the default in the schema).

Por defecto: 50

cursorstringqueryopcional

The next_cursor of the previous page, exactly as it came (only for the same list and filters); without it, the first page.

Respuesta

dataarray<object>
has_moreboolean
next_cursorstring

Errores

lead_source_not_foundcrm_action_deniedinvalid_inputunknown_fieldauthentication_requiredscope_insufficientmodule_access_deniedoperation_not_foundrate_limitedquota_exceeded

Ejemplo

curl "https://api.mb-suite.com/v1/crm/lead-sources/{source_id}/logs" \
  -H "Authorization: Bearer $MB_API_KEY"

Probar con tu API key de prueba

Con una API key de prueba el pedido va siempre a tu organización de práctica: datos de ejemplo que puedes reiniciar.

curl "https://api.mb-suite.com/v1/crm/lead-sources/{source_id}/logs" \
  -H "Authorization: Bearer $MB_TEST_KEY"
POST/v1/crm/webhook-logs/{log_id}/retry

Retry a failed webhook delivery

crm.webhook_logs.retry

EscrituraDesde 2026-11-01

Re-processes a failed webhook delivery from its stored payload through the same ingestion as the original (person and company matched or created, prospect or deal, dedup, assignment, notifications, scoring and sequences). Only error entries of generic webhook and MB Suite form sources are retryable, an entry already retried successfully cannot be retried again, and its source must exist and be active. Meta, TikTok and Google deliveries are recovered with the backfill in the app instead. Requires manage_sources.

Alcance
crm:write
Permiso
Editar en el módulo · Acción del CRM: manage_sources
Tool del MCP
crm_webhook_logs_retryEn la superficie completa; en la compacta, mb_execute_operation con id: "crm.webhook_logs.retry".
Eventos que puede emitir
crm.lead.createdcrm.deal.created

Costo declarado: hasta 22 lecturas y 11 escrituras por llamada (cuentan en el cupo diario).

Parámetros

log_idstringrutarequerido

The error entry to re-process: an id of crm.webhook_logs.list with retryable true.

Respuesta

duplicateboolean

Whether it matched a lead that already existed.

person_idstring
source_idstring
prospect_idstring

The prospect created or matched, when the source creates prospects.

deal_idstring

The deal created or matched, when the source creates deals.

Errores

webhook_log_not_foundcrm_action_deniedinvalid_inputunknown_fieldauthentication_requiredscope_insufficientidempotency_key_reusedrate_limitedquota_exceeded

Ejemplo

curl -X POST "https://api.mb-suite.com/v1/crm/webhook-logs/{log_id}/retry" \
  -H "Authorization: Bearer $MB_API_KEY"

Probar con tu API key de prueba

Con una API key de prueba el pedido va siempre a tu organización de práctica: datos de ejemplo que puedes reiniciar.

curl -X POST "https://api.mb-suite.com/v1/crm/webhook-logs/{log_id}/retry" \
  -H "Authorization: Bearer $MB_TEST_KEY"