ZapSign

Overview

The "Timestamp - Add Timestamp" operation in this node allows users to add a trusted timestamp to a document by providing a public URL of the document (PDF or DOCX, up to 10MB). This feature is useful for certifying the existence and integrity of documents at a specific point in time, which can be important for legal, compliance, or archival purposes.

Typical use cases include:

• Adding a timestamp to contracts or agreements before sending them for signing.
• Certifying official documents or reports to prove their creation date.
• Archiving documents with verifiable timestamps for audit trails.

Example: You have a PDF contract hosted on a public server. By providing its URL to this node, you can add a cryptographic timestamp to it, ensuring that the document existed unchanged at the timestamped moment.

Properties

Output

The node outputs a JSON object representing the response from the timestamp addition API call. This typically includes details about the timestamping operation such as confirmation status, timestamp ID, and metadata related to the timestamped document.

No binary data output is produced by this operation.

Dependencies

• Requires an API key credential for authenticating with the ZapSign API.
• The node uses environment variables to determine the API base URL, supporting sandbox and production environments.
• The document URL provided must be publicly accessible over the internet.
• The document must be in PDF or DOCX format and not exceed 10MB in size.

Troubleshooting

Common Issues

• Invalid or inaccessible document URL: The URL must be publicly reachable without authentication.
• Unsupported document format: Only PDF and DOCX files are supported.
• Document size exceeds limit: The file must be 10MB or smaller.
• Insufficient plan permissions: The timestamp feature may require a specific paid plan.

Error Messages

• 402 Payment Required:
  Indicates the current account plan does not include timestamp functionality.
  Resolution: Contact ZapSign support to upgrade your plan or enable timestamp features.

• 400 Bad Request:
  Possible causes include invalid document URL, unsupported file format, or file size exceeding limits.
  Resolution: Verify the document URL is correct, accessible, points to a PDF or DOCX file, and the file size is under 10MB.

• Network or request errors:
  Ensure network connectivity and that the API credentials are valid.

Links and References

• ZapSign API Documentation (for detailed API usage and error codes)
• Timestamping Concepts (general background on document timestamping)

This summary focuses exclusively on the "Timestamp" resource with the "Add Timestamp" operation as requested.