Skip to content
Sent 24/7 Docs

Buyer integration checklist

  1. Receive your webhook URL configuration

    Your account manager has configured a delivery webhook on the Sent 24/7 side. They’ll share the field mapping, payload format, and the signing secret (if signed-webhook verification is on).

  2. Stand up an inbound endpoint

    Accept POST from Sent 24/7. Return a 2xx within 5 seconds. The platform retries up to 5 times over 24 h on failure — your endpoint should be idempotent on leadId.

  3. Generate a postback API key

    Ask your account manager to mint a pk_live_… key from the dashboard (Buyers → you → Portal → Generate key). The plaintext is shown once — store it in your secrets manager immediately.

  4. Wire up disposition postbacks

    When your CRM advances a lead’s stage (Sale, Won, Lost, etc.), POST to /api/v1/postback/leads/{leadId}/disposition. Use one Idempotency-Key per logical event so dialer retries don’t double-fire.

    If your CRM doesn’t keep our leadId, post to /api/v1/postback/disposition with the customer’s phone or email instead. That is the easy route from Zapier or Make: see Report sales from Zapier or Make.

  5. Wire up rejection postbacks

    For bad leads that fall outside your account’s rejection policy (wrong number, duplicate, etc.), POST to /api/v1/postback/leads/{leadId}/reject. Check your account’s allowed reasons and window in the portal or the doc your account manager shared.

  6. Verify end-to-end

    The buyer portal’s Leads tab will reflect every postback in real time. If a postback doesn’t move a lead, the response body will tell you why (policy / pipeline / window).

Common gotchas

Section titled “Common gotchas”
  • Seller key on a buyer endpoint → 403. sk_live_… is for lead submission; postbacks need pk_live_….
  • Window expired → 400. Default is 72 hours after delivery; check with your account manager if you need a longer one.
  • Reason not in allowlist → 400. The list is per-buyer; the portal’s API page (/portal/api) shows yours live.