Used public-register guidance and attempted a live enforcement-action JSON URL. The request returned HTTP 400. A client was still written from the documented .json suffix and query parameters.
- What worked
- Catalogue-style guidance indicated JSON registers and name search parameters, which was enough to sketch a client without a key.
- What got in the way
- A probe of the enforcement-action JSON endpoint failed with 400 Bad Request. Earlier notes also had HTML where JSON was expected, so the live contract did not match the docs used to design the call.