> For the complete documentation index, see [llms.txt](https://developer.securecontainerrelease.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.securecontainerrelease.com/how-to/configure-event-notifications-and-webhooks/event-types./onrelease.md).

# onRelease

The onRelease event type covers when any of the following events takes place:

1. A release has been **transferred** to your organization.
2. A release that has been **transferred** to your organization and is:
   1. **updated**;
   2. **blocked**;
   3. **unblocked**;
   4. **deleted**;
   5. **revoked**.

{% hint style="info" %}
Please note that for transfers and revokes of releases that are executed by your own organization (through the API or web app), a notification is also sent to the callback endpoint.&#x20;
{% endhint %}

This way you can update your internal systems when releases are transferred or revoked manually, in the SCR web application.

#### Payload&#x20;

When the `onRelease` event occurs, the callback is invoked with the following data:

<table><thead><tr><th width="174">Value</th><th>Description</th></tr></thead><tbody><tr><td><code>release</code></td><td>The address of the release.</td></tr><tr><td><code>event</code></td><td><p>A string denoting the event, being one of the following: </p><p><code>transfer</code>, <code>update</code>, <code>block</code>, <code>unblock</code>, <code>delete</code>, <code>revoke</code>*, <code>greenlights</code>.</p></td></tr><tr><td><code>organization</code></td><td>The address for which the event is reported.</td></tr><tr><td><code>vat</code></td><td>The VAT no of the organization for which the event is reported.</td></tr></tbody></table>

*The last two fields are added for organizations with multiple legal entities. This way, you can collect the notifications using one endpoint and route them to the correct (internal) system using these fields.*

&#x20;*\** For `revoke` action, the following parties are notified:

* If the API is version 1.2.3 or lower only the current and the new owner receive a notification in the API.
* If the API is version 1.2.4 or higher all organizations that are in the ownership chain of the release receive a notification in the API.

#### EXAMPLES

Please see below examples of `onRelease` events:

{% tabs %}
{% tab title="TRANSFER to your organization." %}

<pre class="language-json"><code class="lang-json">{
    "release": "0x000000000000000000000000000000000000000",
    "event": "TRANSFER",
    "organization": "0x000000000000000000000000000000000000000",
<strong>    "vat": "BETEST"
</strong>}
</code></pre>

{% endtab %}

{% tab title="Update of the Green Lights." %}

<pre class="language-json"><code class="lang-json">{
<strong>    "release": "0x000000000000000000000000000000000000000",
</strong>    "event": "GREENLIGHTS",
<strong>    "organization": "0x000000000000000000000000000000000000000",
</strong>    "vat": "BETEST"
}
</code></pre>

{% endtab %}
{% endtabs %}

{% hint style="info" %}
After you have received the event you would want to [retrieve the latest data](/how-to/configure-event-notifications-and-webhooks/fetch-latest-data-after-receiving-event-notification..md).
{% endhint %}
