Why Provide at least one field value is not a published-form cap

POST /api/v1/packets/:id/fill writes values onto marks that already exist. An envelope with marks and a body that yields zero updates returns Provide at least one field value. Empty strings are skipped. An empty array is the same 400. That is empty-fill honesty: fill needs a value, an envelope with zero marks is a different 400, and opening Billing will not “grant a blank fill body.”

Why an envelope with zero marks names itself is why This envelope has no fields to fill is not a published-form cap. Why send of that empty draft is a different door is why Place at least one field before sending 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 an empty body 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 Provide at least one field value 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 Provide at least one field value — the string fill already uses next to an empty body.

What empty-fill covers

• POST fill with an empty values array on an envelope that has marks. Provide at least one field value.
• POST fill whose every value is blank after trim. The same 400. Empty strings do not count.
• POST fill on an envelope with zero marks. This envelope has no fields to fill. That is the no-marks door, not this empty body.
• A field id or label that is not on the envelope. Field X was not found on this envelope. That is a miss, not an empty body.

Reading Provide at least one field value is not a send. Filling is not a send. Free allows 5 packets a month. A refused empty-body fill does not return HTTP 402 ENVELOPE_LIMIT. Free includes 1 published Web Form. Starter grants extra published forms and more monthly envelopes than Free. An empty fill body 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 wrote nothing is this door.

What this is not

• 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 Field labeled X was not found on this envelope. That string is a miss on a named mark.
• Not checkout. Billing is not open. Paying a listed price does not invent a value for fill to write.

Send one fieldId or label with a non-empty value. Then fill again or send the envelope. 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 Provide at least one field value or count an empty fill 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 Provide at least one field value, put a non-empty value on a known id or label. Do not open Billing for a blank body.
3. If fill returns This envelope has no fields to fill, you still have zero marks. Place one. Then fill.
4. If send returns HTTP 402 ENVELOPE_LIMIT, that is the monthly cap, not the empty fill body.
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 Provide at least one field value 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 empty body

Ask Inkpacket for why Provide at least one field value 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 fill a blank body, place a mark, or increment the monthly cap from this article. Marks first. A non-empty value second. No-fields-fill is the other 400.

Caps and what is not open yet

Reading Provide at least one field value 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 fill value or hide the empty-fill string. The FAQ and Public API use Provide at least one field value in the same words.

Send a value. Then send the envelope. Open a workspace on Free — see published pricing — and POST fill with an empty body on a throwaway marked draft so empty-fill honesty is a named 400 you already read, not a checkout you opened for “blank fill body” this pass does not ship.