# Connecting Ashby

> RemakeCV connects to Ashby two ways — our team builds and configures the integration from API credentials issued for your Ashby account, or your own engineers build it against RemakeCV's public REST API.

Source: https://www.remakecv.com/help/integrations/ashby
Last updated: 2026-08-22

---
RemakeCV connects to Ashby. Our team will build and configure the integration for your talent team using API credentials issued for your Ashby account, or your own engineers can build it against RemakeCV's public REST API — both routes end the same way, with a candidate's CV formatted into your branded template and the finished document returned to their record. Email support@remakecv.com and we will scope it with you.

## Two routes, and the second one is not a fallback

Ashby tends to be chosen by companies growing fast enough that tooling gets picked deliberately rather than inherited, and their talent teams are often more hands-on with APIs than most — reporting pulled directly, small automations written in-house, engineering help available when the case for it is good. Where that describes you, building the connection yourself is a genuine first choice: the trigger, the timing and the destination all stay in your own hands.

| | We build it | You build it |
|---|---|---|
| Who writes the connection | Our team | Your engineers |
| What you supply | API credentials for your Ashby account | Nothing beyond a RemakeCV API key, which we issue |
| Where it runs | Managed by us | Your own infrastructure, on your schedule |
| Templates and output | Identical | Identical |

Decide it on where you would rather spend engineering attention. Both are covered below.

## How the integration is set up

### Open with how your hiring actually runs

Email support@remakecv.com with your organisation name and a short picture of the current path — who prepares candidate CVs, and who reads the finished version once it exists.

### Find out what Ashby can issue you

Whoever administers Ashby in your organisation, or Ashby's own support team, decides what API credentials are available to your account and on what terms. Their answer sets what we build against.

### Hand the credentials over on a channel you trust

We will point you to one. Anything with reach into candidate data deserves production-secret handling — not plain email, and not a message thread that outlives the project.

### We implement it and switch it on

Our team builds against Ashby's API and enables the connection for your company. The relevant controls then appear in your RemakeCV dashboard, with nothing for individual recruiters to install.

> **Note:** 
Reach follows access: whatever your Ashby account permits over its API is what the connection can be built to do — collecting a candidate's CV, filing the branded version back against them, or working in both directions. We put that scope in writing with you during scoping, before any build starts, so nobody is working from an assumption.

## What the workflow looks like

With a connection running, the branded CV is produced as part of moving the candidate forward:

1. Candidates are sourced, screened and progressed in Ashby the way they already are.
2. The CV is rendered into your organisation's branded template — same template, same editor, same options as any other RemakeCV job.
3. The finished document returns to the candidate's record, where the next person to open it finds it.

Step two is untouched by the connection, so what your team already knows about RemakeCV carries straight over. See [uploading a CV](https://www.remakecv.com/help/formatting-cvs/uploading-a-cv.md) and [reviewing and editing](https://www.remakecv.com/help/formatting-cvs/reviewing-and-editing.md).

## Does the integration change the formatting?

No. Templates, editing, [auto-anonymisation](https://www.remakecv.com/help/anonymisation-and-compliance/auto-anonymisation.md), [candidate summaries](https://www.remakecv.com/help/ai-tools/candidate-summaries.md) and downloads behave the same whether a CV arrives over a connection or is dragged into the browser. The connection carries the file in and out and does nothing else, which is also why the choice of build route has no bearing on the result. If your branded template has yet to be designed, our team builds it to your organisation's brand as its own piece of work — see [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md).

## Building it yourself

The [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) is the same surface our own native integrations are built on, so nothing is held back for internal use. It is six endpoints in total: [process a CV](https://www.remakecv.com/help/api-reference/endpoints/process-a-cv.md) takes the file and returns the parsed data with a download URL, [get the CV file](https://www.remakecv.com/help/api-reference/endpoints/get-cv-file.md) issues a fresh signed URL later, and the rest cover listing stored CVs and the templates a given user can see. [Authentication](https://www.remakecv.com/help/api-reference/authentication.md) is a single key we issue for your company.

The shape most teams want — read the CV from Ashby, post it to RemakeCV, put the formatted document back on the record — is worked through end to end in [sync to your ATS](https://www.remakecv.com/help/api-reference/recipes/sync-to-your-ats.md). Credits work exactly as they do in the browser: one per CV processed, from the same company pool. Start at [connecting RemakeCV to any ATS or internal system](https://www.remakecv.com/help/integrations/using-the-api-instead.md), which covers what to build and in what order.

## Which plan includes it?

Business and Enterprise both include it — integrations are not gated behind a tier. See [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md).

## Start the conversation

Email support@remakecv.com with **Ashby**, your organisation name, and whether you would like us to build the connection or issue you an API key so your engineers can. We will confirm what the integration will do on your account and what we need from you.

## Frequently asked questions

### Does RemakeCV integrate with Ashby?

Yes. Our team builds and configures the Ashby integration for your talent team using API credentials issued for your Ashby account, and teams with engineering capacity can build it themselves against RemakeCV's public REST API instead. Email support@remakecv.com and we will scope it with you.

### What do I need to provide?

For a build by our team: API credentials issued for your Ashby account, plus a short description of how candidate CVs reach the people who read them today. If your engineers are building it, you need a RemakeCV API key instead, which our team issues for your company. Either way, start at support@remakecv.com.

### Will it work the same as the other integrations?

Yes. The same templates, editor, anonymisation, summaries and downloads apply, and that holds whether our team wrote the connection or yours did. An integration governs only how a CV travels between systems — the document itself is produced the same way every time.

### Can I use RemakeCV with Ashby before the integration is set up?

Yes. RemakeCV runs standalone in the browser — upload a CV, format it into your branded template, download it and file it wherever you need. Teams frequently work this way while they decide which build route suits them; a connection is an improvement on that, not a requirement.