listingsAPIlistingsAPI
Get API keySign in
DELETE/api/v4/posts/{postId}

Delete a post

Permanently deletes a social post campaign and removes it from every site it was published to.

Requires an API key. See Authentication for header format and key rotation.

Parameters

Path

NameTypeRequiredDescription
postIdstringrequiredBase64-encoded social post ID to delete (the `id` from a posts list or the create response).

Body

NameTypeRequiredDescription
clientMutationIdstringoptionalOptional client-supplied token echoed back in the response, for correlating the request.

Sample request

Ready-to-paste body. Replace placeholder IDs and values with yours.

{
  "clientMutationId": "delete-44122-req-1"
}

Responses

200Post deleted. `socialPostId` echoes the deleted post's ID.
{
  "data": {
    "deleteSocialPost": {
      "success": true,
      "socialPostId": "U29jaWFsUG9zdDo0NDEyMg=="
    }
  }
}
401Unauthenticated — missing or invalid API key.

Deletes the specified post campaign. This is permanent: the post is removed from listingsAPI and unpublished from every site it reached (Google, Facebook). Deleting a live post takes it down from the connected profiles; there is no undo.

Use case — retract a mistaken announcement. If an announcement went out with the wrong hours, delete it with DELETE /posts/{postId} (using the id from the posts list), confirm success: true, then publish a corrected one with POST /posts. To pull a campaign from every store at once, delete the bulk campaign by its bulk ID instead.

Notes.

  • The request body is optional. Send clientMutationId only if you want the value echoed back for request correlation; the generated snippet includes it as an example.
  • A post that already finished its scheduled window may report status: EXPIRED and no longer be live on each site, but deleting it still clears it from listingsAPI.
  • Deleting an already-deleted or unknown post returns an error envelope ({"data":null,"errors":[...]}) rather than success: true.

Write operation — not executed against the live account. The request and response shown are built from the API schema.

curl -X DELETE 'https://listingsapi.com/api/v4/posts/<postId>' \
  -H "Authorization: API $LISTINGSAPI_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "clientMutationId": "<clientMutationId>"
  }'
Run in playground