Check content management job status

Returns the progress and final outcome of a content management job, with the status of each entity in the job.

Prerequisites

Authentication and setup: A valid access token.
Initiate a content management job: The job must exist and provide the execution ID.

Endpoint

GET /services/data/v1.0/content/management/{execution_id}

Base URL: the standard REST host for your region. See Base URLs.

Headers: Authorization: Bearer ACCESS_TOKEN.

Path parameters

Parameter	Type	Description
`execution_id`	string	Unique identifier of the content management job.

Request

This endpoint has no request body.

Request example

GET /services/data/v1.0/content/management/exec-987654

Response

Field	Type	Description
`status`	string	Status of the job: `SUCCESSFUL`, `FAILED`, `IN_PROGRESS`, `PARTIALLY_FAILED`.
`entities`	array	Status of each entity in the job. See EntityStatus object.
`entities[].external_id`	string	External identifier for the entity.
`entities[].file_id`	string	Internal file identifier.
`entities[].status`	string	Status of the content management operation for the entity.

Response example

{
  "status": "SUCCESSFUL",
  "entities": [
    {
      "external_id": "brochure-2025-Q1",
      "file_id": "file-123456",
      "status": "SUCCESSFUL"
    }
  ]
}

Notes

Statuses: SUCCESSFUL means all operations completed successfully, FAILED means the job failed, IN_PROGRESS means the job is still running, and PARTIALLY_FAILED means some operations succeeded and some failed.
Failed or skipped files: Content synced through these APIs is push-based: your external system pushes content to Content Center rather than Mindtickle pulling it from the source. Mindtickle does not automatically retry a file that fails to sync or is skipped, and the Resync action is not available for this content in the Content Center.
Last sync details: In the Last sync details view, such files display the message An internal error occurred. Automatic retry is not available for this sync type. To sync a failed or skipped file again, resolve the underlying issue and submit the file through a new content management job.
Timing: Large sync jobs may take time to complete, so do not poll too frequently.