Why Field X was not found on this envelope is not a published-form cap

POST /api/v1/packets/:id/fill writes values onto marks that already exist. A fieldId or label that is not on that envelope returns Field X was not found on this envelope — or Field labeled X was not found on this envelope when you sent a label. The envelope keeps its marks. Nothing is written. That is miss-fill honesty: fill named the wrong mark, an empty body is a different 400, and opening Billing will not “invent a field from a miss.”

Why an empty fill body names itself is why Provide at least one field value is not a published-form cap. Why an envelope with zero marks names itself is why This envelope has no fields to fill is not a published-form cap. The intended create → fill → send loop is API fill then send. Desk help is Docs. This guide is why fill names a miss on an envelope that already has marks, and why that name is not a published-form 402.

The FAQ and API on Features keep fill on existing fields. Ask Inkpacket for why Field X was not found on this envelope is not a published-form cap to open this article. Ask how the API works to open help. Those phrases stay on the product screens. This article is the public version of Field X was not found on this envelope — the string fill already uses next to a miss.

What miss-fill covers

• POST fill with a fieldId that is not on the envelope. Field X was not found on this envelope.
• POST fill with a label that is not on the envelope. Field labeled X was not found on this envelope.
• POST fill with an empty values array on an envelope that has marks. Provide at least one field value. That is the empty-body door.
• POST fill on an envelope with zero marks. This envelope has no fields to fill. That is the no-marks door.

Reading Field X was not found on this envelope is not a send. Filling is not a send. Free allows 5 packets a month. A refused miss does not return HTTP 402 ENVELOPE_LIMIT. Free includes 1 published Web Form. Starter grants extra published forms and more monthly envelopes than Free. A miss does not burn a published-form slot. Field payload is invalid is PUT fields with a bad layout. This envelope can no longer be edited is a closed status. Those strings are other doors. Marks exist and the body named the wrong one is this door.

What this is not

• Not Provide at least one field value. That string is an empty body. This article named a mark that is not here.
• Not This envelope has no fields to fill. That string is zero marks. This article already has a box.
• Not Place at least one field before sending. That string is send of a blank draft.
• Not checkout. Billing is not open. Paying a listed price does not invent a field from a miss.

GET the envelope. Use a fieldId or label that is actually on it. Then fill again or send. A Web Form fill that misses a form mark says Field X was not found on this form — same miss, form words. Reminders go out by email today. Text-message (SMS) is coming soon. Email still soft-fails on the later 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 Field X was not found on this envelope or count a miss toward the monthly cap.

The click-path

1. Create a draft that already has marks — from a template, or PUT fields on a one-off upload.
2. If fill returns Field X was not found on this envelope, GET the envelope and copy a real id or label. Do not open Billing for a miss.
3. If fill returns Provide at least one field value, the body wrote nothing. Put a non-empty value on a known mark.
4. If send returns HTTP 402 ENVELOPE_LIMIT, that is the monthly cap, not the miss.
5. On a phone, Settings is a drawer row. API tokens live there. Help is not a drawer row — it stays in the header.

Idempotency on fill is Idempotency-Key on create, fill, and send. Why a closed envelope shuts fill is why This envelope can no longer be edited is not a completed lock. Ask Inkpacket for why Field X was not found on this envelope is not a published-form cap to open this article. Ask how the API works to open help. Ask mint api token to open Settings → tokens.

Ask and the miss

Ask Inkpacket for why Field X was not found on this envelope is not a published-form cap to open this article. Ask how the API works to open help. Marketing Ask stays site Q&A and deep links. It will not invent a field, fill a miss, or increment the monthly cap from this article. GET the envelope. Name a mark that is there. Empty-fill is the other 400.

Caps and what is not open yet

Reading Field X was not found on this envelope is not a send. Send of a draft that already has marks and 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 field or hide the miss-fill string. The FAQ and Public API use Field X was not found on this envelope in the same words.

Name a real mark. Then fill. Open a workspace on Free — see published pricing — and POST fill with a made-up fieldId on a throwaway marked draft so miss-fill honesty is a named 400 you already read, not a checkout you opened for “invent a field” this pass does not ship.