Receive enrichment results via webhook

Manifolds can send enrichment results to HTTPS endpoints that you provide. You can provide as many endpoints as you'd like.

Setting up

Webhook endpoints are self-serve: add one from your dashboard. You'll receive a per-endpoint secret (shown once) for verifying deliveries. After saving, choose Turn on now to start real deliveries immediately, or Send test & turn on to wait for a successful test. Delivery stays off until you choose one of these paths.

Below is the default webhook contract. The payload shape, cadence, filtering, and other parameters are configurable — let us know if you have specific needs or want to discuss options.

The default contract

Your endpoint should accept JSON and return a successful HTTP response once the request has been accepted.

Delivery

Method
POST
Content type
application/json
Success response
Any 2xx status
Timeout
10 seconds
POST https://your-domain.example.com/path
Content-Type: application/json

We treat non-2xx responses, network errors, and timeouts as failed attempts and retry on an escalating schedule (from 30 seconds up to 12 hours between attempts) for roughly two days before parking the delivery. A 410 Gone response tells us to stop retrying that delivery immediately.

Delivery is at-least-once: your handler should be idempotent; use delivery_id as the dedupe key. Redirects are never followed — respond directly from the registered URL.

The two event types

By default, we only send data when we have a match and enrichment data to share. Some users also want to be explicitly notified of no-match results, so you can opt in to receive a second event type for terminal no-match outcomes.

The payloads look a little different for the two event types, but they share a common envelope with metadata fields like event, organization_id, and occurred_at.

Matched enrichment event

This is the default event type that we send when we have enrichment data to share. It's identified by event value of enrichment_card.created. The contents inside data can be customized, but by default it looks like this:

{
  "event": "enrichment_card.created",
  "version": 1,
  "enrichment_id": "enr_33333333-3333-3333-3333-333333333333",
  "submission_id": "subm_77777777-7777-7777-7777-777777777777",
  "organization_id": "22222222-2222-2222-2222-222222222222",
  "occurred_at": "2026-04-13T16:00:00.000Z",
  "delivery_id": "66666666-6666-6666-6666-666666666666",
  "data": {
    "person": {
      "email": "ada@example.com",
      "fullName": "Ada Lovelace",
      "linkedinUrl": "https://www.linkedin.com/in/ada",
      "jobTitle": "Founder",
      "roleFunctionTags": ["engineering"],
      "roleSeniority": "executive",
      "emailAffiliation": "work"
    },
    "company": {
      "name": "AcmeCorp, Inc.",
      "website": "https://example.com",
      "linkedinUrl": "https://www.linkedin.com/company/example",
      "isYc": false,
      "totalFundingUsd": "2000000",
      "summary": "Short company summary...",
      "sizeBucket": "2-10",
      "sizeMin": 2,
      "sizeMax": 10,
      "verticalTags": ["software_it"],
      "capabilityTags": ["custom_software_services"],
    }
  }
}

No-match event

If you'd like, you can opt in to receive a webhook when we have a terminal no-match result (i.e. we've exhausted all data sources and have no relevant information to share). This event is identified by an event value of submission.completed and a data.result.outcome value of no_match.

{
    "event": "submission.completed",
    "version": 1,
    "delivery_id": "66666666-6666-6666-6666-666666666666",
    "organization_id": "22222222-2222-2222-2222-222222222222",
    "occurred_at": "2026-04-13T16:00:00.000Z",
    "data": {
      "submission": {
        "id": "subm_77777777-7777-7777-7777-777777777777",
        "received_at": "2026-04-13T15:59:00.000Z",
        "identifiers": [
          { "type": "email", "value": "ada@example.com" }
        ]
      },
      "result": {
        "outcome": "no_match"
      }
    }
  }

Authentication

Endpoints created from your dashboard get a per-endpoint secret, shown once at creation. Every delivery (including test events) includes it verbatim in a header:

X-Manifolds-Webhook-Secret: whsec_...

Verify it with a constant-time comparison against the secret you stored, and reject requests without it. (The whsec_ secret format is the industry-standard shape, but this is a plain shared-secret header — not an HMAC signature scheme, so signature verification libraries won't validate it. HMAC-signed deliveries using the same secret are planned; the plain header will keep working.)

Older endpoints set up before dashboard self-serve may instead rely on a high-entropy secret embedded in the URL path. That still works, but we recommend the header secret: URLs appear in our internal admin tooling, while the header secret is stored encrypted and never displayed after creation.

Test deliveries

From the dashboard you can send a test event to any endpoint. Test events carry the same envelope and the same X-Manifolds-Webhook-Secret header as real deliveries, with a distinct event value of webhook.test so you'll never mistake one for real enrichment data:

{
  "event": "webhook.test",
  "version": 1,
  "organization_id": "22222222-2222-2222-2222-222222222222",
  "occurred_at": "2026-08-25T16:00:00.000Z",
  "delivery_id": "99999999-9999-9999-9999-999999999999",
  "data": {
    "message": "This is a test event from Manifolds. Your endpoint is receiving webhooks correctly."
  }
}

A new endpoint starts with delivery off. If you choose to test before turning on, the first test event your endpoint answers with a 2xx turns delivery on automatically. You can also turn on immediately and test later. Testing records a successful test separately from delivery status; a failed test leaves your delivery setting unchanged. Once you've explicitly turned delivery on or off, tests never change that choice.