Webhook events

Each delivery uses the { event, data } envelope from Outbound delivery. This page lists event names and what you should expect under data for documents and templates.

Document payloads usually include a document object with public id, title, status, timestamps, and metadata. Other fields (such as signers, recipients, or account) appear when they apply to that event.

Document events (document.*)

Event	Summary
document.created	Payload includes document, created_by, optional account.
document.updated	document, updated_by, optional account.
document.out_for_signature	document, sent_by, recipients.
document.waiting_on_me	document, sent_by, recipients.
document.completed	document, optional completed_by, signers.
document.declined	document, declined_by, optional declined_at, decline_reason.
document.voided	document, voided_by, voided_at, optional reason.
document.expired	document.
document.failed_delivery	document, recipient, failed_at, optional failure_reason, error_code.
document.deleted	document, deleted_by, deleted_at.

Template events (template.*)

Event	Summary
template.created	template, created_by.
template.updated	template, updated_by, optional changes.
template.deleted	template, deleted_by, deleted_at.

Which subscriptions receive an event

When you register a webhook, you choose a subscription type (for example, events about documents). Upsign delivers each event only to subscriptions whose type matches that event family—document.* events go to document-type subscriptions, template.* to template-type subscriptions, and so on. Traffic is always scoped to your company, so you only see activity for your tenant.