RemakeCV
Book a demo

Connecting RemakeCV to any ATS or internal system

The RemakeCV public REST API lets any ATS, CRM or in-house system process CVs, list results and fetch templates — the same endpoints our own native integrations are built on.

RemakeCV connects to any ATS, CRM or internal system through its public REST API. It processes a CV from a file upload, returns the parsed candidate data and a download URL, and lets you list stored CVs and available templates. If you would rather not build it, our team builds the integration for you instead.

When is the API the right choice?

  • You want CV formatting inside your own candidate portal or careers site
  • You have an in-house recruitment system
  • You want to script a back-catalogue migration
  • Your workflow has a shape you would rather control end to end
  • You are connecting a platform we have not built a native integration for yet — though our team will happily build that for you instead, see integrations overview

What can the API do?

EndpointPurpose
POST /cvs/processUpload and format a CV, returning a download URL
GET /cvsList stored CVs, with pagination and date filters
GET /cvs/{cvId}Get one CV's detail
GET /cvs/{cvId}/fileGet a short-lived signed download URL
GET /templatesList templates visible to a given user
GET /healthCheck the API is reachable

Full details in the API reference.

What does a minimal integration look like?

  1. Get the API enabled

    Email support@remakecv.com and we will enable the API for your company and issue an API key.

  2. Store the key securely

    Treat it as a credential with access to candidate personal data. Server-side only — never in browser or mobile code. See authentication.

  3. Process a CV

    POST /cvs/process with the file and the acting consultant's email address. See process a CV.

  4. Retrieve the formatted document

    Use the download_url from the response, or fetch a fresh signed URL later with GET /cvs/{cvId}/file.

  5. Handle rate limits and errors

    Default limit is 30 requests per minute. Back off on 429, and log the request_id from every error. See rate limits and errors.

Warning:

Every request needs an acting_user_email identifying which consultant the action is on behalf of. This is not decoration — it determines which templates are visible and which credit limits apply. Pass the real consultant, not a shared service account, or per-user credit limits will not work.

How do credits work through the API?

Identically to the web app: one credit per CV processed, drawn from the same company pool, and subject to the same per-user limits. See how credits and usage work.

Can I build a two-way ATS sync?

Yes, and that is the usual shape: pull the CV from your ATS, POST it to RemakeCV, retrieve the formatted document, attach it back to the candidate record. See sync to your ATS for a worked example.

Frequently asked questions

Can RemakeCV connect to our ATS?
Yes. Either our team builds the integration for you using API credentials from your provider, or you build it yourself against the public REST API. Email support@remakecv.com to start.
Do I need a developer?
Only if you want to build it yourself. Our team can build and configure the integration for you instead. If you do build it, it is a small piece of work by most standards — six REST endpoints.
Does the API cost extra?
No. API usage draws on the same credit pool as the web app: one credit per CV processed, on every plan.

Related articles

Was this page helpful?

Last updated . Still stuck? Email support@remakecv.com or book a call.