---
title: "A coupon was removed, carrying its final snapshot."
method: POST
path: "coupon.deleted"
tags: ["coupon.* events"]
---

# A coupon was removed, carrying its final snapshot.

`POST coupon.deleted` (webhook)

### When this fires

A creator deleted a coupon through the delete endpoint. Deletions from the dashboard or the bot do not currently emit this event; those surfaces write through the service layer directly.

The payload is a snapshot taken **before** the delete, so this is your last chance to record what the code was. Read it and store what you need; the code stops resolving at checkout the moment the delete goes through.

> **The code stops working, the history stays.** The coupon row is soft-deleted and its redemption records are left in place; attribution in your own reporting is not lost. What goes is the code itself: it stops resolving at checkout immediately. To retire a code while keeping it visible to creators, use `coupon.deactivated` instead.

### Caveats

- **A delete can be refused.** If any subscriber holds a live reservation (a checkout in flight with this discount already quoted to a payment provider) Subscriby refuses the delete and asks the creator to switch the code off instead. No event fires in that case, because nothing happened.
- **The coupon is soft-deleted, not erased.** [The coupon endpoint](https://docs.subscriby.net/api/v1/reference/coupons) currently still resolves it, because the lookup runs unscoped, so do not use a 404 to detect deletion; treat this event as the authoritative signal and store what you need from this payload.
- **No counts.** As with every lifecycle event, the snapshot omits redemption counts. If you need a final tally, keep a running total from `coupon.redeemed` rather than trying to read one at delete time.

### Related events

- `coupon.deactivated`: the non-destructive way to retire a code.
- `coupon.created`: the same snapshot shape, at the other end of the life.

## Headers

- `SB-Signature` string, required
- `SB-Event-Id` string, required
- `SB-Event-Name` string, required
- `Content-Type` string, required
- `User-Agent` string, required

## Payload

- object: The envelope every event is delivered in.
  - `id` string, required: A ULID unique to the event, prefixed `evt_`. Every retry carries the same id, so it is the key to deduplicate on.
  - `type` 'coupon.deleted', required: The event name, always `coupon.deleted` here.
  - `created_at` string, date-time, required: When the event was emitted, server time, ISO 8601.
  - `api_version` string, required: The contract version of the payload shape, `2026-05-01` today. A breaking change to a shape ships under a new version.
  - `project_id` string, uuid, nullable, required: The project the event belongs to; null for team-scoped and billing events.
  - `data` object, required: The event-specific payload. Keys that do not apply to a given emission are omitted rather than sent as null, so check for presence.
    - `coupon` object, required: The same snapshot every `coupon.*` lifecycle event carries. It reflects the coupon's state immediately **before** deletion, so `active` may well be `true`. Read back from the database, so `discount_value` and `minimum_amount` carry four decimal places.
      - `id` string, uuid, required: The coupon's UUID.
      - `code` string, required: The redeemable string, always uppercase.
      - `name` string, required: Creator-facing label.
      - `discount_type` 'percentage' | 'fixed', required: Whether `discount_value` is a percent or an amount.
      - `discount_value` string, decimal, required: The discount, four decimal places.
      - `currency_id` string, uuid, nullable, required: `null` on a percentage coupon; set on a fixed-amount one.
      - `duration` string, required: Which charges the discount applies to; only `once` is authorable.
      - `max_redemptions` integer, nullable, required: Total cap across everyone. `null` means unlimited.
      - `max_redemptions_per_user` integer, required: Per-subscriber cap.
      - `minimum_amount` string, decimal, nullable, required: Order floor in the plan's own currency; `null` means no floor.
      - `starts_at` string, date-time, nullable, required: When it became redeemable. `null` means immediately.
      - `expires_at` string, date-time, nullable, required: When it was to stop. `null` means it ran until switched off.
      - `active` boolean, required: Whether the creator had it switched on at the moment of deletion.

## Acknowledgement `2XX`

Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.

## Other responses

- `default`: Any other status, a connection failure, or no answer within 30 seconds counts as a failed attempt. The delivery is retried 8 times, after 10 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, 1 day, 3 days; the last failure dead-letters it, and it can be retried from the dashboard or `POST /v1/webhook-deliveries/{delivery}/retry`. After 20 consecutive failures the endpoint is paused until it is resumed.

---

[API](https://skmtc.dev/memberpass/apis/subscriby-rest-api.md) · [All operations](https://skmtc.dev/memberpass/apis/subscriby-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/memberpass/apis/subscriby-rest-api/revisions/59c4df91d764?raw)