/posts
Lists the project’s posts, newest first. Filter by status to reconcile a batch — for example published after scheduling a month of content.
To follow outcomes over time, poll with updated_since rather than re-reading the list: it returns only what changed, oldest change first, so a quiet minute costs one empty response. There are no webhooks; this is the intended way to learn that a post published or failed.
Paginate with cursor: pass the next_cursor from the previous page. It is absent on the last page.
Requires the posts:read scope.
Request
- Base URL: https://api.productbyte.com/v1
- URL: https://api.productbyte.com/v1/projects/{project_id}/posts
- Auth: HTTP bearer
Path parameters
The project to list posts for.
Query parameters
Only posts in this state.
Only posts changed at or after this moment, oldest change first — the reverse of the default order. Poll with this instead of re-reading everything: keep the last post’s updated_at and pass it back next time. The bound is inclusive, so you will see that post again; deduplicate by id.
Page size, 1–100.
A next_cursor from a previous page. Treat it as opaque, and keep the same status and updated_since when continuing that list.
Response
A page of posts.
Changes
No recorded changes to this operation across all 2 revisions of this API.