Why X is already a recipient on this envelope is not a unique-email 400

Send on a draft that already has a signer can add more people. A second add of an inbox that already sits on that envelope returns that address is already a recipient on this envelope. The envelope stays a draft if it was still a draft. No second invite goes out for that inbox. That is already-on-packet honesty: the row already exists, a twin inbox on one new list is a different 400, and opening Billing will not “stack a second signer on the same inbox.”

Why a repeated inbox on one new send list is a 400 is why Each recipient needs a unique email is not a bulk skip. Why an empty recipient list is a different 400 is why Signer name and email are required is not a unique-email 400. How one envelope names several people is how to send one envelope to multiple signers. Desk help is Docs. This guide is why send names an inbox that already sits on the envelope, and why that name is not the unique-email door.

The FAQ and signing link on Features start from a named signer. Ask Inkpacket for why X is already a recipient on this envelope is not a unique-email 400 to open this article. Ask how routing works to open help. Those phrases stay on the product screens. This article is the public version of X is already a recipient on this envelope — the string send already uses next to a second add of a stored inbox.

What already-on-packet covers

• Desk send that adds a person who is already on the draft. that@inbox is already a recipient on this envelope.
• POST /api/v1/packets/:id/send that names an email already stored on that envelope. The same 409.
• A twin inbox on one new recipient list. Each recipient needs a unique email. That is the same-payload door, not this stored row.
• Bulk start that repeats an email in the CSV. Duplicate emails in the list are sent once. That skip is the job, not this envelope send.

Reading X is already a recipient on this envelope is not a send of a new envelope. The first add already created that signer row. Free allows 5 packets a month. A refused second add does not return HTTP 402 ENVELOPE_LIMIT. Signer name and email are required is an empty list. Each recipient needs a unique email is two rows on the same payload. Phone number must be a valid E.164 number is a bad phone on a new row. Those strings are other doors. An inbox that already sits on this envelope is this door.

What this is not

• Not Each recipient needs a unique email. That string is a twin inbox on one new list. This article is a stored row.
• Not Signer name and email are required. That string is zero recipient rows.
• Not a bulk skip. Bulk send sends a duplicate CSV email once. This article is one envelope that already has that inbox.
• Not checkout. Billing is not open. Paying a listed price does not stack a second signer on the same inbox.

Leave the stored signer. Add a different unique email if you need another person. Correct that stored row if the name or phone is wrong after send. Reminders go out by email today. Text-message (SMS) is coming soon. Email still soft-fails on a legal send, not on this 409. Text-message (SMS) is coming soon. Drive archive waits for completed. Stripe off: Payments not live. None of those flags hide X is already a recipient on this envelope or count a refused second add toward the monthly cap.

The click-path

1. Place at least one field. Add a unique email that is not already on the envelope. Then send.
2. If send returns that address is already a recipient on this envelope, stop. Do not open Billing to stack the same inbox.
3. If send returns Each recipient needs a unique email, you named the same inbox twice on this payload. Change one row.
4. If send returns HTTP 402 ENVELOPE_LIMIT, that is the monthly cap, not the stored recipient.
5. On a phone, Documents is a drawer row. The 409 copy is the same. Help is not a drawer row — it stays in the header.

The list cap is why an envelope stops at 20 recipients. Why bulk treats a repeated CSV email as one envelope is why a duplicate bulk email is one envelope. Ask Inkpacket for why X is already a recipient on this envelope is not a unique-email 400 to open this article. Ask how routing works to open help. Ask send an envelope to open Documents → new.

Ask and the stored inbox

Ask Inkpacket for why X is already a recipient on this envelope is not a unique-email 400 to open this article. Ask how routing works to open help. Marketing Ask stays site Q&A and deep links. It will not stack a second signer, send a stored inbox again, or increment the monthly cap from this article. One inbox, one row. Unique-email is the other 400.

Caps and what is not open yet

Reading X is already a recipient on this envelope is not a send of a new envelope. Send of a draft that adds a new unique inbox 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 stack a second signer or hide the already-on-packet string. The FAQ and More on signing order use already a recipient on this envelope in the same words.

Add a different email. Leave the stored row. Open a workspace on Free — see published pricing — and hit Send with an inbox that already sits on a throwaway draft so already-on-packet honesty is a named 409 you already read, not a checkout you opened to “stack the same inbox” this pass does not ship.