# 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.

Source: https://www.remakecv.com/help/integrations/using-the-api-instead
Last updated: 2026-08-21

---
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](https://www.remakecv.com/help/integrations/integrations-overview.md)
- 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?

| Endpoint | Purpose |
|---|---|
| `POST /cvs/process` | Upload and format a CV, returning a download URL |
| `GET /cvs` | List stored CVs, with pagination and date filters |
| `GET /cvs/{cvId}` | Get one CV's detail |
| `GET /cvs/{cvId}/file` | Get a short-lived signed download URL |
| `GET /templates` | List templates visible to a given user |
| `GET /health` | Check the API is reachable |

Full details in the [API reference](https://www.remakecv.com/help/api-reference/introduction.md).

## What does a minimal integration look like?

### 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.

### 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](https://www.remakecv.com/help/api-reference/authentication.md).

### Process a CV

`POST /cvs/process` with the file and the acting consultant's email address. See [process a CV](https://www.remakecv.com/help/api-reference/endpoints/process-a-cv.md).

### Retrieve the formatted document

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

### 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](https://www.remakecv.com/help/api-reference/rate-limits.md) and [errors](https://www.remakecv.com/help/api-reference/errors.md).

> **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](https://www.remakecv.com/help/getting-started/credits-and-usage.md).

## 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](https://www.remakecv.com/help/api-reference/recipes/sync-to-your-ats.md) 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.