TOtoksta
Analysis

Get content match evidence posts

Fetch the matched posts (evidence) for content-match analyses. Same selection modes as /v1/content-match/results (job_id/job_ids accepting content-fit:<uuid> or bare UUID, or creator_ids/result sets + optional campaign_id).

post/v1/content-match/posts

Request

Request body

job_idstring

A single content-match job ID (content-fit:<uuid> or bare UUID).

job_idsstring[]
creator_idsstring[]

Creator UUIDs to operate on. Takes precedence over result_set_id / result_set_ids when provided.

result_set_idstring

A single result_set_id returned by a prior discovery search. Resolved to its ranked creators.

result_set_idsstring[]

Multiple result set IDs to merge (dedupe) into one creator selection.

top_ninteger

When selecting from result set(s), take only the top N ranked creators.

ranksinteger[]

When a single result_set_id is provided, select specific 1-based ranks (e.g. [1,3,5]).

campaign_idstring

Optional campaign UUID to scope creator-based lookups.

posts_limit_per_creatorinteger

Matched posts per creator (1-10). Defaults to 3.

detail_level'summary' | 'full'

Response verbosity. summary (default) returns trimmed fields; full returns the complete records.

wait_secondsinteger

Optional inline poll. Holds the request up to this many seconds (max 30) waiting for jobs to reach a terminal state before returning. Defaults to 0 (return immediately).

Example request

{
  "job_id": "content-fit:56232ac2-8068-4dcb-9d1a-1f2e3a4b5c6d",
  "detail_level": "full",
  "posts_limit_per_creator": 5
}

Response

Matched posts for content-match analyses.

successtrue required
dataobject required

Operation payload. See the example for the exact field structure.

Example response

{
  "success": true,
  "data": {
    "selection": {
      "source": "job_id",
      "selected_count": 1
    },
    "requested_count": 1,
    "found_count": 1,
    "not_found_ids": [],
    "expired_ids": [],
    "detail_level": "full",
    "posts_limit_per_creator": 5,
    "results": [
      {
        "source": "job_id content-fit:56232ac2-8068-4dcb-9d1a-1f2e3a4b5c6d",
        "job_id": "content-fit:56232ac2-8068-4dcb-9d1a-1f2e3a4b5c6d",
        "analysis_id": "56232ac2-8068-4dcb-9d1a-1f2e3a4b5c6d",
        "creator_id": "f0e1d2c3-b4a5-4678-9abc-def012345678",
        "creator_name": "Jane Marketer",
        "status": "succeeded",
        "match_score": 78,
        "matching_posts_count": 6,
        "returned_posts_count": 5,
        "has_more_matched_posts": true,
        "matched_posts": [
          {
            "title": "Why DevEx wins",
            "post_url": "https://www.linkedin.com/posts/jane-marketer_...",
            "posted_date": "2026-05-18",
            "content_type": "text",
            "match_score": 81,
            "keyword_matches": [
              "developer tools"
            ],
            "match_reason": "Directly discusses developer tooling adoption."
          }
        ]
      }
    ]
  },
  "meta": {
    "request_id": "req_01HXYZ...",
    "trace_id": "4f1d...c2"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.