Why an API token never crosses workspaces

Owners and admins mint org-scoped tokens at Settings → API tokens. Send them as Authorization: Bearer ip_… on /api/v1/packets and /api/v1/packets/:id*. Successful calls update lastUsedAt. Tokens never cross workspaces. A secret from org A is Invalid API token on org B, not Bearer token required. That is token-workspace honesty: one ip_… is one organization, the workspace switcher does not re-home a hash, and opening Billing will not “attach this secret to the other desk.”

The two 401 strings on one org are why Bearer token required is not Invalid API token. Health is a different door — why GET /api/v1/health needs no Bearer token. Who can mint is members cannot mint API tokens. Desk help is Docs. This guide is why a worker that stored one secret cannot list the other organization’s envelopes by switching the path.

Ask Inkpacket for why an API token never crosses workspaces to open this article. Ask how the API works to open help. Ask how to create an api token to open Settings #tokens. Those phrases stay on the product screens. This article is the public version of why last-used on org A does not move when you pointed the same header at org B, and why that 401 is not a missing word Bearer.

What org-scoped means

• Mint happens inside the current workspace. The list shows the prefix. The full token is shown once.
• Inkpacket stores only a SHA-256 hash (tokenHash). There is no reprint. Mint again if you lost it.
• A call on /api/v1/packets uses the organization that owns that hash. There is no orgId override in the header.
• Health stays public and workspace-agnostic. A 200 there is not permission to POST envelopes in either org.

Do not paste ip_… into an envelope title. Do not send the secret through a signing invite — that object is a PDF link, not a seat. Do not paste a signing token into Settings and call it a Bearer. A worker that creates envelopes stores the secret for one organization. A second workspace needs a second mint from that workspace’s owner or admin. Members cannot mint in either place. Tokens never cross workspaces: switching the desk above Menu does not rewrite tokenHash.

What this is not

• Not Bearer token required. That 401 is a missing or malformed Authorization header on this request.
• Not HTTP 429. Access-code 429 is a signer PIN lockout. 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.
• Not HTTP 402 ENVELOPE_LIMIT. That is the monthly send cap after a valid token is accepted in the right org.
• Not checkout. Billing is not open. Paying a listed price does not share a secret across workspaces.

Each API token allows 120 requests per minute per token. Over that limit, /api/v1 returns HTTP 429 with a Retry-After header. Inkpacket does not send X-RateLimit headers. The send guard is HTTP 402 ENVELOPE_LIMIT inside the org that owns the token. Idempotency-Key on create, fill, or send replays a stored body in that same org — it does not import an envelope from the other desk. Reminders go out by email today. Text-message (SMS) is coming soon. Email still soft-fails after a valid send. Text-message (SMS) is coming soon. Drive missing: Drive not configured. Stripe off: Payments not live.

The click-path

1. Confirm which workspace the worker should write to. Mint there as owner or admin.
2. If the body says Invalid API token after a workspace switch, mint in the new org. Do not reuse the old secret.
3. If the body says Bearer token required, add the header. Do not revoke the other org’s token.
4. Confirm last-used only moves on the org that accepted the call.
5. On a phone, tap Open desk menu for Settings. The workspace switcher above Menu will not re-scope a hash.

Ask Inkpacket for why an API token never crosses workspaces to open this article. Ask how to create an api token to open Settings. Marketing Ask stays site Q&A and deep links. It will not mint a Bearer token, switch a workspace, or POST an envelope from this article. Stay on the organization you minted in.

Caps and what is not open yet

Reading a 401 is not a send. Send 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 share a token across orgs or merge two desks. The FAQ and Public API use Tokens never cross workspaces in the same words.

Mint in the workspace you mean to send from. Stay there. Open a workspace on Free — see published pricing — and call envelopes with the other org’s secret on purpose so token-workspace honesty is a 401 you already read, not a revoke you opened Billing to undo.