Integrations & API

How CVsprings connects to recruiting workflows — what works today, and where we’re headed. Each capability is tagged so you always know what’s live versus planned. We have no ATS partnerships yet; platform names below indicate intended targets only.

TodayAvailable now

Integration today means manual upload and export:

Single & batch CV upload (PDF/DOCX) scored against a job description.
CSV export of ranked results and the full audit log.
Branded, print-to-PDF candidate reports.
Reusable role / job-description templates.

There is no programmatic API or automated ATS push/pull yet — everything below is direction, not a live capability.

Public REST APIPlanned

Authenticate with a per-org API key and call documented endpoints to submit CVs/JDs and retrieve scores, audit records, and templates — the same analysis the web app produces, programmatically.

Use case: embed CVsprings scoring into your own recruiting tooling. A draft technical specification (auth, endpoints, schemas, webhooks, limits) is available to prospects — request it via the contact below.

WebhooksPlanned

Register a callback URL and receive a signed notification when an analysis (especially a large batch) finishes, instead of polling.

Use case: trigger the next step in your workflow the moment results are ready.

Native ATS connectorsExploring

The generic pattern: your ATS pushes a new application plus the job description to CVsprings → CVsprings scores it → the score and the recruiter’s decision are written back to the ATS record, so scoring appears inside the tool your team already uses.

Platforms we intend to support (examples of common ATS targets — not existing integrations or partnerships): Greenhouse, Lever, Teamtailor, Recruitee, Personio, SmartRecruiters.

Priority follows client demand — tell us which ATS you use.

Middleware (Zapier / Make)Exploring

Once the public API exists, a Zapier/Make connector could bridge CVsprings to many tools without a bespoke integration per platform.

Use case: a lower-effort path to broad coverage while native connectors mature.

Sequencing

We commit to phases, not dates. Order reflects dependency; priority within exploration follows what clients ask for.

Public REST API + API keys Planned
Foundation for everything else.

Webhooks Planned
Analysis-complete callbacks with signed payloads.

First native ATS connector(s) Exploring
Built for the platform the most clients request.

Broader connector coverage / middleware Exploring

Request an integration / API access

Integrations are prioritised by demand. Tell us which ATS you use and what you’d like to automate — it directly informs what we build first.

API usage, once available, is subject to the same human-oversight principle as the rest of the product: scores are advisory and all hiring decisions remain with the recruiter. See the compliance page.