Job Status

Status of a single Career Monitor job.

Endpoint

Method: GET Path: /career-monitor/jobs/{job_id}/ Full URL: https://backend.ecoreservice.com/api/v1/career-monitor/jobs/{job_id}/ Auth: Authorization: Token YOUR_API_TOKEN (or Bearer) — see Authentication

Example Request

curl "https://backend.ecoreservice.com/api/v1/career-monitor/jobs/123/" \
  -H "Authorization: Token YOUR_API_TOKEN"

Successful Response — 200 OK

{
  "job_id": 123,
  "title": "Q1 check",
  "status": "Processing",
  "total_records": 2,
  "processed_records": 1,
  "submitted_at": "2026-07-09T10:15:00Z",
  "started_at": "2026-07-09T10:15:03Z",
  "completed_at": null,
  "total_credits_charged": 0.0,
  "credit_charge_failed": false,
  "credit_charge_failure_reason": null
}

Field	Type	Description
job_id	integer	The job identifier
title	string	Job label
status	string	Pending / Processing / Completed / Failed
total_records	integer	Records in the job
processed_records	integer	Records finished so far
submitted_at / started_at / completed_at	datetime | null	Lifecycle timestamps (completed_at is null until done)
total_credits_charged	number	Net credits charged (0 until the job completes)
credit_charge_failed	boolean	true if the post-completion charge failed
credit_charge_failure_reason	string | null	Reason when credit_charge_failed is true

Job Status Values

Status	Meaning
Pending	Job created, not yet started
Processing	Job is running
Completed	Done — fetch Results
Failed	Job failed

Polling Guidance

Poll this endpoint until status is Completed (or Failed), then fetch Results. Results can also be polled while the job is still Processing — unfinished rows report Pending / Processing.

Error Responses

HTTP	When	Body
401	Missing or invalid token	{ "detail": "Authentication credentials were not provided." }
404	Job not found / not owned by this account	{ "detail": "Not found." }

See Error Codes for the full list.