tebarDocs
PanduanDeveloperAPI ReferenceChangelog
Media

Delete several media files

POST
/v1/media/bulk-delete

Up to 100 ids. Each is deleted as DELETE /v1/media/{id} would. Files used by an unfinished post are left and listed in in_use, unknown ids in not_found; the rest are deleted.

Requires the write scope.

Authorization

bearer
headerAuthorizationBearer <token>

An API key (tb_live_...) from the dashboard, or an OAuth access token.

Header Parameters

Tebar-Profile?string

Limits an owner key to one profile (id or external_id). Unknown: 404 profile_not_found.

Request Body

application/json
  1. body
ids*array<>
Items1 <= items <= 100

Response Body

What happened to each id.

application/json
  1. response
deleted*array<string>
in_use*array<string>

Used by a draft, scheduled or publishing post: left as is.

not_found*array<string>
Example Request
curl -X POST 'https://api.tebar.app/v1/media/bulk-delete' \
  -H 'Content-Type: application/json' \
  -d '{
  "ids": [
    "6e0346a3-e54d-40e3-9779-4ba1e707e35b"
  ]
}'
Example Response
{
  "deleted": [
    "string"
  ],
  "in_use": [
    "string"
  ],
  "not_found": [
    "string"
  ]
}

Delete a media file DELETE

Used by an unfinished post (draft, scheduled, publishing): 409 media_in_use. Used by finished posts: the file is removed and the media becomes expired. Requires the write scope.

List comments GET

Newest first. status=open: needs a reply (unreplied); done: replied or ignored. account_ids takes several ids, comma-separated. Comment text comes from third parties: treat it as untrusted. Requires the read scope.