Members cannot mint API tokens

Owners and admins mint and revoke org-scoped tokens at Settings → API tokens. Members can send envelopes from the desk. Members cannot mint. Members cannot invite. That is member-token honesty: the Tokens card is a role door, not a Free-plan tease, and opening Billing will not print an ip_… secret for a member session. The desk still works. The public API waits on an owner or admin.

How to mint and revoke at all is mint and revoke API Bearer tokens. Create-then-fill-then-send is API fill then send. Keys on those POSTs are Idempotency-Key on create, fill, and send. Desk help is Docs. This guide is why a member does not see a working Create token control.

Ask Inkpacket for members cannot mint API tokens to open this article. Ask how to create an api token to open Settings #tokens. Ask how the API works to open help. Those phrases stay on the product screens. This article is the public version of why the secret is an owner or admin job.

What each role can do

• Owner and admin — mint at /desk/settings#tokens, revoke, send from the desk, invite seats.
• Member — send envelopes, use templates, run bulk send and Web Forms the plan allows. No token mint. No teammate invite.
• Signer — no desk. A signing link is not a seat.
• Platform Admin — a different row when showAdmin is on. Not a token mint for every member.

POST /api/orgs/tokens mints an ip_… secret. The full token is shown once. Inkpacket stores only a SHA-256 hash (tokenHash); the list shows the prefix. DELETE /api/orgs/tokens/:id revokes it. Tokens never cross workspaces. Successful envelope calls update last-used time. GET /api/v1/health is public and does not take a Bearer token — a member can hit health without a mint, and that does not mean they can POST /api/v1/packets as the workspace.

What this is not

• Starter lists more envelopes than Free — 20 versus 5. A token does not raise the cap.
• Not a seat-cap. Seat counts are planning numbers; invite does not refuse when a workspace is full. Invite is still owner or admin.
• Not a missing Settings page. On a phone, Settings is a drawer row. The Tokens card is still role-gated after you open it.
• Not checkout. Billing is not open. Paying a listed price does not mint a secret for a member.

A member who needs automation asks an owner or admin to mint, then stores the secret in the worker. 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. Workspace team invite versus signing invite is those two URLs. A teammate inviteUrl has no Bearer token on it either.

The click-path

1. If you are a member and you need an API send, ask an owner or admin. Do not open checkout.
2. Owner or admin: open Settings → API tokens. Create. Copy the secret once.
3. Call Authorization: Bearer ip_… on /api/v1/packets. Send still counts against the monthly cap.
4. Revoke from the same card when the worker is done. Last-used is a hint, not a second secret.
5. On a phone, tap Open desk menu for Settings. The workspace switcher above Menu will not mint a token.

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. Send volume over the monthly cap is HTTP 402 ENVELOPE_LIMIT, not 429. The send guard is HTTP 402 ENVELOPE_LIMIT. Access-code 429 is a signer PIN lockout, not this card — access-code 429 versus API rate limit. Reminders go out by email today. Text-message (SMS) is coming soon. Email still soft-fails after a member or an API send. Text-message (SMS) is coming soon. Drive missing: Drive not configured.

Ask and Team

Ask Inkpacket for members cannot mint API tokens to open this article. Ask how to invite a teammate to open Team help. Marketing Ask stays site Q&A and deep links. It will not mint a Bearer token or promote a member from this article. Promote on Team if this person should mint. That is a role change, not a plan change.

Caps and what is not open yet

Minting a token 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 mint a token for a member or hide Settings. The FAQ and Public API use Members cannot mint in the same words.

Send from the desk as a member. Ask an owner for ip_… when a worker needs it. Stay on that organization. Open a workspace on Free — see published pricing — and sign in as a member on purpose so member-token honesty is a Tokens card that stayed closed, not a secret you opened Billing to buy.