Webhooks

Webhooks push new signals to your endpoint the moment they are confirmed and stable, so you don't have to poll. Available on the Growth and Scale plans.

How it works

You register an HTTPS endpoint and choose which event types you want. When a signal is confirmed, Datahyena sends a POST with a JSON body. A signal fires once, after it has settled, so you receive a complete record rather than a half-formed one.

Next: Security covers signature verification and retries, and Filters covers narrowing what each endpoint receives.

Events

Payload

Every delivery uses the same envelope. data is the exact single-record response from the REST API, so you can parse it with the same code.

{
  "id": "018f...",
  "event": "funding.created",
  "createdAt": "2026-06-06T12:00:00.000Z",
  "data": {
    "success": true,
    "data": {
      "id": "018e...",
      "company": { "name": "Acme AI", "domain": "acme.ai", "hqCountry": { "code": "US", "name": "United States" }, "industryGroup": "Software Development" },
      "round": "series-a",
      "amountUsdCents": 1200000000,
      "investors": [{ "id": "018d...", "name": "Example Ventures" }],
      "announcedAt": "2026-06-05"
    },
    "meta": { "endpoint": "funding_events.item" }
  }
}

Nullable fields

A signal can be delivered before every detail is resolved, so treat enrichment and extraction fields as optional. The full per-field contract (and which are nullable) is in the API reference.

Always present: the event id, company.name, discoveredAt, and at least one entry in sources.

May be null:

• Company firmographics until the company is resolved/enriched: company.id, company.domain, company.linkedinHandle, company.hqCity, company.hqCountry, company.industryGroup, company.foundedYear, company.description, company.businessModel, company.employeeCountBucket.
• Deal details when not stated in the source: round, amountUsdCents / amountUsd, announcedAt.
• investors may be an empty array.