Search first.
Details when needed.
A focused API for job search and individual listings. Start with a query and explicit filters, then retrieve full details using a returned job ID.
POST /v1/jobs/searchGET /v1/jobs/{id}Search request fields
REST and MCP use the same search arguments. The local server returns synthetic fixture data.
| Field | Use in the request |
|---|---|
query | Search text for the role or skills you need. |
location | A place id with mode: "administrative". |
geo | Use lat, lon, and radiusKm for a coordinate search, instead of location. Radius must be positive; latitude and longitude must be valid coordinates. |
filters | workModes and employmentTypes narrow the results. Read the available choices from GET /v1/metadata. |
pageSize | Between 1 and 50 summaries; defaults to 25. This five-record fixture returns nextCursor: null. |
Retrieve individual details
Use a returned id for one detail operation. Selecting a summary does not fetch its full description. In the playground, choose Fetch full details to take that step.
Places and filter choices
Use GET /v1/locations?query=San for fixture place suggestions and GET /v1/metadata for supported work modes and employment types. Interactive API documentation is available on the API server at 127.0.0.1:4001/docs .
{
"query": "engineer",
"location": {
"id": "san-francisco-ca-us",
"mode": "administrative"
},
"filters": {
"workModes": []
},
"pageSize": 25
}The browser sends REST requests through its local API proxy. MCP selection changes the example format; it does not connect an agent.
The product flow covers job search and individual job details. Bulk exports, full-dataset access, and LLM-performed searches are outside this flow.