500
Retry with backoffSearch backend error — The search backend errored while serving the request.
Response body
{ "error": { "code": "search_error", … } }
Should you retry?
Yes — with exponential backoff, and honour Retry-After
when it is present.
What it means
Transient. Mid-pagination it is safe to re-request the same page — reads are idempotent. The body is deliberately terse — it carries no index names, hostnames or ARNs — so quote error.request_id (also on the X-Request-Id header) when you report one. An unhandled failure outside the search path reports internal_error instead.
Common causes
- A transient fault in the search cluster.
- A query heavy enough to time out — very broad free-text with a wide scope.
How to fix it
Retry with exponential backoff and a cap. If it persists on one specific query, narrow the scope or the free-text term and check jobfront.com/status.
Endpoints that return this
Read from the OpenAPI specification, so this list cannot claim an endpoint returns a status the contract does not list.
| Method | Endpoint | What it does |
|---|---|---|
| GET | /v4/jobs | Search jobs |
| GET | /v4/jobs/options | Job facet values |
| GET | /v4/jobs/{job_id} | One job by global id |
| GET | /v4/sources | Search sources (companies) |
| GET | /v4/sources/options | Source facet values |
| GET | /v4/sources-id/{source_id} | One source by id |
| GET | /v4/sources-url/{url_source} | One source by URL |
| GET | /v4/sources-id/{source_id}/jobs | A source's jobs (by id) |
| GET | /v4/sources/{url_source}/jobs | A source's jobs (by URL) |
| GET | /v4/jobs/hidden | Jobs you have hidden |
| POST | /v4/jobs/hidden/{job_id} | Hide a job |
| DELETE | /v4/jobs/hidden/{job_id} | Un-hide a job |
| GET | /v4/sources/blocked | Companies you have blocked |
| POST | /v4/sources/blocked/{source_id} | Block a company |
| DELETE | /v4/sources/blocked/{source_id} | Unblock a company |