Every paged list answers `data`

Each collection names its rows after what they are: a forum answers topics, a blog articles, a status page monitors, documentation pages. That is clear for one endpoint and a guessing game for a client that reads them all — a publisher that read topics off a blog saw an empty list and re-created every post.

Added

data on every paged list. Every answer that carries page now also carries data: the same rows as the named key, under a key that is the same on every list. It matches the data every create already answers with, so data is the one key a generic client reads.

{ "articles": [ … ], "data": [ … ], "page": { "limit": 100, "hasMore": false, "nextCursor": null } }

topics on blog lists. A blog article is a topic underneath — the same object, the same fields — so blog lists also carry the rows as topics, and a client written against the forum reads the blog unchanged.

Both appear wherever page does: when you state Forumulate-Version (any version) or send a cursor. The named key is unchanged, so nothing you read today moves. Both are in the API reference's response schemas.