partner.application_approved
Subscriby approved the creator's application to the Partner Program: their code is minted, their starting rate is set and their link attributes from this moment.
When this fires
The owner approved the application on the console. Fires once per approval; a creator whose application was turned down and who applied again gets it on the later approval.
Nothing fires when the application is filed. The creator filed it themselves and the page says it is under review; this event is the first thing an integration hears.
Caveats
- The rate here is the floor. Each commitment the owner verifies and each volume tier reached raises it; listen to
partner.rate_changedfor the moves. - The application's answers never travel. Who the partner is, where their audience lives and what they committed to stay on the account.
Related events
partner.rate_changed: every later move of the rate.partner.referral_signed_up: the first creator the link brings.
Ability to subscribe
A token needs this to subscribe an endpoint to the event.
Header Parameters
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=.
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.
The event name, the same as the envelope's type.
Always application/json.
Always Subscriby-Webhooks/1.0.
Payload
JSONWhat Subscriby posts to your endpointapplication/json
The signed JSON envelope posted to your endpoint.
The envelope every event is delivered in.
Responses
2XXAny success status
Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.
defaultAny other status
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.
How is this guide?
Last updated on