> For the complete documentation index, see [llms.txt](https://manual.personr.co/api-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.personr.co/api-documentation/entity-results/retrieving-entity-verification-results/setting-up-a-webhook/ownership-ready-webhook.md).

# Ownership ready webhook

Get notified once an entity's ownership structure has finished, so you know when to fetch it.

Owners can be found a short time after the verification result is sent, especially for companies with several layers of ownership. The ownership ready webhook tells you when that work has finished, so you can fetch the structure once instead of waiting a fixed time.

{% hint style="info" %}
This webhook is opt-in. Ask us to turn it on for your workspace. It is sent to the same endpoint, with the same token in the header, as the [Setting up a webhook](https://manual.personr.co/api-documentation/entity-results/retrieving-entity-verification-results/setting-up-a-webhook.md).
{% endhint %}

#### When it is sent

Once per entity, about 2 minutes after the last owner is found or the verification result is sent, whichever is later. If another owner is found in that time, the 2 minutes start again, so you receive one webhook rather than one per owner.

An entity with no owners still sends the webhook, with `ownershipCount` set to `"0"`.

#### Webhook Response

```json
{
  "event": "entity.ownership_ready",
  "applicantId": "1725329761404x0000000000000",
  "ownershipCount": "3",
  "sourceKey": "Example Source Key",
  "externalUserId": "[\"user_123\"]",
  "sentAt": "2026-11-03T03:19:23.417Z"
}
```

| Field            | Description                                                |
| ---------------- | ---------------------------------------------------------- |
| `event`          | Always `entity.ownership_ready`                            |
| `applicantId`    | The entity's ID                                            |
| `ownershipCount` | Number of owners found, as text                            |
| `sourceKey`      | The source key you set when creating the entity, or `null` |
| `externalUserId` | A JSON-encoded string of your external user IDs            |
| `sentAt`         | When the webhook was sent (ISO 8601, UTC)                  |

When you receive it, call [Retrieving entity ownership structures](https://manual.personr.co/api-documentation/entity-results/retrieving-entity-ownership-structures.md) to get the full structure.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://manual.personr.co/api-documentation/entity-results/retrieving-entity-verification-results/setting-up-a-webhook/ownership-ready-webhook.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
