member.trial_joined
A subscriber joins on a trial via cardless trial or access-code redemption.
When this fires
Two paths emit this event:
- Cardless trial start: a subscriber begins a trial that took no payment method.
- Access-code redemption on a trial plan: the redeemed plan sets
trial_ends_at, so this fires in place ofmember.joined.
A Stripe checkout that begins with a trial window emits subscription.activated and subscription.trial_started, but no member.* join event. Like member.joined, this event covers zero-payment acquisition only.
The data keys differ by path. Absent keys are omitted entirely, not sent as null.
Caveats
- A trial-joined member emits
member.convertedif the trial converts to paid, or rolls intomember.churnedonce the trial expires without converting. member.convertedis currently emitted for Stripe only. Trials taken through other providers will not produce a conversion event.subscription.createdandsubscription.trial_startedfire alongside this event on both paths.
Related events
subscription.trial_started: fires alongside.member.converted: fires on successful trial conversion (Stripe only).member.joined: non-trial counterpart.
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