# Connecting JobDiva > RemakeCV connects to JobDiva. Our team builds the connection from API credentials issued on your JobDiva account, so a contractor's CV is formatted once and reused across every requirement you put them forward for. Source: https://www.remakecv.com/help/integrations/jobdiva Last updated: 2026-08-22 --- RemakeCV connects to JobDiva. Our team builds the connection for your agency from API credentials issued on your JobDiva account, after which a candidate's CV is formatted into your branded template and the finished document lands back on their record — and any later reformatting of a CV you have already processed costs no further credit. Tell us you run JobDiva at support@remakecv.com. ## Where this sits on a contract desk JobDiva's centre of gravity is contract and temporary staffing — IT and professional services, largely in the US — and that work has a rhythm permanent recruitment does not. The same people come back around. A consultant who put a network engineer on site in March is submitting them again in July against a different requirement, then twice more before the year is out. Requirements are often worked by several agencies at once, so how quickly a clean, correctly presented submission reaches the client is part of what you compete on. Two things follow for CV formatting, and they pull the same way: the handling per submission has to be short, and the work done the first time has to still be there the fourth time. ## What changes on the desk 1. Recruiters and sourcers keep working candidates and requirements inside JobDiva. 2. The CV is rendered into your agency's branded template, through the ordinary editor and options. 3. The finished document returns to the candidate's record, in place for the submission. The middle step is the ordinary RemakeCV experience, so whatever your consultants already know still applies. 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). ## The second submission is the cheap one The parse is the expensive part, and you pay for it once. Every CV your team processes is listed in [CV history](https://www.remakecv.com/help/formatting-cvs/cv-history.md), scoped to the company rather than the individual and searchable by candidate name, most recent employer and most recent job title — which is how a contractor gets found again months later, when nobody remembers the filename. From an entry you can: - re-download it as DOCX or PDF - edit it further and take the updated version - regenerate it into a different template - anonymise it for a client that sifts blind None of those spends another credit. For a desk submitting the same contractors repeatedly, that is the economics worth planning around, and connecting JobDiva does not alter it. > **Warning:** Two limits apply before you rely on it. CV storage can be switched off entirely, in which case nothing is retained and there is no history to return to. Where it is on, stored CVs are deleted after your company's retention window — 30 days by default. See [GDPR and data retention](https://www.remakecv.com/help/anonymisation-and-compliance/gdpr-and-data-retention.md). ## Getting the connection built ### Tell us JobDiva is your system of record Email support@remakecv.com with your agency name and an outline of today's path from candidate record to client submission. ### Arrange API access on your JobDiva account JobDiva issues credentials to you as their customer and will set out what your account can be given. Their answer defines the boundaries of the build. ### Pass the credentials to us securely Ask us for a safe channel first. Credentials that reach candidate data want production-secret handling — never plain email, never a shared inbox. ### We implement it and enable it for your company Our team writes the connection against JobDiva's API and turns it on centrally. The controls then surface in your dashboard, with nothing for recruiters to install. > **Note:** How far the connection reaches is set by the API access granted on your JobDiva account, not by us — commonly collecting a candidate's CV, filing the branded version back against them, or working both ways. We agree that scope with you in writing before any build work starts. Whether the connection sits once at company level or with each consultant is settled in the same conversation, since it decides where permissions land. See [security and sub-processors](https://www.remakecv.com/help/anonymisation-and-compliance/security-and-subprocessors.md). ## Does the connection change the output? No. Templates, editing, anonymisation, summaries and downloads behave the same whether a CV arrived over a connection or was dropped into the browser by hand. A connection decides only the route the file takes, so adopting one never obliges you to revisit a template your clients already accept. If that template does not exist yet, it is designed alongside the connection — see [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## Building it against our API instead The live integrations list marks where we have already done the work, not the limit of what we will connect: any platform with an API is buildable, JobDiva included. Where you have engineering capacity in-house and would rather own it, the [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) gives you the processing, retrieval and template endpoints directly — see [connecting RemakeCV to any ATS or internal system](https://www.remakecv.com/help/integrations/using-the-api-instead.md). ## Which plans include it? Business and Enterprise both carry integrations — see [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). ## Start the conversation Email support@remakecv.com with **JobDiva** and your agency name. We will confirm what the connection can do on your account and what we need from you. ## Frequently asked questions ### Does RemakeCV integrate with JobDiva? Yes. Our team builds the JobDiva connection for your agency from API credentials issued on your JobDiva account, and it then behaves like the RemakeCV integrations already running elsewhere. Tell us you run JobDiva at support@remakecv.com. ### What do I need to provide? API credentials issued on your JobDiva account, which JobDiva arranges for you as their customer, plus an outline of how a contractor currently gets from a record to a client submission. Send both to support@remakecv.com and the build is ours to do. ### Will it work the same as the other integrations? Yes. The same templates, editor, anonymisation, summaries, CV history and downloads apply. A connection settles how a CV moves between two systems and nothing more — the document the client receives is identical either way. ### Can I use RemakeCV with JobDiva before the integration is set up? Yes. RemakeCV runs standalone in the browser — upload a CV, format it into your branded template and download it. Contract desks often pilot with a handful of consultants this way and connect JobDiva once the template is settled; the connection was never a prerequisite.