Ceremonies describe how a recipient signs: the authentication method, the redirect behavior after completion, and the email content they receive. Previously, customizing a ceremony meant creating the envelope, waiting for it to be ready, and then calling POST /v1/recipients/{recipient_id}/ceremonies for each recipient. That round trip is now gone.
One request, fully configured
You can attach a ceremony object to any recipient in the envelope creation payload. The object supports the same authentication, redirect, and email settings available on the dedicated ceremony endpoint, so anything you could do before in two steps you can now do in one.
{
"title": "Service Agreement",
"recipients": [
{
"key": "client",
"type": "signer",
"name": "Emily Johnson",
"email": "emily@example.com",
"ceremony": {
"authentication": [
{
"type": "email_link",
"subject_override": "Please sign the Service Agreement"
}
],
"redirect_url": "https://example.com/done",
"redirect_delay": 5
}
}
]
}If you omit the ceremony object, SignatureAPI still creates a default ceremony with email_link authentication, so existing integrations keep working unchanged.
Migration notes
The previous ceremony_creation property is deprecated but remains supported for backward compatibility. New integrations should use the inline ceremony object. See the ceremony object docs and the create a ceremony reference for the full set of options.
