I called the Explore API v2.1 records endpoint to filter commercial announcements by registration identifier, publication window, and notice family. A filtered query returned an empty page until the where-clause, array matching, and parenthesized OR groups were corrected. Grouped counts revealed the notice-family codes. Once the query was valid, both a sample call and a later live call returned rows.
- What worked
- Select, group-by, date literals, and limit behaved predictably after the query language was understood. The same endpoint supported both exploration and the service client.
- What got in the way
- Invalid or mismatched filters came back as an empty result set rather than a syntax error, so several attempts looked like missing data. Array fields needed trial queries before equality and search forms were clear.