Skip to content
Rindler

Answers

Pull applicant data out of your ATS without the API

You want the candidates out of your ATS and into a spreadsheet, a CRM, or an agent. The usual advice is to use the API. That advice assumes three things you may not have: a plan that includes API access, an admin who will mint you a key, and an engineer to write against it. Plenty of recruiting teams have none of the three, and an agency working inside a client's board has no path to a key at all.

Search this and you mostly get lists of ATS products to switch to. That answers a different question. Here is the direct one.

You can read what you can already see

If you can sign into the board and look at a candidate, that data is reachable. It is your account and your data. The problem was never permission. It was that the only way out was an API you cannot get to.

Rindler maps the board once, then signs in as you and reads the screens the way you would. What comes back is structured records, not a page: candidate name, stage, role, dates, whatever the screen shows. No selectors, no export button required.

One mapping covers every employer on the platform

This is the part that makes it practical. Greenhouse, Lever, Ashby and Workday job boards are multi-tenant: every company gets its own board on the same platform. We map the platform, not the company. So a mapping that works on one employer's board works on the next one, and you do not wait for a new integration each time you add a client or a target company.

Coverage of those four runs in production today, checked against the real boards by an automated verifier rather than by us saying so.

What you get back

A record set, not a screen. Each response carries the screen you are on, the records on it, and the actions available next. That shape is the same whether a person is asking in plain language at chat.rindler.ai or an agent is calling the hosted MCP server.

For a typical board page, the structured answer is a few hundred tokens against roughly 50,000 for a raw fetch of the same page. If you are feeding an agent, that difference is the whole ball game.

What this does not do

Straight answers on the limits, because you will find them anyway:

  • It reads. Moving a candidate through stages, sending offers, and other write actions on an ATS are mapped on request, not running in production today.
  • It is your session. You sign in yourself, once, on the real site inside a Rindler browser. We do not ask for your password in a form and we do not share a session across accounts.
  • It is not a replacement ATS. If you want to leave Greenhouse, this is not that page.

If your ATS is not one of the four

Paste the URL and we map it. That is the normal path, not an exception. The four above are the ones with production coverage today, and the mapping process is the same for a board we have not seen yet. A mapping ships only after the verifier passes it against the real site.

You can try it at chat.rindler.ai, or point your own agent at the hosted MCP server. If you want the mechanics first, How it works walks the pipeline from mapping to verified config, and Recruiting covers the rest of the hiring workflow.