Posts
Delete Posts
Delete one or many posts with a single request
POST
Delete one or many posts in a single request. The endpoint enforces key scope, cleans up provider-side artifacts, and reports a per-ID result so your integration can surface partial successes.Documentation Index
Fetch the complete documentation index at: https://docs.genviral.io/llms.txt
Use this file to discover all available pages before exploring further.
Body Parameters
Array of post UUIDs (minimum 1, maximum 50). Duplicates are removed before
processing. The API accepts both
postIds (preferred) and the snake_case
alias post_ids.All IDs must belong to the authenticated key scope. IDs outside scope are
treated as
skipped.Status Guardrails
- Deletable:
draft,pending,scheduled,retry,failed - Blocked:
posted,canceled,partial
posted) or that have been canceled /
partially published are immutable. They are returned inside
blockedStatuses so you can surface the exact status that blocked deletion.
Response
IDs that were permanently removed. Order matches the request order after
duplicates are stripped.
Entries of
{(id, status)} describing posts that failed the status guardrail.IDs that were not found under key scope (already deleted, outside scope, or
never existed).
Optional. Keyed by post ID when the database delete fails. A batch can still
return
200 with a populated errors map.Request Example
Response Example
Error Responses
400 invalid_json- body is not valid JSON422 invalid_payload- missing/invalidpostIds400 too_many_post_ids- more than 50 IDs supplied401- authentication failed (missing/invalid/revoked token)402 subscription_required- active Creator/Professional/Business plan required403 tier_not_allowed- Scheduler tier cannot use Partner API500 bulk_delete_failed- unexpected server error (all attempted IDs are still reported in the response body when possible)
