Get Job Details via Jobs API

This page guides you through the process of retrieving detailed information about a specific job using the Jobs API. This API allows you to access detailed data on job status, start and end times, and more.

Required Parameters

Before using the Jobs API, ensure you have the following:

• Job ID: The ID of the specific job you want to query.
• Pipeline ID: The ID of the pipeline for which you want to list jobs.
• Component ID: The ID of the component within the pipeline.

If you have the Job ID but not the Pipeline ID or Component ID, search with Advanced Job Search using job_id:<your-job-id>. Search results include pipeline_id, step_id, and the Job details. The direct Get Job endpoint still requires all three IDs.

GET Job Details

To retrieve details about a specific job, use the following endpoint:

curl --location 'https://api.platform.datastreamer.io/api/pipelines/:PipelineId/components/:ComponentId/jobs/:JobId' \
--header 'apikey: API_KEY'

API Reference: Get a Job

Example

Here is an example of how the curl command might look after replacing the placeholders:

curl --location 'https://api.platform.datastreamer.io/api/pipelines/12345/components/67890/jobs/job123' \
--header 'apikey: abcdef123456'

The API will return a JSON response containing details of the job, such as job properties, and status.

{
    "type": "job",
    "organization_id": "11111111-1111-1111-1111-111111111111",
    "pipeline_id": "12345",
    "step_id": "67890",
    "job_id": "job123",
    "state": "succeeded",
    "job_name": "test_twitter_auto",
    "data_source": "twitter_auto",
    "job_type": "oneTime",
    "priority": "normal",
    "preferred_start_time": "2026-09-15T19:15:31.910854Z",
    "query_from": "2026-09-14T00:00:00Z",
    "query_to": "2026-09-15T00:00:00Z",
    "query": {
        "platform": "twitter",
        "query": "test",
        "prioritization": "coverage",
        "per_day_limit": null,
        "include": [ { "max_documents": null } ]
    },
    "query_start_offset": 0,
    "start_time_offset": 0,
    "max_documents": 10,
    "secondary_max_documents": 0,
    "created": "2026-09-15T19:15:28.60794Z",
    "updated": "2026-09-15T19:16:32.420828Z",
    "started": "2026-09-15T19:15:31.919687Z",
    "ended": "2026-09-15T19:16:32.420828Z",
    "schedule_time": "2026-09-15T19:15:31.919687Z",
    "document_count": 10,
    "secondary_document_count": 0,
    "elapsed_time_ms": 2899,
    "run_count": 1,
    "error": ""
}

Response Fields

The response includes:

• state: the current job state (for example running, succeeded, failed, or cancelled). Earlier versions returned this as job_state.
• query: an object rather than a string. It always carries query, and for source jobs also platform, prioritization, per_day_limit, and include.
• error: the failure reason when state is failed. It is an empty string otherwise.
• Timing and result fields: started, ended, schedule_time, elapsed_time_ms, run_count, document_count, and secondary_document_count report when the job ran and what it returned.