Why expiration 0 means the link does not expire

Each send can set how many days the signing link stays valid. The default is 14. Set the field to 0 if the link should not expire. That is expiry-zero honesty: 0 is no window, not a same-day close, not “expire immediately,” and not a mute on the first invite. The hourly cron will not mark that SENT envelope expired for a clock you turned off.

Picking a positive window is how to choose an envelope expiry. The other zero — skip nudges — lives next to it on the same send form and is not this field. Cadence versus a real window is reminder cadence versus envelope expiry. After a window actually ends, expired is not voided. Desk help is Docs. This guide is the 0 on expiration, not the 0 on reminders.

Ask Inkpacket for expiration 0 means the link does not expire to open this article. Ask how does expiration work to open help. Ask set expiration to open the send form. Those phrases stay on the product screens. This article is the public version of why a 0 in that box does not kill the token tonight.

Two zeros on the send form

• Expiration 0 — the link does not expire. Status can stay sent until they sign, decline, or you void.
• Reminder interval 0 — skip reminders on that envelope. The first invite still goes out. The window, if set, still ends.
• Both 0 — no nudges and no clock. You still have void, correct, and resend while it is sent.
• Neither 0 — workspace defaults, usually remind every 3 days and expire in 14.

Owners and admins can change those defaults in Settings. More on reminders matches the send form. A Web Form can inherit or set its own reminder and expiry on publish — Web Form reminders and expiry on publish. Expiration 0 on a published form means fills from that share link also skip the window. It does not mean the public slug stays up forever — disable is a different verb.

What expiry zero is not

• Not expire-now. If you need the link dead today, void the sent envelope.
• Not a Free-plan unlock. Checkout does not sell “no expiry.” The field is on every send.
• Not a skip of sequential waiting. Later signers still wait — first-signer waiting message.
• Not an un-expire. You cannot type 0 onto an already expired row. Send a new envelope.

An envelope with no expiry can still stall. Reminders, if you left a positive interval, will keep nudging outstanding invited people. Uninvited later sequential signers still do not get those mails — reminders skip uninvited sequential signers. If the deal is off, void. Do not wait for a clock you set to 0.

The click-path

1. On Documents → new, find #expiration. Default 14 unless Settings changed it.
2. Type 0 only if you mean the link should not expire. Scan reminder interval so you do not confuse the two zeros.
3. Send. Copy the signing link if mail skips. The token will not die at day 14.
4. If you change your mind after send, you cannot edit the window on that id. Void and send again, or leave it open.
5. On a phone, the send form is still Documents. Expiration is not a drawer row of its own.

Public API send accepts the same expiration days. 0 means no expiry there too. An Idempotency-Key on send replays that body — do not reuse a key after you flip 14 to 0. Idempotency-Key on create, fill, and send is that 409. Reminders go out by email today. Text-message (SMS) is coming soon. Email still soft-fails. Text-message (SMS) is coming soon. Drive missing: Drive not configured.

Ask and the list

Ask Inkpacket for expiration 0 means the link does not expire to open this article. Ask what is envelope expiry to open help. Marketing Ask stays site Q&A and deep links. It will not set the field or void a stall from this article. The document list will keep a SENT badge on a no-expiry envelope until someone finishes or you stop it. That is not list-aging lying to you — there is no overdue window to mark.

Caps and what is not open yet

Setting expiration is not a send by itself. Send is. Free allows 5 packets a month. Free at 5 packets a month is the live cap desk send, bulk rows, Web Form fills, and API send share. Hitting it returns HTTP 402 ENVELOPE_LIMIT. Starter is 20 envelopes — more than Free — plus 3 published Web Forms. Seat counts are planning numbers; invite does not refuse when a workspace is full.

Billing is published, not charging. Checkout is not open. Text-message (SMS) is coming soon. Drive missing: Drive not configured. Stripe off: Payments not live. Those flags do not turn 0 into expire-now or sell a longer window. The FAQ and More on reminders use Set the field to 0 if the link should not expire in the same words.

Type 0 when you mean no clock. Type a positive day count when you want the cron to close it. File the envelope when they sign. Open a workspace on Free — see published pricing — and send one throwaway with expiration 0 so expiry-zero honesty is a SENT row that stayed SENT past day 14, not a dead link you thought 0 would kill.