HR & People

The templates in this pack

Recruiting pipeline: applicant contact, role, and stage.

Schema

The canonical field set, printed as it ships.

7 fields with multilingual hints (DE / FR / IT / EN / ES) and field-level validators. Any source column that resolves to one of these is mapped by the cascade — most of them on the deterministic layers, with no LLM call.

candidates_v1

fields: 7
required: 2
validated: 2
hints: 34

Canonical column	Type	Required	Validators	Header hints the cascade matches
`candidate_id`	string	yes	—	bewerbernummeridentifiant candidatid candidatocandidate idid de candidato
`full_name`	string	yes	—	namenom completnome completofull namenombre completo
`email`	email	—	`email`	emaile-mailmailcorreocourriel
`phone`	phone	—	`phone`	telefontéléphonetelefonophoneteléfono
`role`	string	—	—	stelleposteruolorolepuesto
`stage`	enumappliedscreeninginterviewofferhiredrejected	—	—	phaseétapefasestageetapa
`source`	string	—	—	quellesourcefontefuente

Read the same definition as JSON at GET /v1/templates/candidates_v1. A hint match resolves on layer 2 — no LLM call, no token spend, just the flat per-map fee. Hover a validator id to see what it checks.

7 canonical fields
2 required
2 validated
34 header hints
HR & People pack

Try it

A real file, a real call, one template id.

6 rows, recruiting pipeline stages. Fully synthetic — safe to share, commit, and run in CI.

bash

curl -X POST https://api.adaptivmapr.com/v1/uploads \
  -H "Authorization: Bearer $ADAPTIVMAPR_API_KEY" \
  -F "file=@candidates_sample.csv" \
  -F "template=candidates_v1"

→ upload created · mappings ready · confirm before commit

Download candidates_sample.csv Open in Workbench →

This is a medium-risk template. Its mappings response comes back with requires_hitl: true so you can gate your own commit. Schema-only mode — headers plus at most three sample rows, each clamped to 80 characters — is a data-minimization mode. Full-data routes the metered layer-5 call in-region under a BAA at a 20% uplift, and stays locked until the workspace accepts the BAA/NDA in-app.

mcp

adaptivmapr.match_headers({
  template_id: "candidates_v1",
  headers: ["candidate_id", "full_name", "email", "phone"]
})

schema-only · headers and ≤3 clamped rows only

Put candidates in production — without shipping raw records.

Schema-only mapping leaves only headers and a handful of clamped samples. Add full-data when you need row-level AI, routed in-region under a BAA.

Full template page See pricing