# Connecting Eploy > RemakeCV connects to Eploy — our team builds and configures the integration using API credentials issued for your Eploy account, so a formatted CV reaches the candidate record without anyone saving a file to their desktop. Source: https://www.remakecv.com/help/integrations/eploy Last updated: 2026-08-22 --- RemakeCV connects to Eploy. Our team builds and configures the integration for your organisation using API credentials issued for your Eploy account, and from there it runs on the same footing as our other ATS integrations — a candidate's CV goes into your branded template, and the finished document comes back to their record. Email support@remakecv.com and we will scope it with you. ## How the integration is set up ### Let us know Eploy is what you run Email support@remakecv.com with your organisation name and a short account of how your recruiters work today — where candidate CVs sit, and where the branded version has to end up once it exists. ### Ask Eploy for API access on your account Raise the request with Eploy's support team. This is ordinary customer housekeeping rather than a special arrangement, and they will tell you what they can issue for your account and on what terms. ### Share the credentials with us securely We will tell you how to pass them across safely. Anything that reaches candidate data deserves the same care as a password — not a plain email, and not a thread half your office can read. ### We build the connection and switch it on Our team implements the integration against Eploy's API and enables it for your company. The relevant options then show up in your RemakeCV dashboard, with nothing for your recruiters to install or maintain. > **Note:** What the finished integration can do is governed by what Eploy's API exposes to your account — commonly pulling a candidate's CV across, putting the branded document back on their record, or both directions. We confirm exactly what yours will do when we scope it with you, before any build work starts. Connection scope is settled in the same conversation. Some of our integrations are held once for an entire company; others belong to each recruiter individually, which keeps permissions and audit trails sitting where they already sit. Which arrangement suits you depends on how your Eploy account is organised and how you would like access to be divided, so we agree it with you rather than assume it. On credential handling and candidate data more broadly, see [security and sub-processors](https://www.remakecv.com/help/anonymisation-and-compliance/security-and-subprocessors.md). ## What the workflow looks like Once the integration is running, turning a raw CV into a client-ready one stops involving your desktop at all: 1. Work the candidate in Eploy the way your team already does. 2. Their CV is formatted into your branded template, using the same editor and the same options as any other RemakeCV job. 3. The finished document lands back on the candidate record, ready to go to the client. The middle step is unchanged from what you would do in the browser — 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, anonymisation, summaries and downloads behave identically whether a CV arrived over an integration or was dragged into the browser by hand. [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 [template variants](https://www.remakecv.com/help/templates-and-branding/template-variants.md) all carry across untouched, so a CV that came from Eploy is treated exactly like one that did not — and your clients see no difference before and after. If your branded template has not been built yet, that runs alongside the integration rather than behind it: our team builds it to your own design. See [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## Building it yourself If your own developers would rather hold the connection, the [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) exposes the processing, retrieval and template endpoints directly, so you can wire RemakeCV into Eploy to your own design and on your own release schedule. See [connecting RemakeCV to any ATS or internal system](https://www.remakecv.com/help/integrations/using-the-api-instead.md) for what the endpoints cover. ## 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 **Eploy** and your organisation name. We will come back to you on what the integration will do for your account, what we need from your side, and how your recruiters will use it day to day. ## Frequently asked questions ### Does RemakeCV integrate with Eploy? Yes. Our team builds and configures the Eploy integration for your organisation using API credentials issued for your Eploy account. Once it is switched on it runs on the same footing as our other ATS integrations. Email support@remakecv.com and we will scope it with you. ### What do I need to provide? Two things: API credentials for your Eploy account, which Eploy's support team issues, and a short account of how your recruiters work today. Send both to support@remakecv.com and our team handles the build from there. ### Will it work the same as the other integrations? Yes. The same templates, editor, anonymisation, summaries and downloads apply. An integration governs how a CV moves between systems and nothing more, so the document your client receives is unchanged by it. ### Can I use RemakeCV with Eploy 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 like. The integration takes the manual saving and re-attaching out of that loop; it is never a condition of using RemakeCV.