Uploads in SignatureAPI have historically been temporary, with a 24-hour expiry. That is a sensible default for one-off envelopes, but it is a poor fit for assets you reuse, such as a company logo, a signature image for an automatic signer, or a contract template referenced across thousands of envelopes.
The new Store endpoint solves this. Call POST /v1/uploads/{uploadId}/store with a unique key, and the upload is promoted to permanent storage. The id and url stay the same, retention flips from temporary to permanent, and expires_at is removed from the object.
How it works
The key you provide is unique within your account and follows a simple format: lowercase letters, numbers, hyphens, and underscores, up to 100 characters. Use something stable and descriptive, for example acme-logo or contract-template-v2, so your application can reference the stored file by a predictable name.
Once stored, the upload behaves like any other upload for the purposes of envelope creation. Reference its URL in document sources, branding logos, or signature and initials images for automatic signers, and the same file serves every envelope that uses it.
When to use it
Reach for the Store endpoint whenever you find yourself uploading the same bytes more than once. Good candidates include brand assets used across envelopes, document templates that feed a high-volume workflow, and signature images applied by automatic signers. For anything genuinely single-use, the temporary default still applies and no action is needed.
See the Store endpoint docs for the full request and response shape.
