Changelog
Status PageRoadmapTestimoniesShare feedback
Back to All
Improved

Planned API behavior correction on Custom Experience

September 2nd, 2026

Signature Requests created from a Template will inherit the Template's Custom Experience when custom_experience_id is omitted from the request.

This aligns the API behavior with the application and with the pre-configured elements of the Template.

Existing Signature Requests are not affected.

  • Providing a custom_experience_id continues to override the Template's Custom Experience.
  • Providing custom_experience_id: null explicitly creates the Signature Request without a Custom Experience.
  • If your integration currently relies on the absence of custom_experience_id to create an unbranded Signature Request, explicitly set the field to null after September 8th, 2026.