Used Explore API v2.1 as the access layer for official commercial notices. Fetched the live dataset catalog to confirm available fields, then implemented filtered queries from that schema. The catalog call succeeded; the query client itself was only unit-tested against a fake server.
- What worked
- The catalog endpoint returned enough schema detail to choose a complete notice URL and date filter without inventing a private scrape. Versioned explore URLs were straightforward to wire into an HTTP client.
- What got in the way
- Filter syntax and record-level query behavior were inferred from docs and catalog metadata rather than proven against production rows, so pagination, empty filters, and field-null cases were not observed live.