Why Signer name and email are required is not a unique-email 400
Inkpacket returns Signer name and email are required when send has no recipient row. That is missing-recipient honesty — not a repeated inbox, not checkout.
Send on a draft that already has marks still needs at least one recipient. An empty name-and-email list returns Signer name and email are required. The envelope stays a draft. No invite goes out. That is missing-recipient honesty: send waits for a person, a repeated inbox is a different 400, and opening Billing will not “invent a signer from an empty row.”
Why a repeated inbox on one envelope is a 400 is why Each recipient needs a unique email is not a bulk skip. Why the list stops at twenty is why an envelope stops at 20 recipients. 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 a missing recipient, 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 Signer name and email are required 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 Signer name and email are required — the string send already uses next to an empty recipient list.
What missing-recipient covers
- Desk send with no name and no email. Signer name and email are required.
- POST /api/v1/packets/:id/send with an empty recipients array and no top-level name or email. The same 400.
- A repeated inbox on a list that already has rows. Each recipient needs a unique email. That is the twin door, not this empty list.
- Bulk start with no mapped email column. Add at least one recipient with an email address. That string is the job, not this envelope send.
Reading Signer name and email are required is not a send. The draft never left DRAFT. Free allows 5 packets a month. A refused empty-recipient send does not return HTTP 402 ENVELOPE_LIMIT. Place at least one field before sending is a draft with zero marks — that check runs first. This envelope can no longer be sent is a closed status. X is already a recipient on this envelope is a second add of an inbox that already sits on the draft. Phone number must be a valid E.164 number is a bad phone on a row that already has a name and email. Those strings are other doors. Zero recipient rows is this door.
What this is not
- Not Each recipient needs a unique email. That string is a twin inbox on a list that already has people.
- Not Add at least one recipient with an email address. That string is bulk start, not this envelope send.
- Not Place at least one field before sending. That string is zero marks. This article already has a box.
- Not checkout. Billing is not open. Paying a listed price does not invent a signer from an empty row.
Add a name and a unique email. Then send. Sequential or parallel routing still needs that first row. Reminders go out by email today. Text-message (SMS) is coming soon. Email still soft-fails on a legal send, not on this 400. Text-message (SMS) is coming soon. Drive archive waits for completed. Stripe off: Payments not live. None of those flags hide Signer name and email are required or count an empty-recipient send toward the monthly cap.
The click-path
- Place at least one field. Add a signer name and email. Then send.
- If send returns Signer name and email are required, stop. Do not open Billing for an empty row.
- If send returns Each recipient needs a unique email, you already have people — two rows share an inbox. Change one.
- If send returns HTTP 402 ENVELOPE_LIMIT, that is the monthly cap, not the missing recipient.
- On a phone, Documents is a drawer row. The 400 copy is the same. Help is not a drawer row — it stays in the header.
Shared Order slots are when recipients share a sequential order. The waiting page is first-signer waiting message. Ask Inkpacket for why Signer name and email are required 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 empty row
Ask Inkpacket for why Signer name and email are required 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 invent a signer, send an empty row, or increment the monthly cap from this article. Name and email first. Unique is the other 400.
Caps and what is not open yet
Reading Signer name and email are required is not a send. Send of a draft that finally has a recipient 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 invent a signer or hide the missing-recipient string. The FAQ and More on signing order use Signer name and email are required in the same words.
Name the signer. Then send. Open a workspace on Free — see published pricing — and hit Send on a throwaway marked draft with no recipient so missing-recipient honesty is a named 400 you already read, not a checkout you opened to “skip the inbox” this pass does not ship.
Open a workspace on Free
Billing is published, not charging. Send an envelope from the desk without a card.
Open a workspace