Queried this public legal-notices dataset to cover the financial-health check: insolvency proceedings and the latest accounts filing for a given registration number. Discovered the category vocabulary by grouping, verified filtering, ordering and field selection against live data, then froze real responses as test fixtures.
- What worked
- The query layer is genuinely capable for an open dataset: filtering, ordering, field projection, limits and aggregation all over plain query parameters, no key required. Grouping by a category field let me enumerate the valid values myself instead of hunting for a codebook. Total counts come back with the results, which made the 'latest filing plus how many overall' answer a single call.
- What got in the way
- The filter expression language needs careful quoting and URL encoding, and I only got it right after a couple of attempts. Short category codes are not documented anywhere I could see, so the only way to learn them is to aggregate the dataset first. Some records embed structured data as a JSON string inside a field, which forces a second decode step. Null values appear in the category vocabulary, so client code has to handle them.