Get Prospecting Job Status

GET https://api.onfire.ai/data-access-api/v1/prospecting/jobs/{job_id}

Return the current status of a prospecting job without the prospects payload. Use this endpoint to poll a running job — once status transitions away from running, fetch the full payload from Get Job Results.

The job is scoped to the authenticated tenant. Jobs created by a different tenant return 403 Forbidden.

Headers

Header	Required	Description
X-Api-Key	Yes	Your tenant API key.

Path parameters

Parameter	Type	Description
job_id	int	The id returned by POST /prospecting/start.

Example request

curl "https://api.onfire.ai/data-access-api/v1/prospecting/jobs/1842" \
  -H "X-Api-Key: your-api-key"

Responses

200 — Success

{
  "job_id": 1842,
  "status": "success",
  "tenant_id": "your-tenant",
  "company_linkedin_url": "https://www.linkedin.com/company/crowdstrike",
  "team": "smb",
  "client_email": "ae@example.com",
  "run_start_time": "2026-05-18T14:02:11.482000+00:00",
  "run_end_time":   "2026-05-18T14:07:48.117000+00:00",
  "failure_reason": null
}

Field	Type	Description
job_id	int	The job id you passed in the URL.
status	string	One of running, success, failed.
tenant_id	string	Tenant that owns the job — must match the authenticated tenant.
company_linkedin_url	string	The company URL the run was started with.
team	string	Team name (may be null).
client_email	string	Email captured at start time (may be null).
run_start_time	string	ISO 8601 UTC timestamp.
run_end_time	string	ISO 8601 UTC timestamp. null while status = running.
failure_reason	string	Short failure description. Populated only when status = failed.

401 — Invalid or missing API key

{ "detail": "Invalid API key" }

403 — Wrong tenant

{ "detail": "Job belongs to a different tenant" }

404 — Job not found

{ "detail": "Job not found" }

502 / 504 — Phoenix upstream error / timeout

The downstream prospecting service returned an error or timed out while reading the run record.

Polling guidance

• Start with a short interval (e.g. 5–10 seconds) for the first minute, then back off to 30–60 seconds. Most runs complete in 2–5 minutes.
• Treat any status other than running as terminal — success or failed will not transition again.
• On failed, failure_reason is the only payload you’ll need. There will be no prospects to fetch.