Analysis

Start content match analysis

Start LinkedIn content-fit analysis for a creator selection. Requires a user-scoped key.

Selection (provide exactly one): creator_ids, result_set_id, or result_set_ids.

Topic criteria: for ad hoc runs (no campaign_id) you MUST provide topic_keywords (array of strings). The field is topic_keywords, NOT topics. When campaign_id is supplied, criteria are read from the campaign instead.

Returns 202 with prefixed job IDs in the form content-fit:<uuid> under data.job_ids and data.jobs[].job_id. jobs_created is 0 for creators already analyzed. Use those IDs with POST /v1/content-match/results. Cost: 3/5/8 credits per analysis based on posts_to_analyze (10/20/30).

post/v1/creators/content-match

Request

Request body

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. When set, content criteria come from the campaign.

campaign_briefstring

Optional human-readable brief used as the analysis name.

topic_keywordsstring[]

Topic keywords for ad hoc content match. REQUIRED when no campaign_id is provided. (Alias: keywords.)

linkedin_content_typesstring[]

Optional content-type filter.

posts_to_analyze10 | 20 | 30

Posts analyzed per creator. 10 (3cr), 20 (5cr), or 30 (8cr). Defaults to 10.

Example request

{
  "creator_ids": [
    "f0e1d2c3-b4a5-4678-9abc-def012345678"
  ],
  "topic_keywords": [
    "developer tools",
    "API platforms",
    "DevEx"
  ],
  "posts_to_analyze": 10
}

Response

Content match jobs queued. Job IDs are prefixed content-fit:<uuid>.

successtrue required
dataobject required

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

Example response

{
  "success": true,
  "data": {
    "creators_requested": 2,
    "selection": {
      "source": "creator_ids",
      "selected_count": 2
    },
    "campaign_id": null,
    "posts_to_analyze": 10,
    "jobs_created": 2,
    "job_ids": [
      "content-fit:56232ac2-8068-4dcb-9d1a-1f2e3a4b5c6d",
      "content-fit:7a8b9c0d-1e2f-4a3b-8c9d-0e1f2a3b4c5d"
    ],
    "jobs": [
      {
        "creator_id": "f0e1d2c3-b4a5-4678-9abc-def012345678",
        "analysis_id": "56232ac2-8068-4dcb-9d1a-1f2e3a4b5c6d",
        "job_id": "content-fit:56232ac2-8068-4dcb-9d1a-1f2e3a4b5c6d",
        "status": "pending",
        "cached": false,
        "message": "Content analysis started. This may take a minute.",
        "creator_name": "Jane Marketer",
        "profile_url": "https://www.linkedin.com/in/jane-marketer/"
      }
    ],
    "failures": []
  },
  "meta": {
    "request_id": "req_01HXYZ...",
    "trace_id": "4f1d...c2"
  }
}

Changes

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