Improvement
API docs and export routes were tightened up together
The export and reference work now reads as one system instead of separate technical notes.
We cleaned up the API documentation and related export behavior so the public reference matches the way the site actually serves data.
That included clearer endpoint descriptions, better error handling language, and a more usable explanation of what developers can expect from collection-based routes.
The goal here was not to sound more technical; it was to make the platform easier to work with when someone needs the data behind the interface.