partner.* events

A full refund, a dispute or a rejected review reversed a commission, or clawed back one already settled.

When this fires

The platform charge that earned a commission was refunded in full (reason: refund) or disputed (reason: dispute), or Subscriby rejected a referral it had held for review (reason: rejected). A row never settled is reversed in place; a row already credited or paid is answered with a clawback, a second row carrying the negative amount, so the partner's balance drops and the next credit or payout nets it off. One event per commission touched.

A partial refund changes nothing. Subscriby kept most of the money, and the rule a partner can be told is the simple one: only a full refund or a dispute takes a commission back.

Caveats

  • A redelivered refund writes no second clawback. The second delivery finds the rows reversed and the clawback written, and touches nothing.
  • A dispute reverses on the day it opens, because the money is withheld from then; a dispute later won is not revisited.
  • A rejected review reverses every commission the referral earned, and the referral earns nothing further.

Related events

  • partner.reward_credited: where a clawback is netted off on the credit rail.
  • partner.payout_recorded: where a clawback is netted off in cash.
postWebhookpartner.reward_reversed

Headers

SB-Signaturestring required

t=<unix seconds>,v1=<hex>: the HMAC-SHA256 of "<t>.<raw body>" under the endpoint's secret. Verify it before acting, and refuse a t more than 300 seconds from now. During a secret rotation a v0= signature under the previous secret may precede v1=.

SB-Event-Idstring required

The event's ULID, bare. The envelope's id is the same ULID prefixed evt_, so strip the prefix before comparing. Deduplicate on it: a retry carries the same id.

SB-Event-Namestring required

The event name, the same as the envelope's type.

Content-Typestring required

Always application/json.

User-Agentstring required

Always Subscriby-Webhooks/1.0.

Payload

idstring required

A ULID unique to the event, prefixed evt_. Every retry carries the same id, so it is the key to deduplicate on.

type'partner.reward_reversed' required

The event name, always partner.reward_reversed here.

created_atstring date-time required

When the event was emitted, server time, ISO 8601.

api_versionstring required

The contract version of the payload shape, 2026-05-01 today. A breaking change to a shape ships under a new version.

project_idstring uuid nullable required

The project the event belongs to; null for team-scoped and billing events.

Response

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

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.