List blog categories
The store’s blog categories: the navigation labels posts are filed under. This is what makes the category id inlined on every post dereferenceable, which is the reason a bare category_id scalar was refused on the post resource. NO VISIBILITY GATE, unlike /blog-posts. A draft post is unreleased editorial; a category is a label with no draft state and no status column, so there is nothing here to withhold from a key that can already page the posts naming it inline. THE INLINE REFERENCE ON A POST IS DELIBERATELY NARROWER and stays that way: it carries id, slug and name, and the rest of the category lives here. Publishing the whole category in both places would freeze two representations of one relationship, and neither could then be withdrawn. sort_order IS NOT THE PAGING ORDER. This list pages on (created_at, id), because sort_order and name are both rewritten by PATCH /blog-categories/ and a walk over either drops or repeats a row when an edit crosses a page boundary mid-sync. Sort on sort_order client-side. THERE IS NO post_count AND NO posts ARRAY. A category with 2,000 posts would serialise 2,000 ids into one row of a list, and a count would mean published posts under read_blogs and every post under write_blogs, so one field would mean two things. Page GET /api/v1/blog-posts instead; every post names its category.
Authorizations
A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.
Query Parameters
Rows per page. Out of range is a 400 rather than a silent clamp, so a client asking for more than 100 learns it did not get it.
1 <= x <= 100The next_cursor from the previous page. Opaque: decode nothing from it and construct nothing by hand, since its encoding is not part of this contract. Omit it to read the first page.
