Why This envelope can no longer be edited is not a completed lock

PUT /api/v1/packets/:id/fields replaces marks. POST /api/v1/packets/:id/fill writes values by id or label. Both refuse a closed envelope with This envelope can no longer be edited. Closed here means completed, expired, voided, or declined. A sent envelope cannot move marks either. Field placement and routing lock when you send. Filling an existing field still works until someone has signed. That is edit-lock honesty: the field tool is shut once the envelope leaves draft, envelope admin only corrects a signer, and opening Billing will not “unlock edit after send.”

Why void, correct, and resend hide on a filed copy is why completed envelopes cannot be changed. Why drafts hide those three verbs is why only sent envelopes can use void, correct, or resend. Why a second void names the status is why This envelope is already voided is not a completed lock. Desk help is Docs. This guide is why fill and field replace name a closed envelope, and why that name is not an admin lock.

The FAQ and API on Features keep create, fill, and send on the same id. Ask Inkpacket for why This envelope can no longer be edited is not a completed lock to open this article. Ask how the API works to open help. Those phrases stay on the product screens. This article is the public version of This envelope can no longer be edited — the string help already uses next to fill and fields.

What edit lock covers

• PUT fields on a completed, expired, voided, or declined envelope. This envelope can no longer be edited.
• POST fill on those same statuses. The values stay where the last legal write left them.
• A sent envelope is locked for moving marks and for routing. Filling an existing field still works until someone has signed.
• The envelope id stays. A 409 here is not a new draft and not a second envelope.

Reading This envelope can no longer be edited is not a send. The original send already counted — or never happened, if the envelope expired as a leftover draft that later closed. Free allows 5 packets a month. A refused fill does not return HTTP 402 ENVELOPE_LIMIT. Field payload is invalid is a different 400. Provide at least one field value is an envelope that has marks but received an empty body. This envelope has no fields to fill is an envelope with zero marks. Those strings are other doors. Moving marks locks when you send. Filling an existing field still works until someone has signed. A completed, expired, voided, or declined envelope refuses fill as well.

What this is not

• Not Completed envelopes cannot be changed. That string is void, correct, or resend on a filed copy.
• Not Only sent envelopes can use this action. That string is envelope admin on a draft.
• Not This envelope is already voided. That string is a second void, not a field write.
• Not checkout. Billing is not open. Paying a listed price does not reopen marks on a closed id.

If the work still needs different marks, send a new envelope from the PDF or template. Do not hunt for a Settings toggle that “allows late fill.” Reminders go out by email today. Text-message (SMS) is coming soon. Email still soft-fails on that new send. Text-message (SMS) is coming soon. Drive archive waits for completed. Stripe off: Payments not live. None of those flags un-lock a closed envelope or hide This envelope can no longer be edited.

The click-path

1. Place marks before you send. After send, field moves are refused.
2. If fill or fields returns This envelope can no longer be edited, stop. Do not open Billing for a late edit.
3. Read the status. Sent already locks field moves and routing. Completed, expired, voided, and declined lock filling as well.
4. If you needed a new signature, send a new envelope. If send returns HTTP 402 ENVELOPE_LIMIT, that is the monthly cap, not the edit lock.
5. On a phone, Settings is a drawer row. Help is not a drawer row — it stays in the header. The 409 copy is the same.

The fill-then-send path is API fill then send. Create from a layout is create an envelope from a template via the API. Ask Inkpacket for why This envelope can no longer be edited is not a completed lock to open this article. Ask how the API works to open help. Ask mint api token to open Settings → tokens.

Ask and the lock

Ask Inkpacket for why This envelope can no longer be edited is not a completed lock to open this article. Ask how the API works to open help. Marketing Ask stays site Q&A and deep links. It will not replace marks, fill a closed id, or increment the monthly cap from this article. Field moves lock at send. Sent does not let you move a box.

Caps and what is not open yet

Reading This envelope can no longer be edited is not a send. The original send already counted if the envelope ever left draft. 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 reopen marks on a closed envelope or hide the edit-lock string. The FAQ and Public API use This envelope can no longer be edited in the same words.

Fill while it is a draft. Leave a closed id alone. Open a workspace on Free — see published pricing — and try a late fill on a throwaway completed envelope so edit-lock honesty is a named 409 you already read, not a checkout you opened to “unlock fields” this pass does not ship.