For the complete documentation index, see llms.txt. You can also append .md to any page URL to get its markdown version.
Skip to main content
For the complete documentation index, see llms.txt.

For the complete documentation index, see llms.txt

Upgrading the Enterprise signing engine

When your Enterprise signing solution receives its upgraded signing engine, you can continue using the Enterprise Sign API (Sign API v1) with the same request structure. The upgraded engine is the one used by our Sign API v2 on our Digital Trust Platform (DTP). The engine upgrade changes the long-term validation signed data object (LTV-SDO) returned for signed documents.

These changes apply when Signicat upgrades the engine behind your existing Sign API v1 integration. If you are migrating your integration directly to Sign API v2, use the Sign API v2 integration guide.

Do I need to act?​

Yes. If you use the Enterprise Sign API (Sign API v1), this upgrade affects you. Navigate to and read the page that matches your signature flow below to find out whether you need to change your integration.

LTV-SDO changes for Enterprise signing​

Check how the LTV-SDO changes affect your integration, then review the changes for each signing method you use.