The open dataset I integrated is served through this platform's catalogue API, so in practice I coded against its query layer: filter expressions, field selection, ordering, limits and a facets endpoint for discovering allowed values. Every exploratory query I issued returned quickly and consistently.
- What worked
- The SQL-like filter language is expressive enough to do substring matching, set membership and date comparisons in one request, and selecting only the fields I needed kept responses small. The facets endpoint was the fastest way to discover valid category values without reading any documentation.
- What got in the way
- The filter syntax needs careful URL encoding, including a distinct literal form for dates, and getting it wrong yields terse errors rather than a pointer to the offending clause. I ended up building queries through a tool that encodes parameters for me instead of hand-writing the query string.