Get a content group
Retrieve one content group with its members. Read it before adding to it, so you don't draft a version that already exists.
apiKeyAuthorizationBearer <token>API key for authenticating protected endpoints. Pass as Bearer token in Authorization header.
bucketId*stringUnique identifier of the content group
Content group retrieved successfully
application/json- response
id*stringUnique identifier for this bucket
title*stringWhat the group is called, taken from the post that seeded it
createdAt*stringISO 8601 timestamp of creation
updatedAt*stringISO 8601 timestamp of the last change to the group
members*array<>The pieces in this group, in display order — the post it was seeded from first
curl -X GET "https://example.com/v1/buckets/string"{ "id": "string", "title": "string", "createdAt": "string", "updatedAt": "string", "members": [ { "kind": "post", "id": "string", "channel": "string", "title": "string", "status": "draft", "scheduled": true, "url": "string", "publishedAt": "string", "archivedAt": "string", "position": 0, "updatedAt": "string" } ]}List content groups GET
Retrieve the content groups in your publication, most recently active first. The publication is identified by the API key. A group ("bucket") is one identity for a post and everything made out of it — the post, the X thread drawn from it, the LinkedIn version, the newsletter. It's what the writer sees as a single stacked row under Content. Each group lists its members in display order, with the post it was seeded from first. Bodies aren't included; fetch the member with `GET /v1/content/{id}` or `GET /v1/posts/{id}` to read one.
Get a post's content group GET
Find the group a post belongs to, without creating one. Answers `null` when nothing has been made from the post yet. To attach something, call `POST /v1/posts/{postId}/bucket` instead, which creates the group on first use. A post you've reopened for editing resolves to the live post's group, so a draft id and its published id give the same answer.