API reference

Scheduled posts

10 endpoints in this group.

Lists scheduled posts

GET/api/v1/scheduled-posts

Most recently created first. from and to apply to the scheduled time (to is exclusive). The member role sees only the posts of bots it can access. Scope: communities:read.

Scope
communities:read
SDK method
listScheduledPosts · list_scheduled_posts
MCP tool
listScheduledPostsread-only

Paginated

Parameters

NameTypeRequiredDescription
community_idqueryuuidnoThis community only
statusqueryenumnoThis status onlypending_approval | rejected | scheduled | sending | sent | failed | uncertain | canceled
fromquerydate-timenoFrom this moment
toquerydate-timenoBefore this moment
limitqueryintegernoPage size (1–200, default 50); 400 if it isn't an integerval 1–200, default 50
cursorquerystringnonext_cursor from the previous response (opaque)

Example request

curl -X GET "https://hiboty.com/api/v1/scheduled-posts?limit=50" \
  -H "Authorization: Bearer $HIBOTY_API_KEY"

Example response (200)

JSON
{
  "data": [
    {
      "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "community_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "batch_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "topic_id": 1,
      "text": "string",
      "image_url": "https://example.com/a.png",
      "button_text": "string",
      "button_url": "https://example.com/a.png",
      "silent": true,
      "pin": true,
      "repeat": "none",
      "status": "pending_approval",
      "scheduled_at": "2026-11-06T09:00:00.000Z",
      "retry_at": "2026-11-06T09:00:00.000Z",
      "attempts": 1,
      "message_id": "string",
      "simulated": true,
      "error": "string",
      "reject_reason": "string",
      "created_by": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "reviewed_at": "2026-11-06T09:00:00.000Z",
      "sent_at": "2026-11-06T09:00:00.000Z",
      "clicks": 1,
      "created_at": "2026-11-06T09:00:00.000Z",
      "updated_at": "2026-11-06T09:00:00.000Z"
    }
  ],
  "next_cursor": "string"
}

Possible errors

  • 400Invalid request: a missing or wrong field, or an unknown field name (validation_error).
  • 401The API key is missing, invalid or revoked (unauthorized).
  • 403Missing scope (scope), the plan doesn't allow it (plan_limit), the role isn't enough (forbidden_role), the email isn't verified (email_not_verified) or the organization is suspended.
  • 429A key, user or organization request limit (X-RateLimit-Scope) or the monthly message quota was exceeded; follow the Retry-After header.

Schedules a post or publishes it now

POST/api/v1/scheduled-posts

community_ids takes one target or up to 20; several targets are saved in one transaction (if one is invalid, none is created). Needs scheduled_at or publish_now. A post from the member role goes to admin approval (pending_approval) and isn't published even with publish_now. A content policy block returns 422 content_policy; flagged phrases and missing channel permissions are returned in warnings. A channel error during immediate publishing doesn't undo the record: the outcome is in the status and error fields of posts. In test mode the post doesn't go to Telegram and simulated is true. Use Idempotency-Key to avoid duplicates on retries. With a whatsapp block, a WhatsApp campaign draft is opened from the same content: it only uses an approved MARKETING template, only goes to opted-in people, and is sent after an admin approves it; it needs the write scope. If the WhatsApp part is invalid nothing is created (404 template_not_found, 400 template_not_allowed or template_params, 409 empty_audience or channel_not_configured, 502 channel_error). Scope: communities:write.

Scope
communities:write
SDK method
createScheduledPost · create_scheduled_post
MCP tool
createScheduledPostexternal effect

Supports Idempotency-Key

Parameters

NameTypeRequiredDescription
Idempotency-KeyheaderstringnoOptional, 1-255 visible ASCII characters. Within 24 hours the same key and body return the first response unchanged; a different body returns 409 idempotency_conflict.len 1–255

Body fields

NameTypeRequiredDescription
community_idsuuid[]yesitems 1–20
textstringyesUp to 1024 characters on a post with an imagelen 1–4096
publish_nowbooleanno
topic_idsobjectnoTarget topic in a forum group: community ID → topic ID
image_urlstring | nullnoPublic https addresslen ≤ 1000
button_textstring | nullnolen ≤ 64
button_urlstring | nullnohttps address; used with button_textlen ≤ 1000
silentbooleanno
pinbooleanno
repeatenumnonone | daily | weekly
scheduled_atdate-timenoISO 8601 instant with a time zone offset
whatsappobjectno
whatsapp.bot_iduuidyesWhatsApp bot
whatsapp.template_namestringyesA template approved by Meta, in the MARKETING category, without a media headerlen 1–512
whatsapp.template_languagestringyeslen 2–15
whatsapp.template_paramsstring[]noHeader and body variables in order; line breaks become a single spaceitems ≤ 20
whatsapp.topicstringnoOptional campaign topic; people who turned the topic off aren't in the audiencelen ≤ 40

Example request

curl -X POST "https://hiboty.com/api/v1/scheduled-posts" \
  -H "Authorization: Bearer $HIBOTY_API_KEY" \
  -H "Idempotency-Key: order-10482" \
  -H "Content-Type: application/json" \
  -d '{"community_ids":["3fa85f64-5717-4562-b3fc-2c963f66afa6"],"text":"Our new campaign has started!","button_text":"View","button_url":"https://ornek.com/kampanya","repeat":"none","scheduled_at":"2030-01-15T10:00:00+03:00"}'

Example response (201)

JSON
{
  "data": {
    "batch_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "posts": [
      {
        "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "community_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "batch_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "topic_id": 1,
        "text": "string",
        "image_url": "https://example.com/a.png",
        "button_text": "string",
        "button_url": "https://example.com/a.png",
        "silent": true,
        "pin": true,
        "repeat": "none",
        "status": "pending_approval",
        "scheduled_at": "2026-11-06T09:00:00.000Z",
        "retry_at": "2026-11-06T09:00:00.000Z",
        "attempts": 1,
        "message_id": "string",
        "simulated": true,
        "error": "string",
        "reject_reason": "string",
        "created_by": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "reviewed_at": "2026-11-06T09:00:00.000Z",
        "sent_at": "2026-11-06T09:00:00.000Z",
        "clicks": 1,
        "created_at": "2026-11-06T09:00:00.000Z",
        "updated_at": "2026-11-06T09:00:00.000Z"
      }
    ],
    "warnings": [
      {
        "code": "ornek",
        "message": "string"
      }
    ],
    "whatsapp_campaign": {
      "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "status": "string",
      "audience_count": 1
    }
  }
}

Possible errors

  • 400Invalid request: a missing or wrong field, or an unknown field name (validation_error).template_not_allowed
  • 401The API key is missing, invalid or revoked (unauthorized).
  • 403Missing scope (scope), the plan doesn't allow it (plan_limit), the role isn't enough (forbidden_role), the email isn't verified (email_not_verified) or the organization is suspended.
  • 404The record doesn't exist or this key can't access it (not_found).template_not_found
  • 409The action isn't possible in this state; the code gives the reason.empty_audience
  • 422Blocked by the content policy (content_policy).content_policy
  • 429A key, user or organization request limit (X-RateLimit-Scope) or the monthly message quota was exceeded; follow the Retry-After header.
  • 502A channel or external service failed (channel_error).channel_error

Returns a month's calendar with its posts

GET/api/v1/scheduled-posts/calendar

The same range as the dashboard calendar: weeks starting on Monday, in the organization's time zone. Each day comes with its posts; a multi-target round is one item. Defaults to the current month. Scope: communities:read.

Scope
communities:read
SDK method
getPostCalendar · get_post_calendar
MCP tool
getPostCalendarread-only

Parameters

NameTypeRequiredDescription
monthquerystringnoYYYY-MM

Example request

curl -X GET "https://hiboty.com/api/v1/scheduled-posts/calendar" \
  -H "Authorization: Bearer $HIBOTY_API_KEY"

Example response (200)

JSON
{
  "data": {
    "month": "string",
    "timezone": "Europe/Istanbul",
    "days": [
      {
        "date": "string",
        "in_month": true,
        "posts": [
          {
            "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
            "batch_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
            "status": "pending_approval",
            "scheduled_at": "2026-11-06T09:00:00.000Z",
            "repeat": "none",
            "text": "string",
            "targets": []
          }
        ]
      }
    ]
  }
}

Possible errors

  • 400Invalid request: a missing or wrong field, or an unknown field name (validation_error).
  • 401The API key is missing, invalid or revoked (unauthorized).
  • 403Missing scope (scope), the plan doesn't allow it (plan_limit), the role isn't enough (forbidden_role), the email isn't verified (email_not_verified) or the organization is suspended.
  • 429A key, user or organization request limit (X-RateLimit-Scope) or the monthly message quota was exceeded; follow the Retry-After header.

Scheduled post details

GET/api/v1/scheduled-posts/{id}

For a multi-target post, the round's targets and overall status are included. Scope: communities:read.

Scope
communities:read
SDK method
getScheduledPost · get_scheduled_post
MCP tool
getScheduledPostread-only

Parameters

NameTypeRequiredDescription
idpathuuidyesID

Example request

curl -X GET "https://hiboty.com/api/v1/scheduled-posts/3fa85f64-5717-4562-b3fc-2c963f66afa6" \
  -H "Authorization: Bearer $HIBOTY_API_KEY"

Example response (200)

JSON
{
  "data": {
    "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "community_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "batch_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "topic_id": 1,
    "text": "string",
    "image_url": "https://example.com/a.png",
    "button_text": "string",
    "button_url": "https://example.com/a.png",
    "silent": true,
    "pin": true,
    "repeat": "none",
    "status": "pending_approval",
    "scheduled_at": "2026-11-06T09:00:00.000Z",
    "retry_at": "2026-11-06T09:00:00.000Z",
    "attempts": 1,
    "message_id": "string",
    "simulated": true,
    "error": "string",
    "reject_reason": "string",
    "created_by": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "reviewed_at": "2026-11-06T09:00:00.000Z",
    "sent_at": "2026-11-06T09:00:00.000Z",
    "clicks": 1,
    "created_at": "2026-11-06T09:00:00.000Z",
    "updated_at": "2026-11-06T09:00:00.000Z",
    "batch_status": "pending_approval",
    "targets": [
      {
        "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "community_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "status": "pending_approval"
      }
    ]
  }
}

Possible errors

  • 400Invalid request: a missing or wrong field, or an unknown field name (validation_error).
  • 401The API key is missing, invalid or revoked (unauthorized).
  • 403Missing scope (scope), the plan doesn't allow it (plan_limit), the role isn't enough (forbidden_role), the email isn't verified (email_not_verified) or the organization is suspended.
  • 404The record doesn't exist or this key can't access it (not_found).
  • 429A key, user or organization request limit (X-RateLimit-Scope) or the monthly message quota was exceeded; follow the Retry-After header.

Edits a scheduled post

PATCH/api/v1/scheduled-posts/{id}

Only posts in scheduled or pending_approval can be edited; once sending has started it returns 409 post_locked. Admins can edit any post, members only their own pending one; the status doesn't change, so a member's post stays pending. On a multi-target post all targets of the round change together. Validation and content policy are the same as on creation (422 content_policy). Scope: communities:write.

Scope
communities:write
SDK method
updateScheduledPost · update_scheduled_post
MCP tool
updateScheduledPost

Parameters

NameTypeRequiredDescription
idpathuuidyesID

Body fields

NameTypeRequiredDescription
textstringnolen 1–4096
topic_idsobjectnoTarget topic in a forum group: community ID → topic ID
image_urlstring | nullnoPublic https addresslen ≤ 1000
button_textstring | nullnolen ≤ 64
button_urlstring | nullnohttps address; used with button_textlen ≤ 1000
silentbooleanno
pinbooleanno
repeatenumnonone | daily | weekly
scheduled_atdate-timenoISO 8601 instant with a time zone offset

Example request

curl -X PATCH "https://hiboty.com/api/v1/scheduled-posts/3fa85f64-5717-4562-b3fc-2c963f66afa6" \
  -H "Authorization: Bearer $HIBOTY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text":"Our campaign starts tomorrow!","scheduled_at":"2030-01-16T10:00:00+03:00"}'

Example response (200)

JSON
{
  "data": {
    "batch_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "posts": [
      {
        "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "community_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "batch_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "topic_id": 1,
        "text": "string",
        "image_url": "https://example.com/a.png",
        "button_text": "string",
        "button_url": "https://example.com/a.png",
        "silent": true,
        "pin": true,
        "repeat": "none",
        "status": "pending_approval",
        "scheduled_at": "2026-11-06T09:00:00.000Z",
        "retry_at": "2026-11-06T09:00:00.000Z",
        "attempts": 1,
        "message_id": "string",
        "simulated": true,
        "error": "string",
        "reject_reason": "string",
        "created_by": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "reviewed_at": "2026-11-06T09:00:00.000Z",
        "sent_at": "2026-11-06T09:00:00.000Z",
        "clicks": 1,
        "created_at": "2026-11-06T09:00:00.000Z",
        "updated_at": "2026-11-06T09:00:00.000Z"
      }
    ],
    "warnings": [
      {
        "code": "ornek",
        "message": "string"
      }
    ],
    "whatsapp_campaign": {
      "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "status": "string",
      "audience_count": 1
    }
  }
}

Possible errors

  • 400Invalid request: a missing or wrong field, or an unknown field name (validation_error).
  • 401The API key is missing, invalid or revoked (unauthorized).
  • 403Missing scope (scope), the plan doesn't allow it (plan_limit), the role isn't enough (forbidden_role), the email isn't verified (email_not_verified) or the organization is suspended.
  • 404The record doesn't exist or this key can't access it (not_found).
  • 409The action isn't possible in this state; the code gives the reason.post_locked
  • 422Blocked by the content policy (content_policy).content_policy
  • 429A key, user or organization request limit (X-RateLimit-Scope) or the monthly message quota was exceeded; follow the Retry-After header.

Cancels a scheduled post

DELETE/api/v1/scheduled-posts/{id}

Admins can cancel any post, members only their own pending one. On a multi-target post the unsent targets and later rounds of the series are canceled; sent targets don't change. If nothing is left to cancel it returns 409 post_locked. Scope: communities:write.

Scope
communities:write
SDK method
cancelScheduledPost · cancel_scheduled_post
MCP tool
cancelScheduledPostirreversible

Parameters

NameTypeRequiredDescription
idpathuuidyesID

Example request

curl -X DELETE "https://hiboty.com/api/v1/scheduled-posts/3fa85f64-5717-4562-b3fc-2c963f66afa6" \
  -H "Authorization: Bearer $HIBOTY_API_KEY"

Example response (200)

JSON
{
  "data": {
    "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "canceled": true,
    "canceled_targets": 1,
    "sent_targets": 1
  }
}

Possible errors

  • 400Invalid request: a missing or wrong field, or an unknown field name (validation_error).
  • 401The API key is missing, invalid or revoked (unauthorized).
  • 403Missing scope (scope), the plan doesn't allow it (plan_limit), the role isn't enough (forbidden_role), the email isn't verified (email_not_verified) or the organization is suspended.
  • 404The record doesn't exist or this key can't access it (not_found).
  • 409The action isn't possible in this state; the code gives the reason.post_locked
  • 429A key, user or organization request limit (X-RateLimit-Scope) or the monthly message quota was exceeded; follow the Retry-After header.

Publishes a post now

POST/api/v1/scheduled-posts/{id}/publish

On a multi-target post the round's scheduled targets are published and each target's outcome is in posts; targets that don't fit the time budget stay scheduled. A failed post or target is retried with this endpoint. For a single target, a channel error returns 502 channel_error, a policy block 422 content_policy, and a post that isn't scheduled 409 post_locked. In test mode nothing goes to Telegram. Needs admin permission. Scope: communities:write.

Scope
communities:write
SDK method
publishScheduledPost · publish_scheduled_post
MCP tool
publishScheduledPostexternal effect

Supports Idempotency-Key

Parameters

NameTypeRequiredDescription
idpathuuidyesID
Idempotency-KeyheaderstringnoOptional, 1-255 visible ASCII characters. Within 24 hours the same key and body return the first response unchanged; a different body returns 409 idempotency_conflict.len 1–255

Example request

curl -X POST "https://hiboty.com/api/v1/scheduled-posts/3fa85f64-5717-4562-b3fc-2c963f66afa6/publish" \
  -H "Authorization: Bearer $HIBOTY_API_KEY" \
  -H "Idempotency-Key: order-10482"

Example response (200)

JSON
{
  "data": {
    "batch_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "posts": [
      {
        "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "community_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "batch_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "topic_id": 1,
        "text": "string",
        "image_url": "https://example.com/a.png",
        "button_text": "string",
        "button_url": "https://example.com/a.png",
        "silent": true,
        "pin": true,
        "repeat": "none",
        "status": "pending_approval",
        "scheduled_at": "2026-11-06T09:00:00.000Z",
        "retry_at": "2026-11-06T09:00:00.000Z",
        "attempts": 1,
        "message_id": "string",
        "simulated": true,
        "error": "string",
        "reject_reason": "string",
        "created_by": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "reviewed_at": "2026-11-06T09:00:00.000Z",
        "sent_at": "2026-11-06T09:00:00.000Z",
        "clicks": 1,
        "created_at": "2026-11-06T09:00:00.000Z",
        "updated_at": "2026-11-06T09:00:00.000Z"
      }
    ],
    "warnings": [
      {
        "code": "ornek",
        "message": "string"
      }
    ],
    "whatsapp_campaign": {
      "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "status": "string",
      "audience_count": 1
    }
  }
}

Possible errors

  • 400Invalid request: a missing or wrong field, or an unknown field name (validation_error).
  • 401The API key is missing, invalid or revoked (unauthorized).
  • 403Missing scope (scope), the plan doesn't allow it (plan_limit), the role isn't enough (forbidden_role), the email isn't verified (email_not_verified) or the organization is suspended.
  • 404The record doesn't exist or this key can't access it (not_found).
  • 409The action isn't possible in this state; the code gives the reason.post_locked
  • 422Blocked by the content policy (content_policy).content_policy
  • 429A key, user or organization request limit (X-RateLimit-Scope) or the monthly message quota was exceeded; follow the Retry-After header.
  • 502A channel or external service failed (channel_error).channel_error

Approves a pending post

POST/api/v1/scheduled-posts/{id}/approve

The content is rechecked against the current policy (422 content_policy). If its time has passed it's published right away; a publishing error doesn't undo the approval and is returned in warnings. On a multi-target post all targets of the round are approved. If it isn't pending it returns 409 post_locked. Needs admin permission. Scope: communities:write.

Scope
communities:write
SDK method
approveScheduledPost · approve_scheduled_post
MCP tool
approveScheduledPostexternal effect

Supports Idempotency-Key

Parameters

NameTypeRequiredDescription
idpathuuidyesID
Idempotency-KeyheaderstringnoOptional, 1-255 visible ASCII characters. Within 24 hours the same key and body return the first response unchanged; a different body returns 409 idempotency_conflict.len 1–255

Example request

curl -X POST "https://hiboty.com/api/v1/scheduled-posts/3fa85f64-5717-4562-b3fc-2c963f66afa6/approve" \
  -H "Authorization: Bearer $HIBOTY_API_KEY" \
  -H "Idempotency-Key: order-10482"

Example response (200)

JSON
{
  "data": {
    "batch_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "posts": [
      {
        "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "community_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "batch_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "topic_id": 1,
        "text": "string",
        "image_url": "https://example.com/a.png",
        "button_text": "string",
        "button_url": "https://example.com/a.png",
        "silent": true,
        "pin": true,
        "repeat": "none",
        "status": "pending_approval",
        "scheduled_at": "2026-11-06T09:00:00.000Z",
        "retry_at": "2026-11-06T09:00:00.000Z",
        "attempts": 1,
        "message_id": "string",
        "simulated": true,
        "error": "string",
        "reject_reason": "string",
        "created_by": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "reviewed_at": "2026-11-06T09:00:00.000Z",
        "sent_at": "2026-11-06T09:00:00.000Z",
        "clicks": 1,
        "created_at": "2026-11-06T09:00:00.000Z",
        "updated_at": "2026-11-06T09:00:00.000Z"
      }
    ],
    "warnings": [
      {
        "code": "ornek",
        "message": "string"
      }
    ],
    "whatsapp_campaign": {
      "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "status": "string",
      "audience_count": 1
    }
  }
}

Possible errors

  • 400Invalid request: a missing or wrong field, or an unknown field name (validation_error).
  • 401The API key is missing, invalid or revoked (unauthorized).
  • 403Missing scope (scope), the plan doesn't allow it (plan_limit), the role isn't enough (forbidden_role), the email isn't verified (email_not_verified) or the organization is suspended.
  • 404The record doesn't exist or this key can't access it (not_found).
  • 409The action isn't possible in this state; the code gives the reason.post_locked
  • 422Blocked by the content policy (content_policy).content_policy
  • 429A key, user or organization request limit (X-RateLimit-Scope) or the monthly message quota was exceeded; follow the Retry-After header.

Rejects a pending post

POST/api/v1/scheduled-posts/{id}/reject

The reason is optional and is sent to the author. On a multi-target post all targets of the round are rejected. If it isn't pending it returns 409 post_locked. Needs admin permission. Scope: communities:write.

Scope
communities:write
SDK method
rejectScheduledPost · reject_scheduled_post
MCP tool
rejectScheduledPost

Supports Idempotency-Key

Parameters

NameTypeRequiredDescription
idpathuuidyesID
Idempotency-KeyheaderstringnoOptional, 1-255 visible ASCII characters. Within 24 hours the same key and body return the first response unchanged; a different body returns 409 idempotency_conflict.len 1–255

Body fields

NameTypeRequiredDescription
reasonstringnolen ≤ 300

Example request

curl -X POST "https://hiboty.com/api/v1/scheduled-posts/3fa85f64-5717-4562-b3fc-2c963f66afa6/reject" \
  -H "Authorization: Bearer $HIBOTY_API_KEY" \
  -H "Idempotency-Key: order-10482" \
  -H "Content-Type: application/json" \
  -d '{"reason":"Please update the image."}'

Example response (200)

JSON
{
  "data": {
    "batch_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "posts": [
      {
        "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "community_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "batch_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "topic_id": 1,
        "text": "string",
        "image_url": "https://example.com/a.png",
        "button_text": "string",
        "button_url": "https://example.com/a.png",
        "silent": true,
        "pin": true,
        "repeat": "none",
        "status": "pending_approval",
        "scheduled_at": "2026-11-06T09:00:00.000Z",
        "retry_at": "2026-11-06T09:00:00.000Z",
        "attempts": 1,
        "message_id": "string",
        "simulated": true,
        "error": "string",
        "reject_reason": "string",
        "created_by": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "reviewed_at": "2026-11-06T09:00:00.000Z",
        "sent_at": "2026-11-06T09:00:00.000Z",
        "clicks": 1,
        "created_at": "2026-11-06T09:00:00.000Z",
        "updated_at": "2026-11-06T09:00:00.000Z"
      }
    ],
    "warnings": [
      {
        "code": "ornek",
        "message": "string"
      }
    ],
    "whatsapp_campaign": {
      "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "status": "string",
      "audience_count": 1
    }
  }
}

Possible errors

  • 400Invalid request: a missing or wrong field, or an unknown field name (validation_error).
  • 401The API key is missing, invalid or revoked (unauthorized).
  • 403Missing scope (scope), the plan doesn't allow it (plan_limit), the role isn't enough (forbidden_role), the email isn't verified (email_not_verified) or the organization is suspended.
  • 404The record doesn't exist or this key can't access it (not_found).
  • 409The action isn't possible in this state; the code gives the reason.post_locked
  • 429A key, user or organization request limit (X-RateLimit-Scope) or the monthly message quota was exceeded; follow the Retry-After header.

Resends a post with an unknown outcome

POST/api/v1/scheduled-posts/{id}/resend

Only for a post or target in uncertain. Warning: the earlier attempt may have reached Telegram, so the message can appear twice; check the channel first. Other targets aren't touched. If it isn't uncertain it returns 409 post_locked; a channel error returns 502 channel_error. Needs admin permission. Scope: communities:write.

Scope
communities:write
SDK method
resendUncertainPost · resend_uncertain_post
MCP tool
resendUncertainPostexternal effect

Supports Idempotency-Key

Parameters

NameTypeRequiredDescription
idpathuuidyesID
Idempotency-KeyheaderstringnoOptional, 1-255 visible ASCII characters. Within 24 hours the same key and body return the first response unchanged; a different body returns 409 idempotency_conflict.len 1–255

Example request

curl -X POST "https://hiboty.com/api/v1/scheduled-posts/3fa85f64-5717-4562-b3fc-2c963f66afa6/resend" \
  -H "Authorization: Bearer $HIBOTY_API_KEY" \
  -H "Idempotency-Key: order-10482"

Example response (200)

JSON
{
  "data": {
    "batch_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "posts": [
      {
        "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "community_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "batch_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "topic_id": 1,
        "text": "string",
        "image_url": "https://example.com/a.png",
        "button_text": "string",
        "button_url": "https://example.com/a.png",
        "silent": true,
        "pin": true,
        "repeat": "none",
        "status": "pending_approval",
        "scheduled_at": "2026-11-06T09:00:00.000Z",
        "retry_at": "2026-11-06T09:00:00.000Z",
        "attempts": 1,
        "message_id": "string",
        "simulated": true,
        "error": "string",
        "reject_reason": "string",
        "created_by": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "reviewed_at": "2026-11-06T09:00:00.000Z",
        "sent_at": "2026-11-06T09:00:00.000Z",
        "clicks": 1,
        "created_at": "2026-11-06T09:00:00.000Z",
        "updated_at": "2026-11-06T09:00:00.000Z"
      }
    ],
    "warnings": [
      {
        "code": "ornek",
        "message": "string"
      }
    ],
    "whatsapp_campaign": {
      "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "status": "string",
      "audience_count": 1
    }
  }
}

Possible errors

  • 400Invalid request: a missing or wrong field, or an unknown field name (validation_error).
  • 401The API key is missing, invalid or revoked (unauthorized).
  • 403Missing scope (scope), the plan doesn't allow it (plan_limit), the role isn't enough (forbidden_role), the email isn't verified (email_not_verified) or the organization is suspended.
  • 404The record doesn't exist or this key can't access it (not_found).
  • 409The action isn't possible in this state; the code gives the reason.post_locked
  • 422Blocked by the content policy (content_policy).
  • 429A key, user or organization request limit (X-RateLimit-Scope) or the monthly message quota was exceeded; follow the Retry-After header.
  • 502A channel or external service failed (channel_error).channel_error