ReachMee recruitment data is on a Talentech REST API

ReachMee is automatable through Talentech's published ReachMee REST API. Talentech's product page still presents ReachMee as the recruitment product that became part of Talentech in 2019, used by customers in the private and public sectors. The opened OpenAPI 3.0 document is titled ReachMee API version 1.0 and sets its server to https://api.talentech.io/reachmee. It has 34 paths under /public/v2 for projects, candidates, hires, ads, users, organization units, and roles. Those paths include GET, POST, PATCH, PUT, and DELETE. A second OpenAPI, ReachMee export API, uses https://api.talentech.io/reachmee/export and has 16 paths for ads, candidates, projects, and emails. Operations name required scopes such as reachmee-projects:read, reachmee-projects:write, reachmee-candidates:read, and reachmee-users:read. The ReachMee OpenAPI file does not itself contain a security scheme. The Talentech getting-started page says a customer or partner obtains client credentials, requests a JWT with grant_type client_credentials at https://auth.talentech.io/connect/token, and sends that token as Authorization Bearer. It says each endpoint requires the scope configured on the client. The developer home page says some APIs may cost extra. The catalog entry for reachmee-api sets subscriptionRequired to false and records the backend service URL https://api.reachmee.com/api/. The 2021 service description calls ReachMee a web-based recruitment system and places predefined API access on the Pro package and complete HRIS API access on Enterprise. It also lists an additional Excel or XML import and export service. Linköping municipality's customer story names ReachMee and does not document the API. Webcruiter is a different Talentech API. No ReachMee MCP server was established. Zapier, Make, Power Automate, and n8n were not opened. Computer-use viability is unassessed. The API scores 5 because the OpenAPI covers core recruitment records and writes, while access still depends on Talentech issuing a scoped client.

Best path today: api · Overall automatability: 5/10