Book a demo
  1. Home
  2. Connectors
  3. Fortemap API

Early access

Your front end. Our recruitment backend.

The Fortemap API exposes the engine behind Fortemap: the candidate and role data model, pipelines, matching and AI parsing. Enterprise teams build the interface their people or customers need, and leave the recruitment logic to us.

Request early accessWhat the API covers
# Illustrative: parse a CV and score it against a role
POST /v1/candidates/parse
{ "file_url": "https://files.example.com/cv.pdf" }
201 { "id": "cand_8f2k", "duplicate_of": null }
POST /v1/roles/role_31x/matches
{ "candidates": ["cand_8f2k"] }
200 { "score": 84,
       "subscores": { "skills": 92, "experience": 80 },
       "validate": ["P&L scale"] }

What "headless" means here

The recruitment logic, without our screens

A headless recruitment backend is a service that stores and processes hiring data through an API, with no fixed user interface. You keep full control of design and user experience. Fortemap handles duplicate checks, parsing, candidate statuses, pipelines, matching, documents and audit history.

Use case

Your own careers site

Collect applications on a site built to your brand, with parsing, dedup and routing handled by the API.

Use case

Internal mobility portal

Let employees see and apply for roles inside your intranet or HR app, matched against their profiles.

Use case

Client-branded RPO apps

Give each client of an RPO programme its own interface, backed by one recruitment engine.

Use case

Hiring inside a larger product

Add recruitment to an HR suite, workforce platform or staffing marketplace without building an ATS.

Use case

Custom hiring manager tools

Build approval flows or feedback screens that match how your managers already work.

Use case

Data and AI services

Use resume parsing, JD parsing and match scoring as services inside your own workflows.

What the API covers

Resources available to early access customers

Paths below are illustrative. The full reference is shared with early access customers and may change before general release.

  • GET/v1/candidatesSearch and list candidates, with status and skills filters
  • POST/v1/candidates/parseCreate a structured profile from a CV, with duplicate check
  • POST/v1/roles/parseTurn a pasted job description into structured role fields
  • GET/v1/roles/{id}/pipelineCandidates by stage, with SLA state
  • PATCH/v1/applications/{id}Move a candidate between stages and record the reason
  • GET/v1/roles/{id}/identification-bucketMatches from your talent pool via System Match, free
  • POST/v1/roles/{id}/matchesAI match score, sub-scores, rationale and points to validate
  • POST/v1/documentsGenerate a dossier or report from a template
  • GET/v1/clientsClients, contacts and their roles
  • GET/v1/activityAudit and activity history for any record

What you do not have to build

The hard parts of an ATS, already solved

Duplicate detection

The same person applying twice, or sourced by two recruiters, ends up as one record.

Candidate lifecycle

Statuses with time-based rules, cross-role visibility and automatic close-out.

Matching without AI cost

System Match and the Identification Bucket run on your data before any model is called.

AI with guardrails

Fixed schemas, explainable scores, versioned runs and provider-independent routing.

Document templates

Configurable sections and branding for dossiers and reports.

Tenancy and audit

Isolated workspaces, role-based access and an activity log on every record.

Enterprise requirements

Built for security reviews

Security and data

  • Workspace isolation enforced at the database level
  • Encryption in transit and at rest
  • API keys per environment, with rotation
  • Full export of your data at any time

Operations

  • Rate limits and usage reporting
  • AI endpoints charged per operation, like the app
  • Webhooks with retries and delivery logs (coming soon)
  • Named technical contact during early access

Early access

How early access works

  1. Scoping call

    Tell us what you are building, your volumes and your security requirements.

  2. Sandbox

    You get a test workspace, API keys and the current reference.

  3. Build together

    We work with your engineers and adjust the API where your use case needs it.

  4. Go live

    Production keys, agreed limits and pricing, and ongoing support.

Questions

About the Fortemap API

What is a headless ATS?

A headless ATS provides applicant tracking features such as candidate records, pipelines and matching through an API, without a fixed user interface. Companies use it to build their own hiring experiences on a proven backend.

Is the Fortemap API generally available?

Not yet. It is in early access for enterprise teams. The standard REST API included with Fortemap is available now.

How is the Fortemap API priced?

During early access, pricing is agreed with each customer based on volumes and scope. AI endpoints are pay as you go per operation, as in Fortemap.

Can we use the API and the Fortemap app together?

That is a common request, for example a custom careers site feeding recruiters who work in Fortemap. Tell us your setup during scoping and we will confirm how it fits.

Is our data kept separate from other customers?

Yes. Each workspace is isolated at the database level, with role-based access and audit logging.

Building a hiring product or portal?

Tell us what you are building. We will reply with whether the Fortemap API fits and what early access would look like.

Request early access