> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stockinsights.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Webhooks v2 Overview

> Receive each event as the same object that the StockInsights API returns, signed with Standard Webhooks.

> [!NOTE]
>
> Webhooks v2 is not yet available in the dashboard. Until it is released, every
> destination receives [v1](https://docs.stockinsights.ai/webhooks/overview.md) payloads.

## What v2 is

In v2, the `data` of each event is the object that the StockInsights API returns
for the same filing. The keys have the same names, the same order and the same
value formats. Thus one parser reads both the API and the webhooks.

| | v1 | v2 |
| - | - | - |
| Event type | 3 generic types (`filing.created`, `filing.enriched`, `filing.updated`). You read `data.document_type` to know the filing. | One type for each event, for example `quarterly-result.created`. |
| `data` | A webhook-only shape | The API object of the filing, plus a few [webhook extras](#webhook-extras) |
| Signature | `X-StockInsights-Signature` (`t=…,v1=<hex>`) | [Standard Webhooks](https://docs.stockinsights.ai/webhooks/v2/authentication.md) (`webhook-id`, `webhook-timestamp`, `webhook-signature`) |
| Changes | — | An `.updated` event has `previous_attributes`: the old value of each field that changed |

The [delivery and retries](https://docs.stockinsights.ai/webhooks/delivery-and-retries.md) rules are the same in
v1 and v2.

## The envelope

Every v2 request has the same envelope. The envelope describes the event. The
filing is in `data`.

```json theme={null}
{
  "id": "evt_06afd889-e0df-7dde-8000-84708b20988a",
  "type": "quarterly-result.created",
  "api_version": "v2",
  "occurred_at": "2026-11-18T11:14:38.054517Z",
  "data": { "...": "the API object, see the event pages" }
}
```

**id** `string`

The event id: `evt_` and a UUID. It is also the `webhook-id` header. The same
event can arrive more than once, so de-duplicate on this id.

**type** `string`

The event type, for example `quarterly-result.created`. See
[Events](https://docs.stockinsights.ai/webhooks/v2/events.md) for the full list.

**api\_version** `string`

Always `v2`.

**occurred\_at** `string`

When the event happened, as an ISO 8601 timestamp in UTC.

**data** `object`

The API object of the filing. Its keys depend on `type`.

**previous\_attributes** `object`

Only on an `.updated` event. It has the old value of each field of `data` that
changed, in the same shape as `data`. A field that did not change is not in it.

## The rules of `data`

1. **Every key is always sent.** A key that has no value for this filing is
   `null`. The API leaves such a key out; the webhook sends it as `null`.
2. **A key that no filing of the event type has is left out.** For example, an
   India filing has no `cik`, and a quarterly result has no `form_type`.
3. **The values have fixed formats.** For example, `quarter` is `Q1` to `Q4`,
   `month` is the English name of the month, and `published_date` is
   `2026-07-13T08:45:00.000Z`. Each event page lists the formats.
4. **Link keys end in `_link`**, as in the API: `pdf_link`, `html_link`,
   `source_link`. `company_page_url` is the API's own name for the page of the
   filing on stockinsights.ai.
5. **Webhook extras come after the API keys.**
6. **Values are frozen at event time.** The webhook keeps the values of the
   moment that the event was made, for example the company name. The API shows
   the values of now.

## Webhook extras

These keys are in the webhook only. The API does not have them.

| Events | Extra keys |
| - | - |
| All document and announcement events | `country` (`"IN"`) |
| `earnings-transcript.*` | `file_link`, `transcript`, `recording` |
| `earnings-transcript.updated` | `change` |
| Financial statement events | `filing_id`, `ticker`, `source` |

## Where the values differ from the API

The keys are the same. A few values can differ:

* **Announcement id.** The webhook's `data.id` is the StockInsights id of the
  announcement. The API's `id` is the id that the exchange gave the
  announcement. The key name is the same, but the values are different.
* **Announcement `ai_insights`.** It is `null` on `announcement.created`,
  because the summary does not exist yet. `announcement.summary.created` has it.
* **Financial statement numbers.** The API reads the XBRL filing. The webhook
  reads the result PDF, which comes first, sometimes days before the XBRL. A
  later extraction can correct a number, with an `.updated` event. The webhook
  sends the numbers as extracted; the API rounds them to 2 decimals.
* **`company_page_url`** is `null` when the filing has no page yet.

## Events

> [card] [All events](https://docs.stockinsights.ai/webhooks/v2/events.md)
>
> The event types, their subscription keys, and when each one is sent.

> [card] [Authentication](https://docs.stockinsights.ai/webhooks/v2/authentication.md)
>
> Verify the Standard Webhooks signature of each request.

> [card] [Documents](https://docs.stockinsights.ai/webhooks/v2/documents/quarterly-result-created.md)
>
> Quarterly results, investor presentations and earnings transcripts.

> [card] [Announcements](https://docs.stockinsights.ai/webhooks/v2/announcements/announcement-created.md)
>
> New announcements and their AI summaries.

> [card] [Financial statements](https://docs.stockinsights.ai/webhooks/v2/financial-statements/overview.md)
>
> Income statement, balance sheet and cash flow from the result PDF.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.