canonical: https://jentic.com/apis/matchmates.de/matchmates

# Matchmates De MatchMates External API

The MatchMates External API manages candidate records in a recruiting workflow. It searches candidates against criteria, creates a new candidate, fully replaces an existing candidate record, and deletes a candidate by id. It is a focused candidate-management surface for keeping an external system in sync with a MatchMates recruiting pipeline rather than a full applicant-tracking suite.

## For AI agents

Search candidate records, create new candidates, fully replace an existing candidate, and delete a candidate by id. A focused surface for syncing candidate data with a MatchMates recruiting pipeline.

## Scope

Manages candidate records only; does not post jobs, schedule interviews, or run the full hiring pipeline through this surface. Use for candidate search and record management.

## Capabilities

- Search candidate records against a set of criteria
- Create a new candidate in the recruiting pipeline
- Fully replace an existing candidate record by id
- Delete a candidate by id
- Keep an external system in sync with MatchMates candidate data

## Use cases

### Candidate sourcing for an AI agent

Give an AI agent the ability to add and find candidates in a MatchMates pipeline without hand-wiring the X-API-Key header. Through Jentic the agent discovers the candidate search and create operations by intent and calls them with a validated input schema, so a sourcing assistant can create candidate records from applications it processes and search the pipeline for existing matches before adding duplicates.

Example prompt: Search the pipeline for a candidate by email, and if none exists, create a new candidate record from the parsed application data

### Candidate data sync

Keep candidate records in MatchMates aligned with an external system by creating new candidates, fully replacing changed records, and deleting ones that are no longer relevant. This backs a nightly sync or a webhook-driven pipeline that mirrors candidate data from an applicant source into MatchMates.

Example prompt: Replace an existing candidate record with an updated version pulled from the source system and confirm the update

### Candidate search and screening

Search the candidate pool against criteria to build shortlists for a role. A screening tool can query the pipeline for candidates matching skills, location, or other attributes and hand the results to a recruiter or an agent for the next step.

Example prompt: Search for candidates matching a role's required skills and return a shortlist for a recruiter to review

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/candidates/search` | Search candidates against criteria |
| POST | `/candidates` | Create a candidate |
| PUT | `/candidates/{candidateId}` | Fully replace a candidate record |
| DELETE | `/candidates/{candidateId}` | Delete a candidate |

## Key resources

- **Candidates** — Search, create, fully replace, and delete candidate records in the recruiting pipeline

## Why Jentic

- **Setup:** Wiring the MatchMates External API by hand means setting the `X-API-Key` header on every request and coordinating search-before-create logic to avoid duplicate candidates. Through Jentic you install once, import MatchMates from the API Directory, store the key once, and your agent calls the candidate operations directly.
- **Permission scoping:** You choose the operations your agent may call, so you can allow candidate search and creation while withholding replacement and deletion. That way a sourcing assistant can grow the pipeline without the ability to overwrite or remove existing records.
- **Credential handling:** Your MatchMates API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'search candidates' or 'create a candidate', and Jentic returns the matching MatchMates operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Greenhouse** — Full applicant-tracking system with jobs, stages, and scorecards.
- **Lever** — Recruiting platform combining ATS and candidate relationship management.
- **Workable** — Hiring platform with job posting, sourcing, and candidate tracking.

## FAQ

### What authentication does the MatchMates External API use?

The MatchMates External API authenticates with an API key sent in the `X-API-Key` request header, per its OpenAPI spec. You obtain the key from your MatchMates company settings. Through Jentic the key is stored once and injected at call time, so your agent never places it in the header itself.

### What can I do with the MatchMates External API?

You can search candidate records against criteria, create a new candidate, fully replace an existing candidate record, and delete a candidate by id. It is a focused candidate-management surface for keeping an external system in sync with your MatchMates recruiting pipeline.

### Is there a MatchMates MCP server?

You do not need an MCP server to give your agent the MatchMates External API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the candidate operations on demand. Nothing extra runs, and no server tool definitions sit in the agent's context between calls.

### Can I limit what my agent is allowed to do with the MatchMates External API?

Yes. Write a rule that allows only the operations you need, such as searching and creating candidates while leaving out deletion, so the agent can grow the pipeline but cannot remove records. Every call it makes is logged, so you can audit exactly which operations ran.

### What are the rate limits for the MatchMates External API?

The OpenAPI spec does not specify rate limits. Any limits are set by MatchMates for your account, so check your MatchMates account settings or contact their support for the quota that applies to your key.

### How do I add a candidate with MatchMates through Jentic?

Search Jentic for 'create a candidate' to find the create operation, which adds a candidate record to your pipeline, and pair it with the search operation to check for an existing match first. Jentic returns each operation with its input schema so your agent calls it correctly. To run it on your own infrastructure, install Jentic One from its GitHub repo.