IpInkpacket

Blog

Why an access code cannot contain spaces

An Inkpacket access code must be 4–32 characters with no spaces. A space is rejected on the send form. That is pin-format honesty — not a lockout, not a missing invite.

When you send an envelope, you can set an optional access code. The signer must enter that code before they can view or sign the PDF. A code must be 4–32 characters with no spaces. The send form rejects invalid values with Access code must be 4–32 characters. or Access code cannot contain spaces. That is pin-format honesty: a phrase with a blank is not a PIN, Generate a code on the send form will not invent spaces, and opening Billing will not “allow a passphrase with blanks.”

Why the PIN is a second channel is why the access code is not in the invite. After five misses, access-code lockout recovery. The 429 fork is access-code 429 versus API rate limit. Desk help is Docs. This guide is why the send form stops a space before anyone is invited, and why that stop is not a lockout.

The FAQ and access codes on Features store only a hash. Ask Inkpacket for why an access code cannot contain spaces to open this article. Ask how access codes work to open help. Those phrases stay on the product screens. This article is the public version of Access code cannot contain spaces — the string the desk already uses when a blank sits in the PIN field.

What the format covers

  • 4–32 characters. Shorter or longer values return Access code must be 4–32 characters.
  • No spaces. A blank anywhere returns Access code cannot contain spaces.
  • Optional. Leave the field blank to send an open link. Blank on purpose is not an invalid code.
  • The same rules on a bulk send job and on a Web Form PIN. One format. Every recipient on that job shares the code.

Inkpacket stores only a hash, never the plaintext. Generate a code on the send form if you do not want to invent one — that helper still obeys 4–32 and no spaces. Share the code separately from the signing link. When invite email soft-fails, the desk says Signing link is ready. Invite email was not sent — copy the link and share it. When a code is set, it also says Copy the access code and share it separately from the link. Setting a valid PIN is not a send by itself. Sending the envelope counts. Free allows 5 packets a month. A rejected PIN string does not return HTTP 402 ENVELOPE_LIMIT.

What this is not

  • Not a lockout. Too many incorrect access codes. Try again in 15 minutes. is five wrong guesses after a valid PIN was set.
  • Not That access code is incorrect. N attempts remaining. The signer typed the wrong value. This guide is the sender’s form refusing a space.
  • Not the invite omitting the PIN. The code is never in the email even when the format is legal.
  • Not checkout. Billing is not open. Paying a listed price does not allow spaces in the PIN.

An empty unlock attempt returns Enter the access code the sender gave you. Opening a gated file without unlocking returns This envelope requires an access code. Those strings assume a legal PIN already exists. A space never created that PIN. Reminders go out by email today. Text-message (SMS) is coming soon. Email still soft-fails on the send, not on the format check. Text-message (SMS) is coming soon. Drive archive waits for completed. Stripe off: Payments not live. None of those flags let a blank sit in the code.

The click-path

  1. Open Documents → new #access-code, or set the optional code on Bulk send or Web Forms publish.
  2. Type 4–32 characters with no spaces, or generate a code. If the form names a space, remove the blank. Do not open Billing.
  3. Share the PIN out of band. Copy the signing link if invite email was not sent.
  4. If send returns HTTP 402 ENVELOPE_LIMIT, that is the monthly cap, not the PIN format.
  5. On a phone, Documents is a drawer row. The same two format strings appear. Help is not a drawer row — it stays in the header.

When a PIN belongs on a public slug is when to set a Web Form access code. When to require one at all is when to require an access code. Ask Inkpacket for why an access code cannot contain spaces to open this article. Ask how access codes work to open help. Ask set an access code to open the send form.

Ask and the PIN

Ask Inkpacket for why an access code cannot contain spaces to open this article. Ask how access codes work to open help. Marketing Ask stays site Q&A and deep links. It will not mint a PIN, strip a space, or send the envelope from this article. Four to thirty-two characters. No blanks. Share that value separately.

Caps and what is not open yet

Refusing a space is not a send. Send of an envelope that used a legal PIN 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 allow a space in the PIN or hide the format strings. The FAQ and More on access codes use Access code cannot contain spaces and Access code must be 4–32 characters in the same words.

Type a compact PIN. Share it separately. Open a workspace on Free — see published pricing — and paste a throwaway phrase with a blank so pin-format honesty is a send-form string you already read, not a lockout you waited fifteen minutes to clear.

Open a workspace on Free

Billing is published, not charging. Send an envelope from the desk without a card.

Open a workspace