`. Unescape it once before storing. Some HTML libraries re-escape the result when you serialize it again, so check that the stored text contains real `<` characters. **`remote` is a string.** It's `"true"` or `"false"`, not a boolean. In most languages the string `"false"` is truthy, so `bool(ld["remote"])` marks every job as remote. Compare with the string instead. **Country is a full name.** `addressCountry` is `India`, not `IN`, so you need a name-to-code lookup. **A dead career site still returns 200.** A company that has left Freshteam can leave behind a page that says the site couldn't be found and offers to let you claim it. It returns HTTP 200, so check the text rather than the status before treating the board as empty. **A missing job returns 404.** That's a clean signal the job is gone. Otherwise, treat a job as closed when it disappears from a complete list. See [syncing job data in depth](https://cleanjobdata.com/guides/syncing-job-data-in-depth). **There's no salary field.** If pay is disclosed, it's in the description text. **One request per job.** The list page gives only job links grouped by department, with no date or location, so every new job costs a page fetch. Fetch new IDs only and keep the request rate modest. ## Public Pages vs Freshteam's Official API Freshteam has an official REST API for its customers. It needs an API key from the employer's own Freshteam account and covers that company's hiring data. For published job ads from companies you don't work with, the public career site and its JSON-LD are the source to use. ## When This Is Enough For one company, one list page plus a JSON-LD read per job is simple, as long as you handle the swapped address fields and the encoded description. ## When It Isn't Across many companies and platforms you end up maintaining a different collector for each, and many of them have quirks like Freshteam's swapped fields that only show up when you check real postings. The [ATS public job postings API list](https://cleanjobdata.com/articles/ats-public-job-postings-api-list) covers the differences. CleanJobData reads Freshteam career sites alongside other platforms and returns one schema, with locations resolved to cities, states and countries, a remote type and an employment type. Try it in the [Playground](https://cleanjobdata.com/playground) or see the [API Documentation](https://cleanjobdata.com/docs). ## Skip the scraper: get this data from the CleanJobData API If you'd rather not maintain a Freshteam collector, you can query normalized jobs from ATS platforms and company career sites with a single request. The response has structured city/state/country locations, parsed salary when the employer publishes one, a remote type, and company metadata, and you page through results with the cursor in `pagination.next_page`. ```bash curl "https://api.cleanjobdata.com/jobs?title=engineer&domain=acme.freshteam.com&limit=20" \ -H "Authorization: Bearer $CLEANJOBDATA_API_KEY" ``` The `domain` filter is an exact match on the host of each job's `application_url`. Freshteam jobs apply on each company's own `freshteam.com` subdomain, so this scopes the query to one employer; use `company_website_url` or `employer_id` as alternatives. Coverage depends on which employers are in the dataset, so check that the companies you care about appear before you rely on it. - [Jobs API reference](https://cleanjobdata.com/docs/api/jobs) for every filter and response field - [Playground](https://cleanjobdata.com/playground) to run queries without writing code - [Pricing](https://cleanjobdata.com/pricing) — the Trial is free with no card required ## FAQ ### Does Freshteam have a public jobs API? Not for reading other companies' job listings. Freshteam's REST API needs an API key from the employer's account. Public job data comes from the career site at `{company}.freshteam.com/jobs` and the schema.org `JobPosting` JSON-LD on each job page. ### Why are city and state reversed in Freshteam's JSON-LD? Freshteam puts the city in `addressRegion` and the state in `addressLocality`, the opposite of the schema.org definitions. It happens on every Freshteam career site we've checked, so swap the two fields once in your parser. ### How do I decode the Freshteam job description? The `description` in the JSON-LD is HTML escaped as entities, such as `<p>`. Run it through an HTML unescape function once, for example `html.unescape` in Python, to get normal HTML. ### Does Freshteam include salary data? No. The JSON-LD on Freshteam job pages has no `baseSalary`, so pay only appears when the employer writes it into the description.