signNow API Updates & Release Notes

You can now read the field layout of an entire Document Group or Document Group Template in a single API call, instead of requesting each document separately.

• New: GET /v2/document-group-templates/{dgt_id} returns the template, its documents in order, and their roles.
• Extended: GET /v2/document-groups/{dg_id} now accepts documents.fields in the include parameter.

Add include=documents.fields to either request to retrieve documents[].fields. Each field uses the same object structure as GET /document/{document_id}, including type, role, and json_attributes (position, size, required, name, label, and prefilled text).

Without this parameter, fields are not returned.

This update makes it easier to check field configurations and identify which fields to pre-fill before sending an invite.

SignNow now exposes two new fields in the Document Group API response, completed_at and expires_at, so you can track the full lifecycle of a document group in a single call. Instead of calculating expiration dates manually or piecing together completion times from webhook history, you can retrieve precise timestamps directly from the endpoint. This gives you a clearer, more efficient way to monitor deadlines and finalization status across your document group workflows.

When you call GET /v2/document-groups/{document_group_id}, the response now includes completed_at and expires_at as top-level fields. Both return Unix timestamps based on the group's current state. If no invite has been sent, both fields return null. While an invite is in progress, expires_at shows the active deadline and completed_at remains null. Once the group reaches a completed state, completed_at reflects the exact completion time and expires_at returns null. The endpoint maintains full backward compatibility, and the updated fields are documented in the API reference.

We’ve launched an updated API Documentation Portal designed to make integrating SignNow into your applications faster, smoother, and more intuitive. Whether you are building your first integration or scaling an existing setup, everything you need is now available in one centralized hub.

Key Highlights

• All-In-One Developer Hub: Effortlessly navigate API references, integration guides, and ready-to-use code samples for Node.js, PHP, Python, and Java.
• Blazing Fast Navigation: Enjoy instant page loads and a powerful global search tool that surfaces the exact endpoint or guide you need within seconds.
• AI-Ready Documentation: Export any documentation page as clean Markdown simply by appending {{.md}} to the URL—making it effortless to train custom AI tools or automate workflow scripts.

Visit the new portal today to explore the updated experience and streamline your signature workflows.

SignNow now supports the approver role within embedded signing workflows for both individual documents and document groups.

This update extends the embedded signing API, giving you full control over approval steps, enabling you to build complete review-and-approve workflows directly within your integrated applications. By including approvers alongside signers, you can streamline multi-step processes without requiring participants to leave your platform.

To add an approver, include an approvers array in your document embedded invite request with the approver's email, role, signing order, and optional parameters such as authentication type, subject, first name, last name, and message.

For document groups, set the {{approver}} role for each signer object in the {{documents}} array.

Each step supports one approver, and the approver's email must differ from any signer email within the same step.

Approvers can receive their invite through both email and link delivery types.

Once the invite is created, you can retrieve a valid approver link using the standard link endpoint.

Approvers review and approve documents without generating a signature, keeping the workflow clean and role-appropriate.