Official Form 101 — programmatic fill compatibility

Verdict at a glance

File facts

• Source: https://www.uscourts.gov/sites/default/files/form_b_101_0624_fillable_clean.pdf (issuer page: here)
• Blank tested: uscourts-101.pdf · 703 KB · sha256 23c1eaec370df54c59f996a3517bc4d5c010dd039af981b45ef11e58d1373651
• License: US federal government work — public domain (17 U.S.C. § 105). The hash-verified blank is redistributed here unmodified.
• Structure: 9 pages · AcroForm
• Fields: 159 (127 text, 27 checkbox, 4 button, 1 dropdown)

Quirks & limitations

• Plain AcroForm, no XFA, not encrypted — the same clean shape as this registry's other uscourts.gov entry (ao-440), reinforcing 'courts = clean AcroForm' as an actual class pattern rather than a single data point. 159 fields: 127 text, 27 checkbox, 4 pushbutton, 1 dropdown.
• The under-covered quirk this entry was fetched for: every visually mutually-exclusive Yes/No question on the form (dozens of them — 'Are you filing under Chapter 7/11/12/13', debtor questions throughout the petition) and even the chapter-selection checkboxes are built as fully independent CheckBox fields with Ff=0 (verified field-by-field via pypdf's raw /Ff flag — none of the 27 has the radio bit set, none is grouped under a shared parent). Nothing in the AcroForm stops a filler from checking both 'Chapter 7' and 'Chapter 13', or both 'Yes' and 'No' on the same question. This registry's uscis-i-9/opm-of-306/ca-edd-de1 entries show real RadioGroup fields elsewhere in government forms, so this isn't universal — it's a per-form authoring choice, and this form chose the unsafe one.
• Field names are generic and non-semantic — 'Check Box1' through 'Check Box26', plus three inserted-later variants suffixed 'A' ('Check Box16A', 'Check Box17A', 'Check Box20A', breaking the numeric sequence, likely a later revision that added items without renumbering). None of the 27 names hint at which question they answer; mapping them to meaning requires visually cross-referencing rendered field positions against the printed form, not just reading the AcroForm field tree.
• The single Dropdown ('Bankruptcy District Information', 95 options — every federal judicial district) is the identical component this registry's uscourts-ao-440 entry documents under the name 'Dist.Info' — same 95-entry option list, same first blank option, evidently a shared component reused across US Courts forms rather than authored per-form.
• Fetched cleanly with a plain `curl` and a browser User-Agent — no 403, no CDP workaround needed, consistent with this registry's other uscourts.gov entry.

Tested request

This exact shape ran against the live API during the recorded test (values here shortened to two fields; the test filled all 155 supported fields). With flatten=true, two identical runs produced byte-identical output — sha256 0575c552f0c0a0b30ce477223adb9e6e74bce7c55fa81345a78b17e20d4bebcb.

curl -X POST https://pdfops.dev/api/fill-form \
  -F "pdf=@uscourts-101.pdf" \
  -F 'fields={"Debtor1.SSNum":"PDFo","Debtor1.Employer Identification Number1":"PDFops"}' \
  -F "flatten=true" \
  -o filled.pdf

Enumerate all 159 field names first with the inspector or POST /api/inspect.

Field schema

Frequently asked

← All forms in the registry · Inspect your own PDF · Make a flat PDF fillable