user_record.expiring
A user record is coming up to its expiry date. Sent 30, 14, 7 and 1 days before it, at 9am in your account's timezone; `data.reminder_days` says which reminder this is and `data.days_until_expiry` how many days are left. A record that first comes within 30 days late gets only the latest reminder due, then the later ones.
POST to each webhook subscribed to this event.X-Astalty-SignaturestringrequiredHMAC-SHA256 of the raw request body, keyed with the webhook's signing secret and hex encoded. See Verifying the signature.
Payload
application/jsonidstring<uuid>requiredThe delivery ID. It stays the same across retries, so use it to ignore a delivery you have already processed.
event_typeenum<string>requiredThe event that occurred.
Available options:user_record.expiringresourceobjectrequiredThe record the event relates to.
▶Show 2 child attributesHide child attributes
idstring<uuid>requiredThe ID of the user record.
typeenum<string>requiredAvailable options:user_record
dataobjectrequired▶Show 2 child attributesHide child attributes
reminder_daysenum<integer>requiredWhich reminder this is: the number of days before the expiry date it is scheduled for.
Available options:301471days_until_expiryintegerrequiredWhole days from today to the expiry date, in your account's timezone. Lower than reminder_days when the record came within the window after that reminder was due.
The payload names the record but does not include it. Call this endpoint with resource.id to read its current details.
/public/v1/user-records/{userRecord}Return any 2xx status within 15 seconds to acknowledge the delivery. Anything else is retried up to 10 times over about 42 hours, so make your handler idempotent on the delivery id. See Retries and delivery.