Get a content job

Requires `posts:read`. The poll endpoint for `POST /content/...`. Each read refreshes `counts.syncing` / `complete` / `failed` from the member posts' processing status and settles the job to `completed`, `partial` (some links skipped, rejected, or failed to process), or `failed` (nothing was added). Non-terminal responses include `Retry-After` and `meta.pollAfterMs`. `accepted[]` carries each created `postId` (and `postStatus` while syncing); `skipped[]` and `rejected[]` carry a `reason` (`already_complete`, `already_processing`, `duplicate_in_batch`, `unsupported_platform`, `invalid_url`, `insufficient_credits`, …). Rate class `content_jobs` (60 / minute, 2,000 / day per key).

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

OR
X-Api-Keystring
API Key authentication via header

Path parameters

jobIdstringRequired

Response headers

Retry-Afterinteger

Present while the job is discovering, queuing, or syncing

Response

Content job detail
dataobjectOptional
metaobjectOptional

Errors

404
Not Found Error