RedRover Logo

Content Tools

Confirm a Bulk Schedule

Schedules a previewed batch, all or nothing.

POST/content/batches/confirm
Scope: posts:writeAI Connector Tool: redrover_schedule_content_batch

Send the same items you previewed with their confirmToken, and an Idempotency-Key header holding any unique string. Retrying with the same key returns the first result instead of scheduling the batch twice.

Every check runs again before anything is written, so an item whose time is now less than 5 minutes away fails the confirm. If any item can't be scheduled, the ones already created are cancelled and their credits returned.

Headers

  • AuthorizationstringRequired

    Bearer followed by an rr_live_ API key or a connected app's access token. See Authentication.

  • X-Workspace-IdstringRequired

    The workspace to act on, from List Workspaces.

    UUID

Body

  • confirmTokenstringRequired

    The token from the preview of these exact items

    1 to 2000 characters

  • itemsobject or object[]Required

    Up to 50 posts and comments. Each is the body you'd send to Schedule a Post or Schedule a Comment, plus type: post or comment

    1 to 50 items

Response

201 Every scheduled item, in the order sent.

  • dataobjectRequired
    Show 2 Child Fields
    • scheduledobject[]Required

      The scheduled items, in the order sent

      Show 15 Child Fields
      • idstringRequired

        Content ID. Content waiting for your approval has a UUID; scheduled content has a number

      • typestringRequired

        post or comment

        one of post, comment

      • statusstringRequired

        Where it stands

        one of draft, pending_approval, approved, scheduled, posted, failed, cancelled

      • titlestringRequired

        Post title. Null for comments

        nullable

      • bodystringRequired

        The text

        nullable

      • subredditstringRequired

        Subreddit, without r/

        nullable

      • flairstringRequired

        Post flair. Posts only

        nullable

      • threadUrlstringRequired

        Comments only: the thread the comment replies in

        nullable

      • scheduledForstringRequired

        When it is due to go live

        nullable

      • postedAtstringRequired

        When it went live

        nullable

      • urlstringRequired

        The live link once posted

        nullable

      • upvotesnumberRequired

        Upvotes once posted

        nullable

      • commentCountnumberRequired

        Replies once posted

        nullable

      • failureReasonstringRequired

        Why it failed or was removed, when it did

        nullable

      • canChangebooleanRequired

        Whether you can still edit, reschedule or cancel it

    • totalCreditsintegerRequired

      Credits the batch took

Errors

Every error uses the error envelope.

  • 400The Idempotency-Key header is missing, the token is invalid or expired, the items differ from the preview, or an item no longer passes its checks
  • 402The workspace no longer has enough credits
  • 409The same Idempotency-Key is being used for a different batch, or this batch is still being scheduled
  • 401The Authorization header is missing, or the key is invalid or revoked
  • 403The key lacks the endpoint's scope, or cannot reach the workspace
  • 429More than 120 requests in a minute. Wait for Retry-After seconds
  • 500Something went wrong on our side
curl -X POST "https://app.tryredrover.com/api/public/v1/content/batches/confirm" \
  -H "Authorization: Bearer $REDROVER_API_KEY" \
  -H "X-Workspace-Id: $REDROVER_WORKSPACE_ID" \
  -H "Content-Type: application/json" \
  -d '{
  "confirmToken": "eyJ2IjoxLCJoIjoiNGYyYSIsImV4cCI6MTc2NDYwMTIwMDAwMH0",
  "items": [
    {
      "type": "post",
      "title": "What we learned shipping a weekly changelog for a year",
      "body": "We started writing a public changelog every Friday. Here is what changed for us...",
      "subreddit": "startups",
      "scheduledFor": "2026-12-01T15:00:00Z"
    },
    {
      "type": "comment",
      "threadUrl": "https://www.reddit.com/r/startups/comments/1abcde2/how_do_you_plan_content/",
      "body": "We batch ours on Thursdays and ship Friday morning. Keeps it honest.",
      "scheduledFor": "2026-12-01T15:00:00Z"
    }
  ]
}'
201 Response
{
  "data": {
    "scheduled": [
      {
        "id": "48213",
        "type": "post",
        "status": "scheduled",
        "title": "What we learned shipping a weekly changelog for a year",
        "body": "We started writing a public changelog every Friday. Here is what changed for us...",
        "subreddit": "startups",
        "flair": "Lessons Learned",
        "threadUrl": null,
        "scheduledFor": "2026-12-01T15:00:00Z",
        "postedAt": null,
        "url": null,
        "upvotes": null,
        "commentCount": null,
        "failureReason": null,
        "canChange": true
      },
      {
        "id": "91574",
        "type": "comment",
        "status": "scheduled",
        "title": null,
        "body": "We batch ours on Thursdays and ship Friday morning. Keeps it honest.",
        "subreddit": "startups",
        "flair": null,
        "threadUrl": "https://www.reddit.com/r/startups/comments/1abcde2/how_do_you_plan_content/",
        "scheduledFor": "2026-12-01T15:00:00Z",
        "postedAt": null,
        "url": null,
        "upvotes": null,
        "commentCount": null,
        "failureReason": null,
        "canChange": true
      }
    ],
    "totalCredits": 40
  }
}