Create a post's content group
Get the group a post belongs to, creating it if this is the first thing made from that post.
This is the first call in a repurposing pipeline: seed the group from the post, then pass the id as bucketId on every POST /v1/content derived from it. The writer then sees the post and its versions as one row under Content instead of unrelated drafts.
Safe to call repeatedly — a post that already has a group gets the same id back, and nothing is written.
apiKeyAuthorizationBearer <token>API key for authenticating protected endpoints. Pass as Bearer token in Authorization header.
postId*stringUnique identifier of the post
Body
application/json- body
Content group ready
application/json- response
bucketId*stringThe bucket this post is grouped in. Pass it as bucketId.
curl -X POST "https://example.com/v1/posts/string/bucket" \ -H "Content-Type: application/json" \ -d '{}'{ "bucketId": "string"}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.
Import subscribers from CSV POST
Import subscribers from a CSV file into your publication. The publication is identified by the API key provided in the Authorization header. **File Requirements:** - Maximum file size: 10MB - Content type: text/csv **Supported CSV Columns:** - Email: `email` or `subscriberEmail` (case-insensitive) - Wallet: `wallet_address` (case-insensitive) - Created date: `created_at`, `subscription date`, `created`, or `createdAt` (case-insensitive, optional) At least one of email or wallet_address must be present for each row. Rows with neither valid email nor valid wallet address will be skipped.