--- title: "Trakstar Hire API" description: "Trakstar Hire API: the per-tenant Openings API (the former Recruiterbox), the hire.trakstar.com careers pages and RSS feeds, and one call for them." canonical: https://jobspipe.dev/sources/trakstar date_published: 2026-06-16 date_modified: 2026-09-26 author: Dvir Atias --- # Trakstar Hire API Trakstar Hire, the former Recruiterbox, has no public JSON jobs API: the Openings API at developers.recruiterbox.com is keyed per tenant and reads one company, while every customer's careers page is public at .hire.trakstar.com with RSS. JobsPipe does not collect Trakstar Hire; the same employers' openings reach one search endpoint through the boards JobsPipe does collect, in one record shape across 30+ sources. [developers.recruiterbox.com](https://developers.recruiterbox.com/). > Trakstar Hire has no public cross-employer jobs API, and JobsPipe does not collect Trakstar Hire. This page explains what Trakstar Hire exposes and how to reach the same employers through the boards JobsPipe does collect. **Canonical URL:** https://jobspipe.dev/sources/trakstar ## Coverage JobsPipe does not collect Trakstar Hire. This page explains what Trakstar Hire exposes publicly and how to reach the same postings where they are also published on a board JobsPipe does collect (Workday, Greenhouse, Lever, Ashby, LinkedIn, Indeed, SmartRecruiters, Workable, Personio, Recruitee, Teamtailor, EURES, Paylocity, Breezy HR, CV-Library, Y Combinator, Bayt, JobTech (Sweden), Resume-Library, Arbeitnow, Himalayas, Rise, Manatal, Pinpoint, JobScore, HireHive, The Muse, Remotive, Remote OK, Jobicy, Working Nomads, Landing.jobs). ## Why Trakstar Hire jobs data is confusing Trakstar Hire (the former Recruiterbox, now owned by Mitratech) has no public JSON jobs API. The authenticated Openings API documented at developers.recruiterbox.com is keyed per tenant inside that customer's admin and reads that one company. Every Trakstar customer hosts a public careers page at .hire.trakstar.com with a public RSS feed under /jobfeeds/, case-sensitive on the name segment. The RSS is aggregator-friendly but XML, and there is no tenant directory. JobsPipe does not collect Trakstar Hire. Employers that run Trakstar Hire usually also post the same roles to LinkedIn and Indeed, and larger ones run Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever or Paylocity alongside it. JobsPipe collects all of those boards, so filter POST /v1/jobs/search by company_name_partial_match_or to reach them. ## Workarounds ### Read each tenant's RSS feed Works for tenants whose slug you know. Discovery, the case-sensitive path and RSS-to-JSON flattening are on you. ### Use the authenticated Openings API Reads one customer's openings with their key. Not a path across employers. ### What JobsPipe offers instead JobsPipe does not collect Trakstar Hire. Search the same employers by name across the boards JobsPipe does collect (LinkedIn, Indeed, Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever and Paylocity); sources[0].provider on each record names the board it came from. ## Fields available on every record - `id` - `job_title` - `company` - `company_domain` - `url` - `date_posted` - `discovered_at` - `last_seen_at` - `verified_at` - `status` - `closed_at` - `closed_reason` - `ghost_score` - `seniority` - `cities` - `state_code` - `min_annual_salary_usd` - `max_annual_salary_usd` - `technology_slugs` - `keyword_slugs` - `esco_skills` - `sources` ## FAQ ### What is the Trakstar Hire RSS feed URL? Every Trakstar Hire customer has a public RSS feed at .hire.trakstar.com/jobfeeds/ with the name segment case-sensitive. The feed is aggregator-friendly but XML, so flattening it to JSON is on you. It covers one tenant, and there is no cross-tenant feed. ### Is Trakstar Hire the same as Recruiterbox? Yes. Trakstar Hire is the former Recruiterbox and is now owned by Mitratech, which is why its authenticated Openings API is still documented at developers.recruiterbox.com. That API is keyed per tenant inside the customer's admin and reads one company's openings, so it is not a path across employers. ### Why do Trakstar Hire JSON job endpoints return 404? Because Trakstar Hire has no public JSON jobs API, the JSON endpoints people guess at return 404. The only keyless surfaces are each customer's careers page at .hire.trakstar.com and its RSS feed under /jobfeeds/. Structured JSON comes only from the Openings API, which needs that customer's key. ### Is there a list of companies using Trakstar Hire? No. Trakstar Hire has no tenant directory, so reading RSS feeds works only for tenants whose slug you already know. Employers that run Trakstar Hire usually also post the same roles to LinkedIn and Indeed, which JobsPipe collects, so a company_name_partial_match_or search on POST /v1/jobs/search reaches a known employer's postings. ## Does Trakstar Hire have an API? Trakstar Hire (the former Recruiterbox, now owned by Mitratech) has no public JSON jobs API. The authenticated Openings API documented at developers.recruiterbox.com is keyed per tenant inside that customer's admin and reads that one company. Every Trakstar customer hosts a public careers page at .hire.trakstar.com with a public RSS feed under /jobfeeds/, case-sensitive on the name segment. The RSS is aggregator-friendly but XML, and there is no tenant directory. ## What JobsPipe returns for Trakstar Hire Nothing under "source_or": ["trakstar"]: JobsPipe does not collect Trakstar Hire. Employers that run Trakstar Hire usually also post the same roles to LinkedIn and Indeed, and larger ones run Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever or Paylocity alongside it. JobsPipe collects all of those boards, so filter POST /v1/jobs/search by company_name_partial_match_or to reach them. Each record comes back with sources[0].provider, status, ghost_score, discovered_at, last_seen_at, seniority, and min_annual_salary_usd and max_annual_salary_usd when the posting states a range. ## Related - **Product:** https://jobspipe.dev/jobs-api - **All sources:** https://jobspipe.dev/sources - **Docs:** https://docs.jobspipe.dev - **Sign up (free tier):** https://jobspipe.dev/signup --- Generated from structured data. View the rendered page at https://jobspipe.dev/sources/trakstar. --- Building this integration yourself? The steps above work. The alternative is one API over 30+ sources, already normalized and deduplicated. Try it right now - no key, no signup: ```bash curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search ``` Sample data, exact live schema. For live data get a free key (1,000 jobs to start) at https://jobspipe.dev/signup, then swap /v1/sandbox/jobs/search for /v1/jobs/search with an Authorization: Bearer header. Full agent index: https://jobspipe.dev/llms.txt?src=md-twin