- Freeform text on each job. When you create a job you pass
locationas plain text (for example"Paris, France","Remote", or a full street address). That is what shows on the listing. - Normalized locations. Geocoded entities (city, state, country, coordinates) that power location landing pages and filters. Each job is linked to one.
POST /locations, then pass the returned id as location_id when you create the job. That is the reliable path: you see exactly which place you are about to use, and the job is guaranteed to land on the right city page and filter.
Street addresses resolve to their city. A job is browsed by city, so the city is the entity. Keep the full street address in the job’s own
location text: that is what candidates read, and its exact coordinates are stored on the job for map pins.Resolve a place
Any place description:
"Gatineau, QC", "33 Rue des Freres-Moncion, Gatineau", a postal code, or "Remote".Two-letter country code to disambiguate, e.g.
ca. Recommended whenever you know it: without it, "Victoria" could be Australia or British Columbia.false previews matches without writing anything. true commits the best match and returns its id.cURL
id is null when the place is not on your board yet. Re-send with "create": true to commit it:
Fields
exact (already an entity, or a single unambiguous hit), high (clear top hit), or low (one of several plausible hits: confirm before using).The street-level address that matched, when your query was an address. Useful as the job’s
location text.Resolution checks your board’s existing locations first, then a shared geocode cache, and only calls the geocoder as a last resort. Repeat queries and places you already cover cost nothing.
Filtering jobs by location
Use thelocations query parameter on Get Jobs (comma-separated, matched against the job’s freeform location):
cURL
List your locations
Filter to one level of the hierarchy:
country, state, city, area, or remote. Any other value returns a 400 validation_error.cURL