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

# Downgraded

> Event data sent for a Loyalty v2 DOWNGRADED transaction handled by Workflows

The `DOWNGRADED` event indicates that a member moved to a lower Loyalty v2 tier.

<Note>
  This page documents only the event data nested under `data`. See [Introduction to webhooks](/api-reference/introduction-to-webhooks) for the shared webhook structure, and [Workflows webhooks](/api-reference/workflows-webhooks) for the full Workflows webhook payload.
</Note>

This event can trigger a workflow when **Loyalty transaction** is configured with the **Tier transactions** group and the `DOWNGRADED` transaction type. If the workflow reaches a **Webhook callout** action, Voucherify sends a webhook to the action's target URL.

Workflows send this transaction in the `data.trigger` object. The example uses the `APPROVED` status. A workflow can filter the trigger by transaction status: `PENDING`, `APPROVED`, or `REJECTED`. The matched status is available in `data.trigger.transaction.status`; it does not create a separate event type.

Voucherify creates this transaction when the member no longer qualifies for the current tier and a lower tier still applies. If no tier applies, the transaction is `LEFT`.

* The tier structure has no retention, and the member's points qualify for a lower tier.
* The member's retention period has ended and the member qualifies for a lower tier. While retention is still active, Voucherify keeps the current tier and creates an `EXPIRATION_CHANGED` transaction instead. The downgrade is created when the expired tier is recalculated.
* `MULTI_LEVEL` moves the member to the tier the points qualify for. `SINGLE_LEVEL` moves the member one tier below the highest tier reached in the current cycle, even when the points qualify for a lower tier or for none. A later drop in the same cycle does not drop another level. That recalculation is an `EVALUATION_REFRESHED` transaction.

A tier structure with `NO_DOWNGRADE` never creates this transaction. The member stays in the current tier, and the recalculation is an `EVALUATION_REFRESHED` transaction.

`details.tier_from` and `details.tier_to` are tier IDs. They are not nested tier objects.


## OpenAPI

````yaml openapi-events/events-loyalty-transaction.json webhook DOWNGRADED
openapi: 3.1.0
info:
  title: Events - Events loyalty transaction
  version: '2024-01-01'
  description: ''
servers: []
security: []
paths: {}

````

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