Authenticate with a v3 bearer token (Authorization: Bearer YOUR_TOKEN) against https://api.manatal.com/open/v3/.
POST to /candidates/ with the candidate's required fields — at minimum first_name, last_name, and the owning organization ID — plus optional fields such as email, phone, current_position, and resume URL.
To link the candidate to a job, POST to /jobs/{job_pk}/applications/ (or the equivalent application endpoint) supplying the candidate ID returned in step 2 and the target job ID.
Optionally attach a resume file via POST to /candidates/{candidate_pk}/attachments/ using multipart/form-data.
Confirm the record via GET /candidates/{id}/ and verify the application link via GET /jobs/{job_pk}/applications/.
Known gotchas
V1 and v2 endpoints are shut down; all paths must use /open/v3/ — mixing old and new path prefixes in the same integration causes inconsistent 404 errors.
Manatal enforces duplicate-prevention logic per current docs; submitting a candidate with the same email on the same job may be blocked or flagged — check API responses for conflict codes.
Webhooks for candidate events are available but must be configured through Manatal support (support@manatal.com) for accounts that need them, as they are not self-service in the current docs.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp