Post Scheduling

Confirm

Confirm is the publish step. It checks every account on the draft, then charges the schedule fee once and puts the post on the calendar.

Confirm a draft

The body can be empty. The group id is in the path. On success the response is the group as it now sits on the calendar.

POST/api/v1/scheduling/post-groups/{id}/confirmschedule:write

curl

curl -sS -X POST https://api.thealtermeai.com/api/v1/scheduling/post-groups/GROUP_ID/confirm \
  -H "Authorization: Bearer emk_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

422 NOT_READY means a target cannot go out yet. The body includes issues, one row per problem, with the account and a message such as an empty caption. The draft is unchanged and nothing is charged. Fix it with PATCH and confirm again.

402 INSUFFICIENT_WORK_FUNDS means the wallet cannot cover the fee. Top up Work Funds and confirm again. 404 means the group is not in this workspace.

Move a time

scheduledFor is required and must be an ISO 8601 timestamp. Add targetId to move one account and leave the others. This changes unpublished targets. It does not create a second charge.

POST/api/v1/scheduling/post-groups/{id}/rescheduleschedule:write

curl

curl -sS -X POST https://api.thealtermeai.com/api/v1/scheduling/post-groups/GROUP_ID/reschedule \
  -H "Authorization: Bearer emk_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"scheduledFor":"2026-05-13T15:00:00.000Z"}'

OpenAPI: /openapi/scheduling-v1.yaml