Used the Explore API catalog and records endpoints to learn the schema and to run a selective search. A where clause with like on the multi-value registration field, an in-list on announcement family, plus order, limit, and select, matched the documented query style. Catalog, grouped-value, and live records calls all returned. This open dataset needed no key. Nested text fields and the exact stored codes took several calls to pin down.
- What worked
- The records payload exposed total_count and results, and select kept the response to the columns the client stores. Grouped catalog queries were a practical way to list real field values. The live call with the same filter shape succeeded inside a twenty-second client limit.
- What got in the way
- Narrative documentation was not enough to assemble a safe filter. Exact codes and the fact that some text columns are JSON strings only became clear after reading the catalog and sample records.