Some posts are worth sending again: a how-to, a best-seller, a guide that still holds. Mark a published post evergreen and Reelspan puts a copy of it in the profile's queue every few weeks, up to the number of times you choose.
Each copy is a new post made from the original: the same text, files and network settings, sent through the normal publish path. It takes the profile's next free queue slot, shows up as an ordinary scheduled post you can edit or cancel, and counts against your monthly uploads like any post.
Make a post evergreen
curl -X PUT https://api.reelspan.com/v1/evergreen/6e3b9d1f7a2c4e8b0d5f3a1c9e7b2d4f \
-H "Authorization: Bearer $REELSPAN_API_KEY" \
-H "Content-Type: application/json" \
-d '{"every_weeks": 4, "max_times": 6, "platforms": ["linkedin", "x"]}'{
"success": true,
"evergreen": {
"request_id": "6e3b9d1f7a2c4e8b0d5f3a1c9e7b2d4f",
"platforms": ["linkedin", "x"],
"every_weeks": 4,
"max_times": 6,
"times_posted": 0,
"active": true,
"next_at": "2026-12-15T10:00:00.000Z",
"last_request_id": null,
"last_error": null
}
}request_id: the original post'srequest_id. At least one network must have published it.every_weeks: 1 to 52. The first copy goes into the queue that many weeks after the post went out (at once if that time has passed); each next one that many weeks after the copy before it.max_times: how many copies in all, 1 to 52. Then it stops.platforms: the networks for the copies. Leave it out for the networks the post went out on. Only networks of the original post can be named.- The post's files are kept in your media library so they're never deleted, and count against its space (413
LIBRARY_FULLwhen they don't fit). If the files were already deleted, the answer is 409MEDIA_EXPIRED: post it anew.
Sending PUT again changes the settings; copies already made still count towards max_times. A post that had stopped starts again.
When a copy can't be made
Reelspan checks every 15 minutes for copies that are due.
- The last copy hasn't gone out yet (still in the queue, or waiting for a client's approval): the next one waits for it.
- Over your monthly limit, or no free queue slot in the next 30 days: tried again a day later, with the reason in
last_error. - The files are gone (taken out of the library) or the copy is refused for another reason: it stops, with
active: falseand the reason inlast_error. Fix it and sendPUTagain.
Some networks refuse a post that is exactly the same as a recent one. Give the copies a few weeks, or change the text of the original's network settings with Edit a post first.
List and stop
GET /v1/evergreen lists the workspace's evergreen posts, the next copy first; profile_username limits it to one profile. Each item also has profile_username and the original's title. next_at is null once it is no longer active.
GET /v1/evergreen/{request_id} reads one post's settings. DELETE /v1/evergreen/{request_id} stops it; copies already in the queue stay until you cancel them.
curl -X DELETE https://api.reelspan.com/v1/evergreen/6e3b9d1f7a2c4e8b0d5f3a1c9e7b2d4f \
-H "Authorization: Bearer $REELSPAN_API_KEY"Keys and scopes
Reading needs the read scope; making a post evergreen or stopping it needs publish. A key limited to some profiles only sees their posts.
Errors
| Status | error_code |
When |
|---|---|---|
| 400 | INVALID_REQUEST |
every_weeks or max_times is out of range. |
| 400 | INVALID_PLATFORM |
A network the original post didn't go to. |
| 404 | NOT_FOUND |
No such post, or it isn't evergreen. |
| 409 | NOT_PUBLISHED |
No network has published the post yet. |
| 409 | MEDIA_EXPIRED |
The post's files are no longer kept. |
| 413 | LIBRARY_FULL |
The files don't fit in the media library. |