Skip to content

Posts endpoints ​

Reference for the /post endpoint family in API V2.

What is a post? ​

A post is a collected content item ingested by a job and stored inside a project. Posts come from monitored platforms and carry fields such as text content, author, publication timestamp, platform code, engagement metrics, sentiment, priority, and assigned tags.

Capabilities ​

This endpoint family covers:

  • Search and count — filter posts using date ranges, platforms, sentiment, priority, jobs, tags, language, author, and text search
  • Export — download filtered post sets for external use
  • Update — modify post fields such as sentiment, priority, or tags
  • Delete — remove specific posts from a project
  • Get tags — retrieve the tags assigned to a post
  • Translate — request a translation of the post text
  • Summarize — generate an AI-based summary of a filtered dataset

Shared filters ​

Search, count, export, and summarize endpoints accept a common set of filters in the request body:

FilterDescription
startDate / endDateDate range for post_time
platformOne or more platform codes
sentimentSentiment value filter
priorityPriority value filter
jobsFilter by job id list
tagsFilter by tag id list with operator (or, and, not)
langLanguage code filter
authorAuthor filter
text_searchBoolean text search string

Authentication ​

Authentication is required. See Authentication.

Permissions ​

Permissions are tier-based and vary by endpoint.

EndpointMinimum tier
post/search, post/count, post/export, post/gettags, post/translate, post/summarize4 (User)
post/update, post/delete3 (Editor)

Caching ​

Search and count responses may be served from cache. Send Cache-Control: no-cache to bypass the cache and force a live query.

Endpoints ​

Notes ​

  • All endpoints in this family require a project_id to scope the operation.
  • This section documents only V2 paths (/v2/...).

Doc rev.1.12.3 2026.05.08