BlogTag
Access codes
Lock a signing link with a PIN you share separately. Inkpacket stores only a hash.
Related product pages
Guides
Access codes for sensitive envelopes
How Inkpacket access codes lock a signing link: optional PIN on send or bulk send, hash at rest, lockout after wrong guesses, and why you share the code on a second channel.
When to require an access code
Decide whether an Inkpacket signing link needs a PIN: require one when a forwarded URL would be a leak, share it on a second channel, and know the five-try, 15-minute lockout.
Access-code lockout recovery
After five incorrect Inkpacket access-code tries the page locks for 15 minutes and returns HTTP 429. Wait it out. There is no desk unlock. That 429 is a PIN lockout, not an API send cap.
When to set a Web Form access code
Set an optional PIN when you publish an Inkpacket Web Form if a public /form/SLUG would be a leak. Later fills inherit that code. Share it separately. That is web-form-pin honesty — not an envelope access code on send.
Access-code 429 versus API rate limit
Too many incorrect access codes returns HTTP 429 and Try again in 15 minutes. Send volume over the monthly cap is HTTP 402 ENVELOPE_LIMIT, not 429. A token over 120 requests per minute per token returns HTTP 429. That is pin-429 honesty — a PIN lockout, not a traffic throttle.
Why the access code is not in the invite
An Inkpacket access code is a second secret. It is not in the invite email and not in the SMS. Share it separately. That is pin-channel honesty — not a missing PIN, not a mail bug.
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.