RemakeCV
Book a demo

Using the API instead of a native integration

If your ATS isn't natively supported, the RemakeCV public REST API lets you process CVs, list results and fetch templates from your own system.

If your ATS or internal system has no native RemakeCV integration, use the public REST API. It processes a CV from a file upload, returns a download URL for the formatted document, and lets you list stored CVs and available templates — everything a native integration does, under your own control.

When is the API the right choice?

  • Your ATS is not natively supported
  • You have an in-house recruitment system
  • You want CV formatting inside your own candidate portal
  • You are migrating a back catalogue and want to script it
  • Your workflow needs something a native integration does not do

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

    The public API is off by default. Email support@remakecv.com to enable it 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

Do I need a developer?
Yes. The API is a REST interface, so it needs someone comfortable making authenticated HTTP requests. It is a small integration by most standards — six endpoints.
Does the API cost extra?
API usage draws on the same credit pool as the web app: one credit per CV processed. The public API must be enabled for your company — email support@remakecv.com.
Is the API as capable as a native integration?
For processing, retrieval and templates, yes. Native integrations additionally handle the ATS-side user experience, which you would be building yourself.

Related articles

Was this page helpful?

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