# RemakeCV — full documentation > Every RemakeCV help article, concatenated. Generated from https://www.remakecv.com/help > Articles: 89 --- # What is RemakeCV? > RemakeCV is an AI CV formatting platform for recruitment agencies. It reformats candidate CVs into your branded template, anonymises personal details and syncs with your ATS. Source: https://www.remakecv.com/help/getting-started/what-is-remakecv Last updated: 2026-08-22 --- RemakeCV is an AI CV formatting platform built for recruitment agencies. You upload a candidate CV in PDF, DOCX or DOC, and RemakeCV extracts the content, reformats it into your agency's branded template, and returns a finished DOCX or PDF. It also anonymises candidates, writes summaries, and syncs with major ATS platforms. ## What problem does RemakeCV solve? Recruitment consultants spend a large share of every week retyping candidate CVs into an agency template. The source documents arrive in every conceivable layout — two-column designs, scanned PDFs, CVs written in the first person, CVs with the employment history in reverse order. RemakeCV automates that step. It reads the source document, works out which text is a job title, which is an employer, which is a date range and which is a bullet point, then rebuilds the whole document inside your template. ## What does RemakeCV actually do? | Capability | What it means | |---|---| | **AI formatting** | Parses PDF, DOCX and DOC files and maps the content into your agency template | | **Custom branding** | Fully custom templates — any layout, logo, font, colour and section structure your agency uses, rebuilt exactly and applied to every CV | | **Bulk formatting** | Drop in a batch of CVs and process them together | | **Auto-anonymisation** | Replaces the name with a professional headline and employers with industry descriptors, for blind hiring | | **AI summaries** | Generates a candidate profile paragraph from the CV content | | **Cover letters** | Drafts a cover message tailored to the candidate | | **ATS integrations** | Any ATS or CRM — Bullhorn, Vincere, JobAdder, Salesforce and Mercury are live, and our team builds others on request | | **Public API** | REST endpoints for processing and retrieving CVs programmatically | ## How is it different from a CV template? A template is a blank document you still have to fill in. RemakeCV does the filling in. The difference matters most on messy inputs. A scanned PDF has no machine-readable structure at all — RemakeCV runs OCR over it, then reconstructs the sections. A two-column CV has text that reads in the wrong order when copied and pasted — RemakeCV works out the intended reading order before rebuilding the document. > **Tip:** If you already have an agency CV template in Word, you do not need to redesign it. Send it to us and we rebuild it in RemakeCV exactly as it stands — typically within 24 hours. See [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## How does RemakeCV fit into your stack? RemakeCV is the formatting and presentation layer, and it is built to sit alongside the tools you already run: - **It works with your ATS, not against it.** Your ATS stays the system of record; RemakeCV connects to it and hands the finished document back. See [integrations overview](https://www.remakecv.com/help/integrations/integrations-overview.md). - **It stays faithful to the candidate's CV.** RemakeCV restructures and presents what the candidate wrote rather than authoring claims on their behalf — which is exactly what makes the output safe to send to a client. Anything you want to add is a field in the editor. - **You decide what is retained.** CV storage is a company-level setting with a retention window you control, so RemakeCV holds candidate data on your terms. See [GDPR and data retention](https://www.remakecv.com/help/anonymisation-and-compliance/gdpr-and-data-retention.md). ## Where do I start? **Quickstart** Format your first CV in about five minutes. **How formatting works** The extraction and rendering pipeline, step by step. **API reference** Build RemakeCV into your own tooling. ## Frequently asked questions ### Who is RemakeCV for? Recruitment agencies, executive search firms and in-house talent teams that send branded candidate CVs to clients. It is built around agency workflows rather than individual job seekers. ### Does RemakeCV write the CV for the candidate? No. RemakeCV reformats and restructures the CV the candidate already wrote. It can generate a summary and neutralise first-person language, but it does not invent experience that is not in the source document. ### Do I need to install anything? No. RemakeCV runs in the browser. There is also a public REST API if you want to build it into your own tooling. --- # Quickstart: format your first CV > Upload a candidate CV, choose a template, review the extracted content and download a branded DOCX or PDF — the whole loop takes about five minutes. Source: https://www.remakecv.com/help/getting-started/quickstart Last updated: 2026-08-21 --- Log in to RemakeCV, drag a candidate CV onto the upload area, and pick a template. RemakeCV extracts the content in roughly 10 to 30 seconds. Review the parsed sections in the editor, correct anything that needs it, then download the finished CV as a DOCX or PDF. ### Log in Go to [app.remakecv.com](https://app.remakecv.com) and sign in. If your agency uses two-factor authentication you will be prompted for your code — see [two-factor authentication](https://www.remakecv.com/help/account-and-billing/two-factor-authentication.md). ### Upload a CV Drag a file onto the upload area, or click to browse. RemakeCV accepts **.pdf**, **.doc** and **.docx** files. You can drop several files at once to format a batch. See [bulk formatting](https://www.remakecv.com/help/formatting-cvs/bulk-formatting.md). ### Choose a template Depending on your agency's setup, you pick the template at upload or when you generate the document. Where your agency has one template it is applied automatically; where you have variants for specific clients, choose the right one — see [template variants](https://www.remakecv.com/help/templates-and-branding/template-variants.md). ### Wait for extraction RemakeCV reads the document and pulls out contact details, work experience, education, skills and qualifications. A text-based PDF or Word file usually finishes in 10 to 30 seconds. A scanned CV runs through OCR first and takes longer. ### Review the result The editor shows every extracted section next to the original document. This is the step that matters most: a quick scan of dates, job titles and employer names means the CV your client reads is exactly the one you intended to send. Fix anything that needs correcting, and add details the candidate gave you verbally — see [adding information that wasn't on the original CV](https://www.remakecv.com/help/formatting-cvs/adding-missing-information.md). ### Apply any AI tools you need Optionally generate a [candidate summary](https://www.remakecv.com/help/ai-tools/candidate-summaries.md), [anonymise the CV](https://www.remakecv.com/help/anonymisation-and-compliance/auto-anonymisation.md) for a blind submission, or draft a [cover message](https://www.remakecv.com/help/ai-tools/cover-letter-generator.md). ### Download Download as **DOCX** if you or your client will edit the file, or **PDF** if it is going out as a final document. See [downloading as DOCX or PDF](https://www.remakecv.com/help/formatting-cvs/downloading-docx-pdf.md). ## What should I check before sending a CV to a client? Read the CV the way your client will. Before you send, confirm in about 30 seconds that: - **Dates** read the way you expect for every role, including any role that is still ongoing. - **Each role sits under the right employer**, with divisions and client names shown the way the candidate described them. - **The most recent job title** is exactly right — it is the line clients read first. - **Every section from the original** is present, in the order you want to present it. > **Tip:** Want something laid out differently — bullets moved to another role, entries reordered, a date restyled? Every field is editable in place, and reprocessing is free. See [adjusting a formatted CV](https://www.remakecv.com/help/troubleshooting/formatting-looks-wrong.md). ## What next? **Set up your team** Invite colleagues and set permissions. **Get your template built** Put your agency's brand on every CV. ## Frequently asked questions ### How long does one CV take? Text-based PDFs and Word documents typically finish in 10 to 30 seconds. Scanned or image-only PDFs take longer because they run through OCR first. ### Does uploading a CV use a credit? Yes — one credit per CV processed. Reprocessing a CV you have already formatted does not consume a second credit. ### Can I change the template after processing? Yes. You can switch template and regenerate the document without re-uploading the CV. --- # Setting up your account and team > Invite colleagues to your RemakeCV account, assign roles, arrange per-user credit limits and configure company-wide defaults. Source: https://www.remakecv.com/help/getting-started/account-setup Last updated: 2026-08-21 --- Your RemakeCV account is scoped to your company. Where self-serve user management is enabled, an administrator adds a colleague and receives a temporary password to pass on — there is no invitation email. Everyone shares the company's templates and credit pool, while formatting preferences are set per user. ## How is a RemakeCV account structured? There are two levels: | Level | What it owns | |---|---| | **Company** | Templates, branding, credit balance, integrations, API keys, company details | | **User** | Individual login, formatting preferences, optional per-user credit limit | Templates are company-owned, which is what keeps agency output consistent. **Formatting preferences — date format, section toggles, headers and footers — are per user**, so two consultants can produce different-looking output from the same template if their settings differ. Worth aligning across the team when you onboard. > **Note:** CV history is scoped to the company rather than to you individually, so colleagues can see CVs processed across the agency. ## How do I add a colleague? ### An administrator adds the user Self-serve user management is available on some plans. If you cannot see the user-management tab, email support@remakecv.com and we will add the user for you. ### Collect the temporary password RemakeCV generates a temporary password and shows it to the administrator. **No email is sent to the new user.** ### Pass it on securely Send it through a channel you trust — not plain email if you can avoid it. ### They set their own password The new user is prompted to change it on first login. > **Warning:** There is no invitation email. If a colleague is waiting for one, they will wait indefinitely — the administrator has to pass the temporary password on directly. ## What should I configure first? ### Confirm your default template Set the template most of your consultants will use day to day, so nobody has to pick one on every upload. See [template basics](https://www.remakecv.com/help/templates-and-branding/template-basics.md). ### Agree your date and section preferences These are set **per user**, not company-wide, so agree them as a team and have each consultant apply the same settings. See [date formats and sections](https://www.remakecv.com/help/templates-and-branding/date-formats-and-sections.md). ### Decide on credit limits By default the whole company draws from one pool. Per-user limits and shared pools are set up by our team — email support@remakecv.com to cap individual consultants or ring-fence credits for a team. See [credits explained](https://www.remakecv.com/help/account-and-billing/credits-explained.md). ### Have everyone turn on two-factor authentication Each user enables it on their own account — there is no company-wide switch. Candidate CVs are personal data, so this is the highest-value security step you can take. See [two-factor authentication](https://www.remakecv.com/help/account-and-billing/two-factor-authentication.md). ### Connect your ATS If you use Bullhorn, Vincere, JobAdder, Salesforce or Mercury, connecting it removes the download-and-re-upload step entirely. See [integrations overview](https://www.remakecv.com/help/integrations/integrations-overview.md). ## Can users see each other's CVs? Yes. CV history is scoped to the company, so consultants can see CVs processed across the agency rather than only their own. If that does not suit your agency's confidentiality requirements, tell us — email support@remakecv.com. ## Frequently asked questions ### Do all users share the same templates? Yes. Templates belong to the company, so every user sees the same set unless a specific template has been restricted to named users. ### Does each user get their own credits? Credits are pooled at company level. Per-user limits and shared pools can be layered on top — they are set up by our team, so email support@remakecv.com with the split you want. ### Will a new colleague get an invitation email? No. A temporary password is generated and shown to the administrator, who passes it on. The user changes it at first login. ### How do I remove someone who has left? Ask your administrator to remove them, or email support@remakecv.com. Removing a user does not delete the CVs they processed. --- # How credits and usage work > One credit formats one CV. Credits are pooled at company level and refresh each billing cycle. Reprocessing, editing and re-downloading do not consume extra credits. Source: https://www.remakecv.com/help/getting-started/credits-and-usage Last updated: 2026-08-21 --- In RemakeCV, one credit equals one CV processed. Credits sit in a shared company pool and refresh at the start of each billing cycle. Editing, anonymising, re-downloading or reprocessing a CV you have already formatted does not spend another credit — only a new upload does. ## What consumes a credit? Exactly one thing: processing a new CV. | Action | Costs a credit? | |---|---| | Uploading and processing a new CV | **Yes** — one credit | | Reprocessing a CV you already formatted | No | | Editing sections in the editor | No | | Generating an AI summary | No | | Anonymising a CV | No | | Generating a cover message | No | | Downloading as DOCX or PDF | No | | Re-downloading from CV history | No | | Switching template and regenerating | No | This is the point worth internalising: **a credit buys a candidate, not an action.** Once a CV is in the system you can work with it as much as you like. ## How many credits do I get? Your account has a monthly credit allocation set when your plan is agreed, shared across everyone at your company. Business plans are sized from seat count — 30 credits per user is the standard basis — and Enterprise allocations are sized to volume. > **Note:** Adding a user does not automatically increase your allocation. If your headcount grows, ask us to resize it — see [upgrading and adding seats](https://www.remakecv.com/help/account-and-billing/upgrading-and-downgrading.md). See [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). ## When do credits refresh? At the start of each billing cycle, not on the first of the calendar month. If your account renews on the 12th, your credits refresh on the 12th. Unused credits do not roll over between cycles on standard accounts. A small number of agencies have rollover arranged as part of their agreement — if you are not sure which applies to you, ask us. ## Can I cap individual users? Yes. Two kinds of cap can sit on top of the company balance: - **Per-user limits** — a hard cap for a named consultant, checked against their usage in the current billing cycle. - **Shared pools** — a group of users sharing an allocation between them. A per-user limit takes precedence over any pool the user also belongs to. Per-user limits and shared pools are set up by our team — email support@remakecv.com with the split you want. See [credits explained](https://www.remakecv.com/help/account-and-billing/credits-explained.md) for how they interact. > **Warning:** If a consultant sees "credit limit reached" while the company still has credits, they have hit an individual or shared-pool cap rather than the company balance. Email support@remakecv.com and our team will adjust it. ## Where can I see usage? Credit usage is logged per user, per CV, with a timestamp. Administrators can review the log to see who is consuming the pool and when — useful both for spotting an unexpected spike and for sizing your plan at renewal. ## Frequently asked questions ### How many credits does one CV use? One. A single credit covers processing that CV plus all the editing, anonymising, summarising and downloading you do with it afterwards. ### Do I lose a credit if the formatting comes out wrong? No. Reprocessing an existing CV does not deduct a credit, so you can retry without penalty. ### Do unused credits roll over? Not on standard accounts — credits refresh each cycle and unused ones lapse. Rollover is available on some agreements. If you regularly run out, you can buy top-ups yourself from the dashboard. --- # Supported file types, sizes and limits > RemakeCV accepts .pdf, .doc and .docx CVs. The API defaults to a 10MB file limit and 30 requests per minute. Scanned PDFs are handled via OCR. Source: https://www.remakecv.com/help/getting-started/supported-file-types Last updated: 2026-08-21 --- RemakeCV accepts CVs in .pdf, .doc and .docx format. Through the public API the default maximum file size is 10MB and the default rate limit is 30 requests per minute, both configurable per company. Scanned or image-only PDFs are supported and run through OCR automatically. ## Which file types are supported? | Format | Extension | Notes | |---|---|---| | PDF | `.pdf` | Both text-based and scanned/image-only | | Word (modern) | `.docx` | The most reliable input format | | Word (legacy) | `.doc` | Supported; converted before processing | DOCX is the format that produces the most consistent results, because the document carries real structural information — headings are headings, tables are tables. A PDF has to be reconstructed from positioned text. ## What are the size and rate limits? | Limit | Default | Configurable? | |---|---|---| | Maximum file size (public API) | 10MB | Yes, per company | | API requests per minute | 30 | Yes, per company | | Concurrent uploads in a bulk batch | 5 processed at a time | No | If you routinely handle CVs above 10MB — usually portfolios with embedded images — email support@remakecv.com and we will raise the cap on your account. ## How are text and scanned CVs handled differently? RemakeCV reports a `processing_method` for every CV: - **`text`** — the document had an extractable text layer. Fastest and most accurate. - **`image`** — no usable text layer, so the pages were run through OCR first. Scanned CVs take noticeably longer and are more prone to small character errors, so they are worth reviewing more carefully. See [scanned PDFs and OCR](https://www.remakecv.com/help/troubleshooting/scanned-pdfs-and-ocr.md). > **Tip:** If a candidate sends a scanned CV and you can ask for a Word version, do. It processes faster and more accurately than any OCR pass. If a file will not upload at all, see [upload failed or timed out](https://www.remakecv.com/help/troubleshooting/upload-failed.md). ## What about password-protected files? RemakeCV cannot open a password-protected or permission-restricted PDF. Remove the protection before uploading — in most PDF readers this means opening the file with the password and re-saving it without one. ## Frequently asked questions ### Can RemakeCV read a scanned PDF? Yes. If a PDF has no extractable text layer, RemakeCV runs OCR over the pages and reconstructs the content from the recognised text. It takes longer than a text-based file. ### Does RemakeCV accept .txt or .rtf files? The formatting pipeline is built around .pdf, .doc and .docx. Other formats are not officially supported — convert to DOCX or PDF first. ### What is the largest CV I can upload? Through the public API the default cap is 10MB per file, and it can be raised for your company. Most CVs are well under 1MB. --- # Uploading a CV > Drag and drop a candidate CV into RemakeCV, or send it straight from your ATS — Bullhorn, Vincere, JobAdder, Salesforce, Mercury and other platforms we integrate with — without leaving your workflow. Source: https://www.remakecv.com/help/formatting-cvs/uploading-a-cv Last updated: 2026-08-22 --- Drag a .pdf, .doc or .docx file onto the upload area in RemakeCV, or click to browse. Choose a template, and processing starts immediately. If your ATS is connected you can pull a CV directly from a candidate record instead of downloading and re-uploading it. ## How do I upload a CV? ### Open the upload area The upload area is the first thing on the dashboard. You can drag files onto it from your desktop, or click it to open a file browser. ### Select the file RemakeCV accepts `.pdf`, `.doc` and `.docx`. There is no file size limit in the web app. See [supported file types](https://www.remakecv.com/help/getting-started/supported-file-types.md). ### Choose a template Depending on your agency's setup, the template is selected either at upload or when you generate the document. Where a default is set, it is pre-selected either way. ### Wait for processing A text-based file typically completes in 10 to 30 seconds. Scanned PDFs take longer because they run through OCR. ## Can I upload from my ATS instead? Yes, and it is worth setting up. With an integration connected, you open the candidate record in your ATS, send the CV to RemakeCV, and the formatted document comes back — no downloading to your desktop and re-uploading. Supported: [Bullhorn](https://www.remakecv.com/help/integrations/bullhorn.md), [Vincere](https://www.remakecv.com/help/integrations/vincere.md), [JobAdder](https://www.remakecv.com/help/integrations/jobadder.md), [Salesforce](https://www.remakecv.com/help/integrations/salesforce.md) and [Mercury](https://www.remakecv.com/help/integrations/mercury.md). ## What happens during the upload? Three things, in order: 1. **Text extraction.** RemakeCV pulls the raw text out of the document. If the file has no text layer, it runs OCR over the pages instead. 2. **Structured parsing.** The AI works out which text is a job title, an employer, a date range, a bullet point, a qualification, a skill. 3. **Rendering.** The structured data is written into your template. [How AI formatting works](https://www.remakecv.com/help/formatting-cvs/how-ai-formatting-works.md) covers each stage in more detail. > **Tip:** The quality of the output tracks the quality of the input. A clean single-column Word CV gives near-perfect results. A scanned two-column design is where you should expect to do some reviewing. > **Note:** Turning on the side-by-side original-CV view is convenient, but it also means the candidate's source file is stored on our servers. Worth knowing if your agency runs a strict retention posture — see [GDPR and data retention](https://www.remakecv.com/help/anonymisation-and-compliance/gdpr-and-data-retention.md). ## What if the upload fails? The common causes are a password-protected PDF, an unsupported file type, a file over the size limit, or a corrupted document. See [upload failed](https://www.remakecv.com/help/troubleshooting/upload-failed.md). ## Frequently asked questions ### Can I upload more than one CV at a time? Yes. Drop multiple files onto the upload area and RemakeCV queues them, processing five at a time. See bulk formatting. ### Can I upload directly from my ATS? Yes, if your ATS is connected. Integrations including Bullhorn, Vincere, JobAdder, Salesforce and Mercury remove the manual download step, and our team builds integrations for other platforms on request. ### What happens to the original file? It depends on two settings: your company's CV storage setting, and your own 'display original CV' preference — enabling the side-by-side original view also stores the candidate's file on our servers. See GDPR and data retention. --- # How RemakeCV's AI formatting works > RemakeCV extracts text from the CV, uses AI to identify roles, employers, dates and bullets as structured data, then renders that data into your agency template. Source: https://www.remakecv.com/help/formatting-cvs/how-ai-formatting-works Last updated: 2026-08-22 --- RemakeCV formats a CV in three stages. First it extracts raw text from the document, using OCR when there is no text layer. Then an AI model parses that text into structured fields — employers, job titles, date ranges, bullet points, education, skills. Finally those fields are rendered into your agency's template. ## Stage 1: text extraction RemakeCV first has to turn a document into text. - **DOCX and DOC** carry real structure — the paragraphs, tables and headings are all machine-readable. This is the most reliable input. - **Text-based PDFs** have a text layer, but no structure. The text has to be reassembled from positioned fragments, which is why column order can be ambiguous. - **Scanned PDFs** have no text at all. RemakeCV runs optical character recognition over the page images and works from the recognised text. The CV records which path it took as `processing_method`: `text` or `image`. ## Stage 2: structured parsing This is where the real work happens. The extracted text is a flat wall of words; the AI's job is to decide what each part *is*. For each role it identifies the employer, the job title, the location, the date range, and the bullet points that belong to that role. It does the same for education, qualifications, certifications and skills. Two problems make this genuinely hard: - **Attribution.** When a candidate has held three roles at the same employer, the bullets under the second role must not be attached to the first. When a CV lists a client name next to an employer, the employer must win. - **Reading order.** In a two-column layout, naive extraction interleaves the columns. The parser has to recover the order a human would read. > **Note:** The parser preserves the candidate's wording. It decides where text goes, not what it says. If you want the language changed, that is a separate opt-in step — see [first-person neutralisation](https://www.remakecv.com/help/anonymisation-and-compliance/first-person-neutralisation.md). ## Stage 3: rendering into your template The structured data is written into your agency template — your fonts, your colours, your section order, your headings, your date format. Because the data is structured rather than copied, the same candidate renders identically into any template you own. This is also why switching template is cheap: the parse is already done, so regenerating into a different template costs nothing and does not consume a credit. ## How does it handle difficult source documents? Real candidate CVs arrive in every possible shape, and the pipeline is built for that rather than for tidy inputs: | Source | How RemakeCV handles it | |---|---| | Two-column and sidebar layouts | Re-read in the order a person would read them, before parsing | | Scanned and photographed documents | Recognised page by page, including names held in header graphics | | Several roles at one employer | Each role's bullets attributed to the role they belong to | | Non-standard date formats | Normalised so dates read consistently across the whole CV | | Unusual section headings | Matched to the section they correspond to | | Continuous-scroll exports from Canva or Notion | Sliced, read and stitched back together | Anything you do want to adjust is a click in the editor — see [reviewing and editing](https://www.remakecv.com/help/formatting-cvs/reviewing-and-editing.md) — and reprocessing never costs a credit. ## What the pipeline guarantees These are hard constraints in the pipeline, not tendencies — and they are what makes the output safe to put in front of a client: - **No invented content.** Employment history, dates and qualifications come from the source CV and nowhere else. - **No silent removal.** Content is only dropped when you ask for anonymisation. - **No meaning drift.** A bullet point is moved, never reworded, unless you opt into a feature that rewrites. Anything you want to add or change is available in the editor — see [adjusting a formatted CV](https://www.remakecv.com/help/troubleshooting/formatting-looks-wrong.md). ## Frequently asked questions ### Does the AI rewrite the candidate's words? No. The extraction step preserves the candidate's own wording. Bullet points are moved, not rewritten. The only features that generate new text are the candidate summary, the cover message and first-person neutralisation, and each is opt-in. ### Which AI model does RemakeCV use? RemakeCV runs on OpenAI's models under an enterprise agreement with zero data retention. Candidate data is not retained by OpenAI after processing and is never used to train models. EU data residency is available on request. ### Is my candidate data used to train AI models? No. RemakeCV's enterprise agreement with OpenAI carries zero data retention: candidate CVs are processed to produce your formatted document, are not retained afterwards, and are never used to train models. See security and sub-processors. --- # Bulk formatting multiple CVs > Drop a batch of CVs onto RemakeCV and they queue automatically, processing five at a time. Each CV costs one credit and can be reviewed individually. Source: https://www.remakecv.com/help/formatting-cvs/bulk-formatting Last updated: 2026-08-21 --- Drag several CVs onto the upload area at once. RemakeCV queues the whole batch and processes five files concurrently, starting the next as each one finishes. Every CV consumes one credit and lands in your CV history, where you can review and download each one individually. ## How do I format a batch of CVs? ### Select multiple files Drag several CVs onto the upload area together, or select several in the file browser. Mixed formats are fine — a batch can contain PDFs and Word files side by side. ### Choose one template for the batch The whole batch renders into the same template. If some CVs need a different one, run them separately or switch template afterwards. ### Let the queue run RemakeCV processes five CVs at a time and starts the next as soon as a slot frees. You can watch each file's status as it moves through the queue. ### Review each CV Bulk processing does not mean bulk trust. Open each result and check dates, employers and job titles before anything goes to a client. ## How long does a batch take? Roughly: `(number of CVs ÷ 5) × time per CV`. A text-based CV takes 10–30 seconds, so 20 clean CVs finish in around two minutes. A batch of scanned PDFs takes substantially longer, because every file runs through OCR first. ## What does a batch cost? One credit per CV, exactly as with single uploads. Nothing about batching changes the price. Credits are checked file by file rather than up front. If you have 5 credits left and queue 10 CVs, the first 5 process and the rest stop with a credit error — you do not lose the batch, and you do not get charged for the ones that did not run. > **Warning:** If a consultant hits "credit limit reached" partway through a batch while the company clearly has credits available, they have hit an individual or shared-pool cap. See [credits explained](https://www.remakecv.com/help/account-and-billing/credits-explained.md). ## When is bulk formatting the right tool? It suits the situations agencies actually hit: - **A shortlist for one client** — several candidates, one template, sent together. - **A backlog migration** — reformatting existing candidates into a new agency template. - **A new client's first submission** — where consistency across the set matters more than any individual document. For a single urgent CV, single upload is simpler; the queue adds nothing. ## Can I bulk format through the API? Yes. The public API processes one CV per request, so batching is a matter of looping with respect for the rate limit — 30 requests per minute by default. See [process a CV](https://www.remakecv.com/help/api-reference/endpoints/process-a-cv.md) and [rate limits](https://www.remakecv.com/help/api-reference/rate-limits.md). ## Frequently asked questions ### How many CVs can I upload at once? There is no fixed cap on the number of files in a batch. RemakeCV processes five concurrently and queues the rest, so a large batch simply takes longer. ### What happens if I run out of credits mid-batch? Credits are checked per file rather than per batch, so processing stops at the point the pool is exhausted. Already-processed CVs are unaffected. ### Can I use different templates for different CVs in a batch? A batch uses one template. Process in separate batches if you need different templates, or switch template afterwards on individual CVs — that does not cost a credit. --- # Reviewing and editing a parsed CV > Every extracted section can be edited before download — job titles, employers, dates, bullet points, skills and education — with the original document alongside for comparison. Source: https://www.remakecv.com/help/formatting-cvs/reviewing-and-editing Last updated: 2026-08-21 --- After processing, RemakeCV shows every extracted section in an editor. You can correct any field, reorder or delete entries and bullet points, and add content. If you have the original-CV preview enabled, the source document sits alongside for comparison. Edits do not consume credits. ## What should I check first? Work top-down and check the fields a client reads first: ### Candidate name and contact details Especially on scanned CVs, where names in header graphics are the most common OCR casualty. ### The most recent job title and employer This is the line a client scans before anything else. Confirm a client name or division has not been picked up as the employer. ### Date ranges Check for roles that should be open-ended, unusual date formats, and any range that looks implausible. ### Bullet attribution Where a candidate held several roles at one employer, confirm each set of bullets sits under the right role. ### Section completeness Compare against the original: is every section from the source present in the output? ## What can I edit? Everything the parser produced: | Section | Editable | |---|---| | Contact details | Name, email, phone, location | | Profile / summary | Free text, or AI-generated | | Work experience | Employer, title, location, dates, bullet points; reorder and delete entries | | Education | Institution, qualification, dates | | Qualifications and certifications | Name, body, date | | Skills | Categories and individual items | | Additional sections | Custom sections defined by your template | Which of these you see depends on your template — not every agency has qualifications, certifications or personal-details sections enabled. ## Can I add content that wasn't in the CV? Yes — details you gathered on a call, expected salary, notice period, right-to-work status, your own notes for the client. See [adding information that wasn't on the original CV](https://www.remakecv.com/help/formatting-cvs/adding-missing-information.md). > **Tip:** If a CV needs heavy correction across many sections, reprocessing is often faster than editing — and it does not cost a credit. Parsing is not deterministic in the trivial sense, so a second pass sometimes resolves an ambiguous layout. If it comes back the same way, see [the formatted CV looks wrong](https://www.remakecv.com/help/troubleshooting/formatting-looks-wrong.md). ## Does editing change the original file? No. The original document is untouched. The editor works on the structured data extracted from it, and the download is generated fresh from that data each time. ## Frequently asked questions ### Do edits cost credits? No. A credit covers processing the CV. Editing, regenerating and re-downloading are all free after that. ### Can I see the original CV while editing? If the original-CV preview is enabled on your account. It is a per-user setting, so a colleague may see the source pane when you do not. Note that enabling it stores the candidate's original file on our servers. ### Can I reorder work experience entries? Yes — entries and bullet points can be dragged into a different order, and individual entries removed if a role is not relevant. The order of the sections themselves comes from your template. --- # Checking what was extracted > The CV Comparison Tool highlights text in the original document that did not make it into the formatted output, so you can spot omissions before sending a CV. Source: https://www.remakecv.com/help/formatting-cvs/checking-the-extraction Last updated: 2026-08-22 --- RemakeCV's CV Comparison Tool shows the original CV side by side with the formatted output, highlighting anything that did not carry across. It is a one-glance confidence check before a CV goes to a client — particularly useful on scanned and design-heavy source documents — and corrections are made in the editor alongside it. ## What does it show? The original document, with highlighting over any text that does **not** appear in the formatted output. It answers one question quickly: *did anything get dropped?* That matters because a wrong date is visible at a glance, whereas a paragraph you have never seen is not. Comparing against the source closes that gap in seconds, and gives you something to stand behind when the CV goes to a client. > **Note:** The comparison view is for reviewing rather than editing: select and copy text freely, and make any changes in the editor alongside it, where every field is available. ## How should I read the highlights? Not every highlight is a problem. Text is legitimately dropped when it is page furniture rather than content. | Highlighted | Usually means | |---|---| | A bullet point or paragraph of real content | **Genuine omission** — add it in the editor | | A section heading you expected to see | The section may not have been recognised | | Page numbers, headers, footers | Normal — deliberately not carried over | | Decorative or template text from the candidate's design | Normal | | Scattered fragments across a scanned CV | OCR differences, not necessarily omissions | The workflow is: scan the highlights, ignore the furniture, and act on anything that is substantive content. ## Why are scanned CVs noisier? On an image-based CV the comparison runs against OCR-recognised text rather than a clean text layer, so small character-level differences register as mismatches even where the content did make it into the output. Expect more highlights and weight them more loosely. See [scanned PDFs and OCR](https://www.remakecv.com/help/troubleshooting/scanned-pdfs-and-ocr.md). ## What do I do about a real omission? ### Add it in the editor Faster than reprocessing for one or two missing items. See [reviewing and editing](https://www.remakecv.com/help/formatting-cvs/reviewing-and-editing.md). ### Reprocess if a whole section is missing Free, and a second pass sometimes resolves an ambiguous layout differently. See [the formatted CV looks wrong](https://www.remakecv.com/help/troubleshooting/formatting-looks-wrong.md). ### Report a recurring pattern If the same kind of content is dropped across many CVs, that is something we can fix in the pipeline. Email support@remakecv.com with the source file. ## When is it worth using? Every time on a scanned CV, and whenever a candidate is going to an important client. On a clean single-column Word CV the extraction is reliable enough that a normal read-through of the editor is usually sufficient. ## Frequently asked questions ### Can I edit or mark text in the comparison view? The comparison view is for reviewing; corrections are made in the editor alongside it, where every field is editable. You can select and copy text from the comparison view as you go. ### Does a highlight always mean something is wrong? No. Page furniture, headers, footers and decorative text are legitimately dropped. Highlights are a prompt to look, not a defect list. ### Why are there more highlights on a scanned CV? The comparison runs against OCR-recognised text, which introduces small differences that read as mismatches even when the content did make it across. --- # Adding information that wasn't on the original CV > Add expected salary, notice period, right-to-work status, recruiter contact details or your own notes to a candidate CV before sending it to a client. Source: https://www.remakecv.com/help/formatting-cvs/adding-missing-information Last updated: 2026-08-21 --- Anything you learned about a candidate outside their CV can be added in the RemakeCV editor before download. Common additions are expected salary, notice period, availability, right-to-work status, the consultant's own contact details and a note for the client. These fields can be built into your template so they appear in the same place every time. ## What do agencies usually add? The information that wins placements is rarely on the CV. It comes out of the screening call. | Field | Why clients want it | |---|---| | Expected salary | Filters out mismatches before an interview is arranged | | Notice period / availability | Determines whether the candidate fits the start date | | Right to work / visa status | A hard gate on many roles | | Location and willingness to relocate | Increasingly decisive for hybrid roles | | Reason for leaving | Context a CV never gives | | Consultant name and contact | So the client knows who to call | | Client-facing note | Your pitch for why this candidate fits *this* role | ## How do I add them? Open the CV in the editor and add the values to the relevant fields. If your template includes dedicated slots for them, they are already there waiting — you are filling in a form, not designing a layout. > **Tip:** If you find yourself typing the same field into every CV, it belongs in your template. Email support@remakecv.com and we will add it — see [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## Can I add a whole extra section? Yes. Additional sections — references, project portfolios, publications, security clearance — can be added per CV in the editor, or built into your template so they appear every time. ## Reprocess first, then add Reprocessing re-runs extraction against the source document. It has no knowledge of anything you typed by hand, so manual additions do not survive it. The practical order is: ### Process the CV Upload and let the AI extract. ### Fix any structural problems If the parse is wrong, reprocess or correct it now — before you invest typing time. ### Add your own information Salary, notice period, notes, consultant details. ### Download Generate the final DOCX or PDF. ## Does adding information cost a credit? No. Everything after the initial processing step is free — see [how credits and usage work](https://www.remakecv.com/help/getting-started/credits-and-usage.md). ## Frequently asked questions ### Can custom fields appear on every CV automatically? Yes. Fields such as expected salary or consultant contact details can be built into your template so they render in a fixed place on every CV, ready for you to fill in. ### Will added information survive if I reprocess the CV? Reprocessing re-runs extraction from the source document. Anything you typed manually is not in the source, so add it after your final reprocess rather than before. ### Can I add a section that isn't in my template? Additional sections can be added in the editor. If you want a section on every CV permanently, ask us to add it to your template instead. --- # Cover pages and additional candidate info > Add a branded cover page carrying your logo, the consultant's details, a candidate summary and role-specific information ahead of the CV itself. Source: https://www.remakecv.com/help/formatting-cvs/cover-pages Last updated: 2026-08-21 --- In RemakeCV, a cover page is the branded first page ahead of the candidate's CV, carrying your logo, consultant details, a candidate summary and commercial facts such as salary and notice period. Whether one is included is usually your own setting, so you can turn it on or off per submission. ## What goes on a cover page? The purpose is to give the hiring manager everything they need to decide whether to read the CV. - **Agency branding** — logo, colours, and any compliance footer you need. - **Candidate summary** — three to five lines on who this person is and why they fit. See [candidate summaries](https://www.remakecv.com/help/ai-tools/candidate-summaries.md). - **Commercial facts** — expected salary, notice period, availability, location, right to work. - **Consultant details** — name, phone, email, so the client can respond immediately. - **Role reference** — the vacancy or client reference this submission relates to. > **Note:** Cover pages are especially valuable for anonymised submissions. When the candidate's identity is removed from the CV, the cover page is where you carry the reasoning about fit that would otherwise be lost. ## How do I turn one on? For most agencies, **including a cover page is a setting on your own account** — look for the cover-page option in your settings, alongside font and display preferences. Turn it on and the cover page fields appear in the editor for you to fill in per candidate. What the cover page *contains* is defined by your template. If it is missing fields you need, email support@remakecv.com. > **Note:** Because this is a per-user setting rather than a company one, colleagues may have it on when you have it off. If a client complains that submissions are inconsistent, this is a likely cause. ## Can I have a cover page for some clients and not others? Yes. Because inclusion is a setting you control, you can turn it off for a client who wants the CV alone. For a genuinely different cover-page *design* per client, use a [template variant](https://www.remakecv.com/help/templates-and-branding/template-variants.md). ## What if a client wants their own logo on it? Client-branded variants are a common request: your candidate formatting, the client's branding. This is set up as a separate template variant. See [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## Frequently asked questions ### How do I turn the cover page on or off? For most agencies it is a setting on your own account, alongside your font and display preferences. Because it is per user, colleagues may have it set differently from you. ### What if the cover page is missing a field I need? The content of the cover page comes from your template. Email support@remakecv.com with the field you need and where it should sit. ### Can the cover page summary be AI-generated? Yes. The candidate summary can be generated from the CV content and then edited before download. --- # Downloading as DOCX or PDF > Download the formatted CV as an editable Word document or a fixed PDF. DOCX suits internal edits and client tweaks; PDF suits final submissions. Source: https://www.remakecv.com/help/formatting-cvs/downloading-docx-pdf Last updated: 2026-08-21 --- Once you are happy with the CV, download it from RemakeCV as DOCX or PDF. Choose DOCX when you or the client may still edit the document, and PDF when it is the final version and the layout must not shift. Downloading does not consume a credit, and you can download the same CV as many times as you need. ## Which format should I choose? | | DOCX | PDF | |---|---|---| | **Best for** | Internal edits, clients who want an editable file, further tailoring per role | Final client submissions, uploads into client portals, anonymised CVs | | **Trade-off** | Layout can shift depending on the reader's Word version and installed fonts | Cannot be edited after download without a PDF editor | | **Fonts** | Uses whatever is installed on the reader's machine | Embedded, so it looks identical everywhere | | **Metadata** | Carries document properties and revision data | Dropped on export | The short version: **PDF unless someone needs to edit it.** > **Tip:** For anonymised submissions, always send PDF. A DOCX carries document metadata and revision information that a PDF export drops — which matters when the whole point is that the candidate cannot be identified. ## Why does my DOCX look different in Word? Almost always fonts. If your template uses a font that is not installed on the machine opening the file, Word substitutes another one, and spacing shifts. Two fixes: - Send PDF instead, which embeds the fonts. - Ask us to build your template on fonts that ship with Microsoft Office. See [the downloaded DOCX won't open correctly](https://www.remakecv.com/help/troubleshooting/docx-wont-open.md). ## Can I download in a different template? Yes. Switch the template and regenerate — the CV does not need re-uploading and no credit is consumed, because the parse has already been done. ## Where do downloads go afterwards? If your company has CV storage enabled, the formatted CV stays in your [CV history](https://www.remakecv.com/help/formatting-cvs/cv-history.md) and can be re-downloaded at any time. If storage is disabled, the file is not retained after your session — download it before you leave the page. ## Frequently asked questions ### Should I send clients DOCX or PDF? PDF for final submissions, because the layout is fixed on every device. DOCX when the client has asked for an editable file, or when you expect to make further changes. ### Does downloading use a credit? No. Downloading and re-downloading are free. Only processing a new CV consumes a credit. ### Can I download the same CV again later? Yes, from CV history — as long as your company has CV storage enabled. --- # CV history and re-downloading > Every processed CV is listed in your history with the candidate name, latest employer and role, so you can find and re-download it without spending another credit. Source: https://www.remakecv.com/help/formatting-cvs/cv-history Last updated: 2026-08-21 --- RemakeCV's CV history lists the CVs processed across your company — not just your own — with the candidate name, latest employer and role, who uploaded it and when. Reopening an entry to re-download or edit it costs no credit. History exists only where CV storage is enabled, and entries are deleted automatically after your retention window. ## What is shown in history? Each entry records: | Column | Description | |---|---| | Date processed | When the CV was first run | | Uploaded by | Which consultant processed it | | Type | New, or a reprocess of an existing CV | | Method | Text or Image, depending on whether OCR was needed | | Candidate name | Extracted from the CV | | Latest company | The candidate's most recent employer | | Latest role | The candidate's most recent job title | | Last updated | When it was last edited | > **Warning:** History is scoped to your **company**, not to you. Consultants can see and filter CVs processed by colleagues, including who uploaded each one. If that does not suit your confidentiality requirements, tell us at support@remakecv.com. Those first three fields exist precisely because "Smith_CV_final_v2.pdf" is useless six weeks later. Searching by employer or role is how consultants actually find a candidate again. ## What can I do with a past CV? - **Re-download** it in DOCX or PDF. - **Regenerate** it into a different template. - **Edit** it further and download the updated version. - **Anonymise** it for a blind submission to a different client. None of these consume a credit. The credit was spent when the CV was first processed. > **Note:** Regenerating an old CV into a new template is the fastest way to migrate a back catalogue after a rebrand — no re-uploading, no credits. ## How long does history last? Two limits apply: - **CV storage can be off entirely.** Some agencies turn it off so no candidate document is retained after processing. There is then no history at all — download the CV before you close the session. - **Stored CVs expire.** Where storage is on, entries are deleted automatically after your company's retention window, which defaults to **30 days**. > **Warning:** Reprocessing a CV **replaces** the stored original file. The previous version is not kept. See [GDPR and data retention](https://www.remakecv.com/help/anonymisation-and-compliance/gdpr-and-data-retention.md). ## Can I get history programmatically? Yes: - `GET /cvs` — [list stored CVs](https://www.remakecv.com/help/api-reference/endpoints/list-cvs.md), with pagination and date filters - `GET /cvs/{cvId}` — [get one CV's detail](https://www.remakecv.com/help/api-reference/endpoints/get-cv.md) - `GET /cvs/{cvId}/file` — [get a signed download URL](https://www.remakecv.com/help/api-reference/endpoints/get-cv-file.md) ## Frequently asked questions ### How long are CVs kept? Stored CVs are deleted automatically after a per-company retention window, which defaults to 30 days. Anything you need to keep should be downloaded or filed in your ATS. ### Can I see CVs processed by colleagues? Yes. History is company-scoped and shows who uploaded each CV, so consultants can see each other's work. ### Can I access my history through the API? Yes. GET /cvs lists stored CVs with pagination and date filters. See list stored CVs. --- # Template basics > A RemakeCV template is a fully custom reproduction of your agency's CV design — any layout, font, colour, logo, section order and heading — applied automatically to every CV you process. Source: https://www.remakecv.com/help/templates-and-branding/template-basics Last updated: 2026-08-22 --- A RemakeCV template is your agency's CV design, reproduced exactly and held as a reusable layout. It is fully customisable — any layout, font, colour, logo placement, section order, heading and custom field — and there is no house style you have to work within. Templates belong to the company rather than the user, so every consultant produces an identical document from the same candidate. ## What does a template control? | Element | Examples | |---|---| | Branding | Logo, brand colours, footer text, compliance wording | | Typography | Heading and body fonts, sizes, weights | | Structure | Section order, which sections appear, section headings | | Formatting | Bullet styling, spacing, margins | | Custom fields | Expected salary, notice period, consultant details | | Cover page | Whether one is available and what it carries | Date style is handled a level earlier, in how your CVs are read rather than how they are rendered — see [section order, headings and how dates appear](https://www.remakecv.com/help/templates-and-branding/date-formats-and-sections.md). ## Why do templates live at company level? Because the value of an agency template is consistency. The layout, section structure and branding are shared, so a client receiving three candidates from you receives three documents that look like they came from the same agency. > **Note:** A few conveniences are stored per login rather than per company — font choice, whether a cover page is included, and whether the original CV is shown alongside the editor — so consultants can adapt to a particular client without touching the shared template. Agree these once as a team and everyone's output matches; if you would rather they were locked to a company-wide value, ask us and we will fix them at template level. What is per-CV is content: every field can be edited on an individual candidate without touching the template. ## What is a default template? Where your agency has several templates, one is marked as the default and pre-selected, so consultants do not have to choose every time. It cannot be deleted while it is the default. > **Tip:** If most of your submissions go to one client, make that client's variant the default rather than the generic house template. Defaults should reflect what you actually send most. The template is applied when you generate the document, not when you upload — so you can switch and regenerate at any point without reprocessing. See [downloading as DOCX or PDF](https://www.remakecv.com/help/formatting-cvs/downloading-docx-pdf.md). ## Can templates be restricted to certain users? Yes. Template visibility is scoped to the teams that need it, so a variant built for one client account is not visible to consultants who do not work it. This matters when a client-branded template must never accidentally go to a different client — tell us which templates and which teams, and we will configure it. Day-to-day settings live in the [template editor](https://www.remakecv.com/help/templates-and-branding/template-editor.md), and branding assets are covered in [logos, fonts and colours](https://www.remakecv.com/help/templates-and-branding/logos-fonts-colours.md). ## How do I get a template built? Send us the Word document you use today. We rebuild it as a RemakeCV template — typically within 24 hours — so the output matches what your clients already recognise, down to the detail. There is no design system to conform to and no limit on how bespoke it can be. See [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## Frequently asked questions ### How many templates can I have? There is no fixed limit. Agencies commonly run one house template plus a variant per major client. ### Can I switch a CV to a different template after processing? Yes, and it does not cost a credit. The extraction has already happened, so regenerating into another template is instant. ### Can I edit a template myself? Yes. The template editor covers fonts, margins, bullet styling, section order, headings, logos, colours and cover pages, and admin users at your agency can change any of it. Our team will also make any change for you on request. See using the template editor. --- # Requesting a custom branded template > Send us your existing agency CV template and we rebuild it inside RemakeCV — fully custom, typically within 24 hours — so every formatted CV matches the document your clients already recognise. Source: https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template Last updated: 2026-08-22 --- Email your existing agency CV template — ideally a Word document plus one or two completed example CVs — to support@remakecv.com. Our team rebuilds it as a fully custom RemakeCV template, typically within 24 hours, sends you a sample for review, and applies your corrections before making it live for your whole company. There is no design system to conform to and no limit on how bespoke the layout can be. ## What should I send? ### Your template as a Word document The `.docx` you use today. A Word file tells us far more than a PDF, because we can see the actual styles, spacing and table structure rather than guessing from a picture. ### One or two completed example CVs A blank template shows the design; a filled-in CV shows the intent. Examples answer the questions a blank file cannot — how you handle a candidate with ten roles, what happens when a job title runs onto two lines, how you show current roles. ### Your logo High-resolution PNG with a transparent background, or SVG. See [logos, fonts and colours](https://www.remakecv.com/help/templates-and-branding/logos-fonts-colours.md). ### Any rules that aren't visible in the file Things like "we always show duration in years and months", "we never include the candidate's address", "the profile section must be third person". These are cheap to build in up front and tedious to retrofit. ## What happens next? 1. **We build it.** Our team reproduces your template inside RemakeCV. 2. **You review a sample.** We send a real CV rendered in the new template. 3. **You mark up corrections.** Spacing, wording, ordering — whatever is not right. 4. **We apply and go live.** The template becomes available to your whole company. > **Note:** Review the sample against a *difficult* CV, not an easy one. A candidate with fifteen years of history, several roles at one employer and a long skills list will expose layout problems that a two-page graduate CV never will. ## What if I don't have a template yet? Tell us what you want and we will design one. It is worth having a view on: - Whether you want a [cover page](https://www.remakecv.com/help/formatting-cvs/cover-pages.md) - Whether CVs are anonymised by default - Which sections you always want, and in what order - What custom fields you need — expected salary, notice period, consultant details ## Can I get a client-branded version? Yes, and it is a common request — many clients require submissions in their own template. We reproduce the client's design as a variant alongside your house template, and scope it so the team working that account sees it. There is no limit on how many client-branded variants you run. See [template variants](https://www.remakecv.com/help/templates-and-branding/template-variants.md). ## How long does it take? **Typically 24 hours** from receiving your files to a sample landing in your inbox for review. Your corrections are then applied and the template goes live for your whole company. Send your files to support@remakecv.com and we will confirm the turnaround for your specific template when we have seen it. ## Frequently asked questions ### What do you need from me? Your existing template as a Word file, one or two completed example CVs showing how it looks when filled in, and your logo as a high-resolution PNG or SVG. ### Do I have to redesign my template? No. The usual request is to reproduce the template you already use, exactly, so your output looks like what clients receive today. Templates are fully custom — whatever your design does, we rebuild it. ### How long does a custom template take to build? Typically 24 hours from receiving your files. You then review a sample and we apply any corrections before it goes live for your company. ### Can I have more than one template? Yes. Most agencies end up with a house template plus client-specific variants. --- # Using the template editor > The RemakeCV template editor is a full template builder — fonts, margins, bullet styling, section order and headings, logos, colours, cover pages, and creating or duplicating whole templates. Source: https://www.remakecv.com/help/templates-and-branding/template-editor Last updated: 2026-08-22 --- The RemakeCV template editor is a full self-serve template builder covering fonts, margins, bullet styling, section order and headings, logos, colours, page backgrounds and cover pages, plus creating, duplicating and restoring whole templates. Editing is reserved for admin users at your agency, since a template change affects everyone's output, and our team can make any change for you on request. ## What the editor covers It is considerably more than a settings panel — this is the full design surface of your agency's CV. | Area | What you control | |---|---| | **Typography** | Document font, body size, and per-element font, size, colour, bold, italic, underline | | **Page** | Margins on all four sides, tab stops, spacing between sections | | **Bullets** | Symbol per indent level, indent and hanging-indent sizes | | **Sections** | Order (drag and drop), heading text, show or hide | | **Header and footer** | Content, logo, alignment, width | | **Cover page** | Enable, and author its content in blocks | | **Backgrounds** | Page background images, opacity, position and size | | **Templates** | Create, rename, duplicate, delete, restore, reorder, set the default | Anything beyond this — a new structured section type, a bespoke layout, a client's own branding rebuilt from scratch — is work our team does for you, usually within 24 hours. See [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## Who can make changes? Creating, renaming, duplicating, deleting, reordering and setting the default — along with every styling control — are reserved for **admin users** at your agency. Non-admins can open the editor and preview templates. This is deliberate: a template change affects every consultant's output from that template, so the people accountable for your agency's brand are the ones who hold the controls. > **Tip:** If you are an admin, agree changes with the team before applying them rather than experimenting in the live editor — and use the preview, which costs nothing. ## How do I preview a change? Use the editor's built-in preview, which renders the template against sample data. That is faster than regenerating a real candidate, and it is free. > **Tip:** Preview against your *longest* sample. Short CVs hide the spacing and pagination behaviour that a fifteen-year career history shows you immediately. ## Would you rather we made the change? Many agencies prefer it, and it is included — no ticket cost, no change fee. It also means the change is validated against awkward real CVs before it reaches your consultants. Email support@remakecv.com with: 1. **Which template**, if you have more than one. 2. **What should change**, as specifically as you can. 3. **A CV that shows what you mean** — far more useful than a description. 4. **Whether it applies to every CV** or only some clients, which decides whether it is a change or a new [variant](https://www.remakecv.com/help/templates-and-branding/template-variants.md). ## Do changes apply retrospectively? Not to files already downloaded — those are fixed documents. Any CV still in your history can be regenerated with the new template at no credit cost, which is how agencies migrate a whole back catalogue after a rebrand. ## Frequently asked questions ### Can I edit my agency's CV template myself? Yes. The template editor covers fonts, margins, bullet styling, section order and headings, logos, colours, backgrounds and cover pages, and lets you create, duplicate, restore and reorder whole templates. Our team can also make any change for you — email support@remakecv.com. ### I can see the editor but cannot create, rename or delete anything. Why? Template editing is reserved for admin users at your agency, because a change affects every consultant's output from that template. Non-admins can open the editor and preview templates. Ask an admin at your agency, or email support@remakecv.com. ### Will my changes affect CVs I already downloaded? No. Downloaded files are fixed. Changes apply to CVs generated afterwards, and to any CV you regenerate from history — which is how agencies migrate a back catalogue after a rebrand, free of charge. ### Can I recover a template I deleted? Yes. Deleted templates are restored from the editor — deletion is reversible. The default template is protected from deletion entirely. --- # Template variants and client-specific versions > Run several versions of your template — client-branded, anonymised, with or without a cover page — and choose the right one per submission. Source: https://www.remakecv.com/help/templates-and-branding/template-variants Last updated: 2026-08-22 --- A RemakeCV template variant is a fully custom version of your template for a specific situation: a client's own branding reproduced exactly, an anonymised layout, or a version without a cover page. There is no limit on how many you run or how different they are. Variants sit alongside your house template, consultants pick the right one when processing a CV, and visibility is scoped so each team sees the variants it works with. ## When do agencies use variants? | Situation | Variant | |---|---| | Client requires submissions in their own template | Client-branded version | | Client runs blind hiring | Anonymised version with identifying fields removed | | Client wants the CV only, no cover sheet | Version without a cover page | | Different divisions with different brands | One variant per brand | | Different markets or languages | Region-specific wording and date formats | ## How do I get a variant set up? Email support@remakecv.com with what needs to differ from your existing template. Because a variant starts from a template we have already built, it is usually turned around faster than an original build — often the same day. > **Tip:** Name variants after the situation, not the design — "Acme Corp — anonymised" beats "Template 3". Consultants pick from a dropdown under time pressure, and the name is the only thing preventing the wrong document going to the wrong client. ## Can I limit who sees a variant? Template visibility is scoped to named consultants or teams — email support@remakecv.com with the template and who should see it, and we configure it. Administrators always see every template regardless. > **Warning:** By default every consultant can select every template, which is what most agencies want. Where a client-branded template must only ever go to that client, ask us to scope it to the team working the account — it takes a moment to set up and removes the risk entirely. ## Can I switch a CV between variants after processing? Yes. Open the CV from [history](https://www.remakecv.com/help/formatting-cvs/cv-history.md), select a different variant and regenerate. No re-upload, no credit. This is genuinely useful in practice: a candidate rejected by one client can be resubmitted to another in that client's format in seconds. ## Should anonymisation be a variant or a setting? Both work, and it depends on how you operate: - **As a variant** — when the layout itself differs, for instance a cover page carrying the reasoning that the anonymised CV cannot. - **As a per-CV action** — when the layout is identical and only the content changes. See [auto-anonymisation](https://www.remakecv.com/help/anonymisation-and-compliance/auto-anonymisation.md). ## Frequently asked questions ### Can a client's template carry their logo instead of ours? Yes. Client-branded variants are a common setup for agencies on preferred-supplier agreements that require submissions in the client's own format. ### Can I restrict a variant to one team? Yes. Tell us the template and which team should see it, and we configure the visibility rule for you. By default every consultant can select every template, which suits most agencies. ### Can I switch a CV between variants? Yes, and it costs no credit. Regenerate the same CV in a different variant from CV history. --- # Logos, fonts and colours > Administrators upload your logo and set header colours in Company Settings. Fonts are chosen from a supported list, and logos must be PNG or JPEG under 5MB. Source: https://www.remakecv.com/help/templates-and-branding/logos-fonts-colours Last updated: 2026-08-22 --- In RemakeCV, your logo, header logo and header/footer colour are set by an administrator in Company Settings, and the CV font is chosen from the built-in list or added for your agency on request. Logos must be **PNG or JPEG under 5MB** — SVG is not accepted. Get the logo dimensions right and the rest is straightforward. ## Uploading your logo | Asset | Format | Size limit | Suggested dimensions | |---|---|---|---| | Logo | PNG or JPEG | 5MB | ~800 × 100 px | | Header logo | PNG or JPEG | 5MB | ~1000 × 400 px | > **Warning:** **SVG files are not accepted.** Export your logo to PNG at the suggested dimensions or larger. A transparent PNG is strongly preferable to JPEG, which will put a white box behind your logo. ## Choosing a font Ready to select straight away: Arial · Aptos · Tahoma · Calibri · Helvetica · Cambria · Century Gothic · Garamond · Montserrat · Apercu Pro Medium **Using your own brand font?** Email support@remakecv.com with the font and we will add it to your template — agencies routinely run their own typeface rather than one of the above. > **Tip:** One practical note for **DOCX** output: a font renders on the recipient's machine only if they have it installed, so a distinctive brand font can shift the layout on a client's PC. Two common approaches — send **PDF**, which embeds fonts and always looks identical, or pair your brand font in headings with an Office-standard body font (Arial, Calibri, Cambria, Garamond, Tahoma, Helvetica). We will set either up for you. See [the downloaded DOCX doesn't look right in Word](https://www.remakecv.com/help/troubleshooting/docx-wont-open.md). ## Header and footer colour Set as a colour value in Company Settings by an administrator — any colour, no palette to choose from. If you have a Pantone or CMYK value from a print brand guide, convert it to hex first and check the result on screen, since print colours rarely match exactly. Send us the brand guide and we will match it for you. ## Who can change what | Setting | Who | |---|---| | Logo and header logo | Administrator | | Header and footer colour | Administrator | | Company address, office number, licence number | Administrator | | CV font | Available beyond administrators | > **Tip:** Font choice being widely available is the most common reason two consultants produce differently styled CVs from the same template. Agree one font as a team and check everyone has it set. See [template basics](https://www.remakecv.com/help/templates-and-branding/template-basics.md). ## Accessibility Some clients — public sector especially — apply contrast requirements to documents they receive. Pale grey body text on white is the usual thing they flag. If your clients audit for this, factor it into your colour choices, or ask us to check the template for you. ## Frequently asked questions ### What logo format should I upload? PNG or JPEG, under 5MB. SVG is not accepted. Aim for roughly 800x100 pixels for the standard logo and 1000x400 for a header logo. ### Can we use our own brand font? Yes. Your brand font can be added to your template — email support@remakecv.com with the font and we will set it up. Worth knowing for DOCX output: a custom font renders on the recipient's machine only if they have it installed, so many agencies pair a brand font for headings with a widely available body font. ### Who can change branding? An administrator, in Company Settings. Font choice is available more widely, which is worth knowing if your team's output looks inconsistent. --- # Section order, headings and how dates appear > Which parts of your CV layout can be changed, who changes them, and why date wording comes from the source CV rather than a formatting setting. Source: https://www.remakecv.com/help/templates-and-branding/date-formats-and-sections Last updated: 2026-08-22 --- Section order, headings and visibility are controlled by your template, and are fully customisable — change them in the template editor, or tell us the specification and we will build it. Date style is set a level earlier, in how your CVs are read, so your agency's house date format is applied consistently to every CV rather than being a per-document setting. ## Who changes what | Change | How | |---|---| | Section order | Template editor, or ask us | | Section headings ("Career History" vs "Work Experience") | Template editor, or ask us | | Hiding a section entirely | Template editor, or ask us | | Font, logo, header and footer colours | Company Settings — see [logos, fonts and colours](https://www.remakecv.com/help/templates-and-branding/logos-fonts-colours.md) | | Whether a cover page is included | Your own settings — see [cover pages](https://www.remakecv.com/help/formatting-cvs/cover-pages.md) | | Date wording | Not a setting — see below | See [using the template editor](https://www.remakecv.com/help/templates-and-branding/template-editor.md) for the full set of controls. ## How do dates actually appear? Dates work slightly differently from the rest of the template, and it is worth knowing why: **date style is configured in how your CVs are read, not in how they are rendered.** RemakeCV reads the date range as the candidate wrote it and carries that wording through, with one automatic normalisation — **full month names are shortened**, so `January 2019` becomes `Jan 2019`. That means: - A CV written as `2019 – 2022` stays as `2019 – 2022`. - A CV written as `January 2019 – Present` becomes `Jan 2019 – Present`. - Two candidates who wrote their dates differently will still look different from each other. > **Note:** If date consistency matters to your agency — and for client-facing submissions it usually does — email support@remakecv.com with the style you want. We configure it once, at the level where dates are interpreted, and every CV your agency produces follows it from then on. ## Can I show time in role? Not as a calculated value. RemakeCV renders the date range from the CV; it does not compute "3 years 2 months" from it. If you want tenure displayed, tell us — it is a template-level change rather than a setting, and it needs a decision about what to do with open-ended and overlapping roles. ## Choosing a section order If you are specifying a template with us, the principle is: **lead with what your client screens on.** | Sector | Common order | |---|---| | General / commercial | Profile → Experience → Education | | Technology | Profile → Skills → Experience → Education | | Graduate / early career | Profile → Education → Experience | | Regulated (finance, legal, healthcare) | Profile → Qualifications → Experience → Education | ## Renaming sections Worth doing where your clients use particular terminology: - Work Experience → Career History, Professional Experience, Employment - Profile → Executive Summary, Candidate Overview - Education → Academic Background A heading applies to every CV rendered in that template. If different clients want different terminology, that is a case for a [template variant](https://www.remakecv.com/help/templates-and-branding/template-variants.md). ## What about one unusual candidate? Within the editor you can reorder and delete **entries and bullet points** inside a section — moving a role up, dropping an irrelevant job. What you cannot do per CV is reorder the sections themselves; that comes from the template. See [reviewing and editing a parsed CV](https://www.remakecv.com/help/formatting-cvs/reviewing-and-editing.md). ## Frequently asked questions ### Can I choose how dates are displayed? Yes. Your agency's house date style is configured once and then applied to every CV automatically, rather than being set per document. Month names are shortened by default — January becomes Jan. Email support@remakecv.com with the style you want. ### Can I show how long a candidate was in each role? Not automatically. RemakeCV renders the date range from the CV rather than calculating a duration from it. If you want tenure shown, tell us — it is a template-level change. ### Can I reorder sections on a single CV? No. You can reorder entries and bullet points within a section, but the order of the sections themselves comes from your template. --- # Auto-anonymisation: what gets removed > RemakeCV removes names, contact details, employer names, institutions and other identifying markers from a CV while preserving achievements, metrics and seniority. Source: https://www.remakecv.com/help/anonymisation-and-compliance/auto-anonymisation Last updated: 2026-08-21 --- RemakeCV's auto-anonymisation strips identifying information while keeping the substance intact. The candidate's name is replaced with a professional headline such as "Lead Data Scientist with 8 years of experience in e-commerce". Employers become industry descriptors, contact details are redacted, and quantified achievements are deliberately preserved. ## What gets removed or replaced? | Element | What happens | |---|---| | Candidate name | Replaced with a **professional headline** — e.g. "Senior Software Engineer with 10+ years of experience in FinTech" | | Email, phone, address | Replaced with `[REDACTED]` | | LinkedIn, YouTube, website and social URLs | Replaced with `[REDACTED]` | | Employer names | Replaced with an industry-and-type descriptor | | Educational institutions | Replaced with a short neutral descriptor | | Locations | Generalised to city or region level | | Proprietary internal tool names | Genericised | | Contact details inside bullet points | Removed | | Photographs | Never present — the output is rebuilt from extracted text | ## What replaces the candidate's name? Not initials, and not a blank. The name is replaced with a **professional headline** summarising seniority, years of experience and specialisation: | Original | Anonymised | |---|---| | Jane Doe | Lead Data Scientist with 8 years of experience in e-commerce | | — | Senior Software Engineer with 10+ years of experience in FinTech | This is deliberate. A blank where a name should be tells a hiring manager nothing; a headline tells them immediately whether the candidate is worth reading, without revealing who they are. ## What is deliberately kept? This is the part that distinguishes a useful anonymised CV from a useless one. - **Quantified achievements.** "Managed a team of 10 and a budget of $500,000" survives verbatim. Strip the numbers and you have removed the evidence the client is hiring on. - **Job titles and seniority.** The client still needs to know whether this is a manager or a director. - **Date ranges and durations.** Career progression is visible. - **Skills, tools and technologies.** Industry-standard tools are kept verbatim — Jira, Salesforce, AWS. Only *proprietary internal* tool names are genericised, since "AcmeCorp Internal Dashboard" identifies the employer. - **Industry context.** An employer becomes a short descriptor of industry and type — for example `Global fintech company; public`. Placeholders like "Company A" are explicitly forbidden. - **Acronyms.** KYC, AML, ERP and the like are preserved rather than expanded, because expanding them changes the meaning a specialist reads. > **Note:** The design goal is stated plainly: maximum insight, zero bias. Anonymisation that also removes the substance defeats the purpose — the client cannot assess the candidate and asks for the identified version anyway. ## How are employer names replaced? With a short descriptor giving industry and type, capped at 12 words. `Stripe` becomes `Global fintech company; public`. Size is only added where it is definitively known rather than inferred — if uncertain, it is omitted entirely. This keeps the CV assessable. "Five years at a tier-one investment bank" tells a hiring manager what they need; "five years at [REDACTED]" tells them nothing. ## Why must I still review the result? Because identifying information hides in places pattern-matching does not reach: - **Project or product names** unique to one employer - **Internal job titles** that only one company uses - **Company-specific acronyms** in bullet points - **Distinctive career paths** — a single named role at a small organisation can be identifying on its own - **Named awards** tied to one company - **Acronyms**, which are deliberately preserved and can be employer-specific Automation catches the structured fields reliably. The long tail is a human judgement call, and the consequence of missing one is a candidate identified in what was supposed to be a blind process. > **Warning:** Before sending an anonymised CV, read it once as a stranger trying to identify the person. Automation reliably handles the structured fields; the long tail below is a human judgement call, and the cost of missing one is a candidate identified in a process that was supposed to be blind. Before anonymising, it is worth confirming nothing was dropped in extraction — see [checking what was extracted](https://www.remakecv.com/help/formatting-cvs/checking-the-extraction.md). ## Can I anonymise a CV I processed earlier? Yes. Open it from [CV history](https://www.remakecv.com/help/formatting-cvs/cv-history.md) and anonymise it there. No re-upload and no credit — useful when a client switches to a blind process mid-shortlist. ## What if I only want to remove some details? Edit the fields directly in the editor. Some clients want the employer visible but the name hidden; that is an edit rather than a full anonymisation. For anything identifying that anonymisation left behind — a project codename, an internal job title — change the wording in the editor before downloading. Replacing beats deleting: "Led delivery of Project Nightingale" → "Led delivery of a group-wide CRM migration" keeps the achievement legible. ## Frequently asked questions ### Does anonymisation remove the candidate's achievements? No. Quantified achievements are explicitly preserved. 'Managed a team of 10 and a budget of $500,000' stays intact — only identifying details are removed. ### What happens to employer names? They are replaced with a neutral descriptor of industry and type, for example 'a global management consultancy' or 'a mid-size SaaS business', so the client can still judge relevance. ### Should I check an anonymised CV before sending it? Yes, always. Identifying details can hide in places automation does not reach — a project name, a niche job title, a company-specific acronym. Review before sending. --- # Neutralising first-person language > Convert a CV written in the first person into neutral or third-person phrasing, so submissions read consistently regardless of how the candidate wrote theirs. Source: https://www.remakecv.com/help/anonymisation-and-compliance/first-person-neutralisation Last updated: 2026-08-21 --- Many candidates write their CV in the first person — "I managed a team of eight". RemakeCV can rewrite this into neutral phrasing or third person, so every CV you submit reads in the same voice. Third person uses the candidate's own name rather than a pronoun: it never infers gender. The rewrite changes phrasing, not facts. ## What are the modes? Three conversions are available. There is no "leave as written" mode — not running the tool is the no-op. | Mode | Example output | Where | |---|---|---| | *(not run)* | "I managed a team of eight across three sites." | — | | **Neutral** | "Managed a team of eight across three sites." | Automatic runs only | | **Third person** | "Sarah Okonjo managed a team of eight across three sites." | AI tools menu | | **First person** | "I managed a team of eight across three sites." | AI tools menu | `First person` is an active conversion *to* first person, not the untouched original — useful when a candidate's CV mixes voices and your house style is first person. ## Which should I use? **Third person** suits agencies whose house style is narrative — common in executive search, where the profile reads more like a written recommendation than a bullet list. Importantly, third person **does not guess gendered pronouns**. It keeps `he`, `she` or `they` only where the source CV already establishes that pronoun; otherwise it uses the candidate's name, or restructures the sentence with an implied subject ("Led the migration…"). It is also prevented from falling back on "the candidate" — that phrasing is detected and rewritten. **Neutral** removes first-person pronouns entirely without introducing any third-person reference. It is currently applied through company-configured automatic runs rather than the AI tools menu, so if you want it applied to every CV, ask us to enable it for your account. > **Warning:** Do not combine third person with [anonymisation](https://www.remakecv.com/help/anonymisation-and-compliance/auto-anonymisation.md). Third person uses the candidate's real name, which puts the name straight back into a document whose purpose is removing it. For anonymised submissions use neutral, or run the person conversion before anonymising and check the result. ## Does it change the meaning? No — and this is enforced structurally, not just requested in a prompt. Two guardrails run after the rewrite: - **Array cardinality is locked.** If the rewrite returns a different number of bullets or roles than it was given, the original list is kept instead. A rewrite cannot silently drop a job. - **Non-narrative fields are protected.** Name, company, employer, title, role, duration, dates, location, email, phone, institution and degree are restored from the original regardless of what the rewrite returned. So the tool can only change the prose. It will not turn "assisted with the migration" into "led the migration"; if you want a claim strengthened, that is an editorial decision for you in the editor. ## When should I run it? After the parse is correct and before you add your own content: ### Process and check the extraction Fix any structural problems first. ### Neutralise the language Apply neutral or third person across the CV. ### Review the rewritten text Read the bullets. This is a language transformation and the occasional sentence will read awkwardly. ### Add your own information and download Salary, notice period, consultant details, then export. ## Does it cost a credit? No. Like every other post-processing action, it runs on a CV that has already been processed. See [how credits and usage work](https://www.remakecv.com/help/getting-started/credits-and-usage.md). ## Frequently asked questions ### Which mode should I use? Third person for narrative house styles; first person if that is your convention. Neutral removes pronouns entirely and is the safest choice alongside anonymisation, but is applied through company-configured automatic runs rather than the menu. ### Does third person guess the candidate's gender? No. It keeps a pronoun only where the source CV already establishes one, and otherwise uses the candidate's name or an implied subject. It is also prevented from writing 'the candidate'. ### Does it change what the CV says? No. Grammatical voice only. Bullet counts and factual fields such as employer, title and dates are restored from the original if the rewrite alters them. ### Does neutralising language cost a credit? No. It runs on a CV you have already processed, so no additional credit is consumed. --- # GDPR, data retention and where CVs are stored > How RemakeCV handles candidate personal data: what is stored, for how long, who controls it, and how to configure retention for your agency. Source: https://www.remakecv.com/help/anonymisation-and-compliance/gdpr-and-data-retention Last updated: 2026-08-22 --- Candidate CVs are personal data and your agency is the data controller; RemakeCV processes them on your instructions. Stored CVs are deleted automatically after a per-company retention period, which defaults to **30 days**. CV storage can also be switched off entirely, in which case nothing is retained after processing. > **Note:** This page explains how the product behaves so you can configure it correctly. It is not legal advice. Your retention periods and lawful basis are decisions for your own DPO or legal adviser. ## Who is the controller? Your agency. You decide which candidates to process, for what purpose, and how long to keep the results. RemakeCV acts as a **processor**, handling that data on your instructions. Practically, this means the obligations that sit with you include: - Having a lawful basis for processing candidate data - Telling candidates their CV will be reformatted and shared with clients - Honouring subject access, rectification and erasure requests - Setting and enforcing a retention period ## How long are CVs kept? **Stored CVs are deleted automatically.** A retention window is applied per company and defaults to **30 days** from when a CV was last updated. When the window passes, both the stored file and its database record are permanently removed — not archived, not soft-deleted. | Setting | Default | Effect | |---|---|---| | Retention window | 30 days from last update | File and record permanently deleted | | CV storage disabled | — | Nothing retained at all; no CV history | | Temporary preview files | 24 hours | Deleted automatically | > **Warning:** This is the fact most often needed for a client security questionnaire or a DPO review: RemakeCV does **not** retain candidate CVs indefinitely by default. If your agency needs a longer or shorter window than 30 days, email support@remakecv.com — it is configurable per company, but only we can change it. Two practical consequences: - **A CV you processed six weeks ago is gone.** Download anything you need to keep into your own systems, or your ATS. - **Retention is not a substitute for your own records.** RemakeCV is a formatting step, not an archive. ## What does RemakeCV store? | Data | Stored? | |---|---| | The uploaded CV file | Only if CV storage is enabled, and only within the retention window | | Extracted structured data | Same — including the *original* pre-edit extraction alongside your edits | | Candidate name, latest employer, latest role | With the stored CV record, for search in history | | Your templates and company settings | Yes | | User accounts | Yes | | Credit usage logs | Yes — user, company and timestamp, for billing | > **Warning:** Disabling CV storage removes [CV history](https://www.remakecv.com/help/formatting-cvs/cv-history.md) as well. Consultants must download the formatted CV before leaving the page, because there is nothing to come back to. Make sure the team knows before you change the setting. ## How do I handle an erasure request? If a candidate asks you to delete their data: ### Locate the CV in your history Note the candidate and roughly when it was processed. ### Email support@remakecv.com Erasure requests come to us and we action them directly, confirming deletion of both the stored record and the underlying file in writing — a documented confirmation you can put straight into your compliance file. ### Delete your own copies Anything you downloaded, sent to a client, or filed in your ATS sits outside RemakeCV and is yours to handle. This is usually the larger part of the request. > **Note:** If the CV is older than your retention window it has already been deleted automatically, and there is nothing left for us to remove. ## Does anonymisation make data non-personal? Not automatically, and this is a common misconception. Removing a name does not make data anonymous under GDPR if the person remains identifiable from what is left — and a detailed career history is often identifying on its own. Treat [anonymised CVs](https://www.remakecv.com/help/anonymisation-and-compliance/auto-anonymisation.md) as pseudonymised personal data unless you have specifically assessed otherwise. They are a bias-reduction tool, not a get-out from data protection obligations. ## Where is data processed? AI processing runs on OpenAI under an enterprise agreement with zero data retention and no training on customer data, and EU data residency is available on request. For hosting, sub-processors and the full detail, see [security and sub-processors](https://www.remakecv.com/help/anonymisation-and-compliance/security-and-subprocessors.md). If you need a signed Data Processing Agreement, email support@remakecv.com. ## Frequently asked questions ### Is RemakeCV a data controller or a data processor? A processor. Your agency decides which CVs to process and why, which makes you the controller. RemakeCV processes them on your instructions. ### How long does RemakeCV keep candidate CVs? Stored CVs are deleted automatically after a per-company retention window, which defaults to 30 days from last update. Both the file and its record are permanently removed. The window is configurable — email support@remakecv.com. ### Can I turn off CV storage entirely? Yes. CV storage is a company-level setting. With it disabled, processed CVs are not retained at all — which also means there is no CV history to return to. ### Can I delete a specific CV myself? Send erasure requests to support@remakecv.com and we action them and confirm back in writing — which is what you want on your audit trail rather than an unlogged button. CVs older than your retention window have already been deleted automatically. ### Are candidate CVs used to train AI models? No. CVs are processed to produce your formatted document and are not used as training data. --- # Security, DPAs and sub-processors > How RemakeCV secures candidate data: encryption, access control, two-factor authentication, an enterprise OpenAI agreement with zero data retention, EU data residency and Data Processing Agreements. Source: https://www.remakecv.com/help/anonymisation-and-compliance/security-and-subprocessors Last updated: 2026-08-22 --- Candidate data is transmitted over encrypted connections and stored in access-controlled cloud infrastructure. AI processing runs on OpenAI under an enterprise agreement with zero data retention — candidate data is not retained by OpenAI after processing and is never used to train models — and EU data residency is available on request. Accounts support two-factor authentication, and a signed Data Processing Agreement is available from support@remakecv.com. ## How is candidate data protected? | Control | Implementation | |---|---| | Data in transit | Encrypted over HTTPS/TLS | | AI processing | OpenAI enterprise agreement — zero data retention, no training on customer data | | Data residency | EU residency available on request | | Data at rest | Stored in access-controlled cloud object storage | | File access | Downloads issued as short-lived signed URLs rather than public links | | Account access | Password authentication with optional two-factor | | API access | Bearer API keys, stored hashed, revocable, optionally time-limited | | Company isolation | Every request is scoped to the authenticated company | ## Who processes candidate data? RemakeCV uses sub-processors for hosting, storage and AI processing. A CV is parsed into structured data by an AI model — that is what makes the formatting work — and the terms under which that happens are the ones your clients will ask about. **AI processing runs on OpenAI under an enterprise agreement.** That agreement carries: - **Zero data retention.** Candidate data is not stored by OpenAI after your request is processed. - **No training on your data.** Customer data is contractually excluded from model training. - **EU data residency, available on request.** Email support@remakecv.com and we will configure it for your account. Alongside that: - **Scoped to purpose.** Data is sent only for the specific processing you triggered. - **Company isolation.** Every request is scoped to the authenticated company, and one customer's data is never accessible to another. For the full list of sub-processors and processing locations, email support@remakecv.com — it is maintained alongside the DPA so it stays accurate as infrastructure changes. > **Tip:** If you are completing a client security questionnaire, the three answers most often asked for are here: **OpenAI, enterprise agreement, zero data retention and no training**, with **EU residency available**. Request the DPA for the signed version. > **Note:** If your clients audit your supply chain — common in financial services, public sector and healthcare recruitment — request the DPA and sub-processor list before you need them, not when a questionnaire lands. ## What should my agency do? The controls on your side matter as much as the ones on ours: ### Enable two-factor authentication The single highest-value change you can make. See [two-factor authentication](https://www.remakecv.com/help/account-and-billing/two-factor-authentication.md). ### Remove leavers promptly A dormant account with access to candidate data is a standing risk. See [user roles and permissions](https://www.remakecv.com/help/account-and-billing/user-roles-and-permissions.md). ### Set a retention position Decide deliberately whether CV storage is on, and for how long. See [GDPR and data retention](https://www.remakecv.com/help/anonymisation-and-compliance/gdpr-and-data-retention.md). ### Rotate API keys If you use the public API, rotate keys periodically and revoke any key whose holder has left. See [authentication](https://www.remakecv.com/help/api-reference/authentication.md). ## How do I report a security concern? Email support@remakecv.com with the details. If you believe you have found a vulnerability, please report it privately rather than publicly, and give us a reasonable window to fix it before disclosure. ## Frequently asked questions ### Can I get a signed DPA? Yes. Email support@remakecv.com and we will provide a Data Processing Agreement covering sub-processors and the roles of each party. ### Are candidate CVs used to train AI models? No. RemakeCV processes CVs through OpenAI under an enterprise agreement with zero data retention: the data is used to produce your formatted output, is not retained by OpenAI afterwards, and is never used to train models. ### Which AI provider does RemakeCV use? OpenAI, under an enterprise agreement. The agreement carries zero data retention and excludes training on customer data, and EU data residency is available on request. ### Can candidate data be processed in the EU? Yes. EU data residency is available on request — email support@remakecv.com and we will configure it for your account. ### Do you support SSO? Two-factor authentication is available on every account as standard. Single sign-on is configured per organisation — email support@remakecv.com with your identity provider and we will set it up. --- # AI-generated candidate summaries > Generate a profile paragraph from the CV content — seniority, sector experience and strengths — then edit it before it goes to the client. Source: https://www.remakecv.com/help/ai-tools/candidate-summaries Last updated: 2026-08-22 --- RemakeCV can generate a candidate summary from the CV's own content: seniority, sector experience, core skills and notable achievements. The summary appears at the top of the CV or on the cover page, and is fully editable before download. It draws only on what the CV says and does not invent experience. ## What does the summary contain? A typical generated summary covers: - **Seniority and discipline** — what this person does and at what level - **Sector experience** — the industries they have worked in - **Core capability** — the skills that recur across their history - **Notable achievements** — quantified results where the CV provides them Length follows your agency's reference summary rather than a fixed limit — the generator is told to match the shape and length of the example your template carries. ## Can I tailor it to a specific role? Yes — and this is the feature most people miss. As well as the CV, the summary generator accepts: - **A context file** — upload the job description, and the summary is written with that role in mind. - **Free-text instructions** — tell it what to emphasise for this submission. Without those, the summary weights a career evenly. A candidate with ten years across operations and analytics gets a balanced summary; if you are submitting them for an analytics role, supply the JD and the emphasis shifts. > **Tip:** Even with a job description supplied, the most useful line is usually the one only you can write: what you learned on the call. Generate the factual base, then add your judgement. ## Does it hallucinate? The summary is generated from the CV's own content, so employers, dates and achievements come from the candidate rather than from the model. It is still worth the ten seconds to read it against the CV before the document goes out — a summary is the first thing a client reads, and it is the part of the document most worth having in your own voice. Every summary is fully editable, and regenerating one costs nothing. Read the summary against the experience section before you send it. ## Where does the summary appear? That depends on your template. Some agencies place it at the top of the CV as a profile section, some on the [cover page](https://www.remakecv.com/help/formatting-cvs/cover-pages.md), and some render a summary per employer or per role rather than one for the whole CV. For [anonymised submissions](https://www.remakecv.com/help/anonymisation-and-compliance/auto-anonymisation.md) the cover page is usually the better home — it lets you carry your reasoning about fit in a document where the candidate's identity has been removed. ## Should the summary be first or third person? Match your house style. Most agencies use neutral phrasing, which avoids pronouns entirely and works for every candidate. See [neutralising first-person language](https://www.remakecv.com/help/anonymisation-and-compliance/first-person-neutralisation.md). ## Frequently asked questions ### Does the summary invent anything? No — it is explicitly instructed not to invent, infer or embellish skills or experience that are not in the CV. It can still emphasise the wrong things for a particular role, which is why it is editable. ### Can I tailor the summary to a specific vacancy? Yes. Upload the job description as a context file, or give free-text instructions on what to emphasise. You can also just edit the result. ### Does generating a summary cost a credit? No. It runs on an already-processed CV, so no additional credit is consumed. --- # Cover letter and cover message generator > Draft a covering message for a candidate submission from the CV content, then edit it to reflect the specific client and role. Source: https://www.remakecv.com/help/ai-tools/cover-letter-generator Last updated: 2026-08-22 --- RemakeCV can draft a covering message for a candidate submission from the CV plus the job description. The job description is required, not optional — the generator is built to argue a specific candidate for a specific role. Output is 220 to 350 words in three to five paragraphs, and it does not invent experience. ## What is it for? The message that accompanies a candidate submission — the two or three paragraphs explaining who this person is and why they are worth a conversation. Most consultants write a version of the same message dozens of times a week. The generator handles the parts that come straight from the CV, so your time goes into the part that does not. ## How should I use it? ### Supply the job description Paste it, or upload the JD as a file. **This is required** — for most agencies the generator refuses to run without it, because a cover message with no role to argue against is just a CV summary. ### Add your screening notes Optional but high-value. Notes from your call are the one input that produces something a competitor cannot generate: motivation for moving, notice period, salary expectation, why this role specifically. ### Generate You get 220–350 words across three to five paragraphs, in plain text, with keywords from the job description worked in naturally for ATS matching. ### Edit and check Read it against the CV. A cover message is the most personal part of a submission, so it is worth a quick pass to put it in your own voice before it goes out — it is fully editable. > **Note:** The cover letter generator is enabled per company rather than available to everyone. If you cannot see it, email support@remakecv.com to ask whether it is switched on for your account. > **Warning:** Never send a generated cover message unedited. An unedited draft carries no evidence you have actually spoken to the candidate — which is the thing your client is paying you for. Supplying your screening notes is what closes that gap. ## What goes in, what comes out | Input | Required? | |---|---| | The processed CV | Yes | | Job description (pasted or uploaded) | Yes, for most agencies | | Your screening notes | Optional, high value | | Client/company details | Optional | | Output property | Value | |---|---| | Length | 220–350 words | | Structure | 3–5 short paragraphs | | Format | Plain text | | ATS keywords | Drawn from the job description, without stuffing | ## Does it work for anonymised submissions? Yes, and it is more useful there. When the CV has been [anonymised](https://www.remakecv.com/help/anonymisation-and-compliance/auto-anonymisation.md), the covering message is where the client learns why you are putting this person forward. > **Warning:** Check the message does not reintroduce what the CV removed. The generator works from the candidate's real data, so employer names and the candidate's name can reappear in the covering text even when the CV itself is anonymised. ## Does it cost a credit? No. Like every post-processing action, it runs on a CV that has already been processed. See [how credits and usage work](https://www.remakecv.com/help/getting-started/credits-and-usage.md). ## Frequently asked questions ### Do I have to supply a job description? Yes, for most agencies — the generator will not run without one. It is built to argue a specific candidate against a specific role, so it needs the role. ### Is the output a message or part of the CV document? It depends on how your template is configured. For some agencies it is a standalone message; for others the generated text is written into the CV's summary or a cover page. ### Can I set a house style? Yes — cover letter output is already tailored per company. Email support@remakecv.com with the structure and tone you want. ### Does it cost a credit? No. It runs on an already-processed CV. --- # Custom extraction fields > Pull agency-specific information out of every CV automatically — security clearance, driving licence, language proficiency or any field your sector requires. Source: https://www.remakecv.com/help/ai-tools/custom-extraction-fields Last updated: 2026-08-21 --- Custom extraction fields tell RemakeCV to look for specific information in every CV you process, beyond the standard sections. Agencies use them for security clearance, driving licences, professional registration numbers, language proficiency and visa status — anything their sector screens on but a standard CV parser does not extract. ## What do agencies extract? In practice, custom fields cluster into three kinds: | Kind | Fields agencies actually use | |---|---| | **Location** | Suburb, current location, region | | **Skills roll-ups** | Top skills, IT skills, system skills, key expertise, key highlights | | **Career summary values** | Total years of experience, education summary, qualifications | Some agencies also extract demographic fields such as nationality or citizenship where their market requires it. The test is simple: **if your consultants read every CV hunting for the same detail, that detail is a custom field.** > **Warning:** Think carefully before extracting demographic data — nationality, age, gender. It is technically straightforward, but it puts protected characteristics into a document that goes to a client, which cuts directly against [blind hiring](https://www.remakecv.com/help/anonymisation-and-compliance/auto-anonymisation.md) and may create obligations under your local employment law. Have a reason beyond "it might be useful". ## How do I set one up? Email support@remakecv.com with: 1. **The field name** as you want it labelled. 2. **What it means**, precisely enough that an extraction rule can be written. 3. **How it appears in real CVs.** Send two or three examples. "SC Cleared", "Security Check (SC)" and "Clearance: SC (expires 2027)" are all the same field, and the examples are what make the rule reliable. 4. **Whether it should infer.** Should the field stay empty when the CV does not say so explicitly, or may it be deduced from context? Decide this deliberately. 5. **Where it should appear** in the output document. ## Does it guess when a CV doesn't say? **That depends on how the field is defined, and it is the most important decision you make when setting one up.** Each field carries its own instruction, and that instruction decides the behaviour: - **Strict** — "if the location is not explicitly stated, leave blank." The field comes back empty, which is a genuine prompt to ask the candidate. - **Permissive** — "only if explicitly mentioned *or strongly inferable* from the CV." The field may be populated by inference. There is no system-wide rule forcing one or the other. > **Warning:** For anything carrying legal or safety weight — clearance levels, registration numbers, licence categories — ask us to define the field as **strict**, and verify the value before relying on it. An inferred security clearance is considerably worse than an empty one. Where a field comes back empty, fill it in from your screening call — see [adding information that wasn't on the original CV](https://www.remakecv.com/help/formatting-cvs/adding-missing-information.md). ## Do custom fields work on scanned CVs? Yes, but with the usual OCR caveat: character-level errors are more likely, and registration numbers are exactly the kind of string where a misread digit matters. Check them. See [scanned PDFs and OCR](https://www.remakecv.com/help/troubleshooting/scanned-pdfs-and-ocr.md). ## Frequently asked questions ### What happens if the information isn't in the CV? It depends how the field was defined. A strict field comes back empty; a permissive one may infer a value from context. Ask for strict definitions on anything with legal or safety weight. ### How do I set up a custom field? Email support@remakecv.com describing the field, how it typically appears in CVs, and whether it should infer or stay strictly literal. Custom extraction is configured per company by our team. ### Do custom fields work on scanned CVs? Yes, though accuracy depends on OCR quality. Always verify extracted values on image-based CVs. --- # Getting better results from the AI > Practical steps to get the most out of RemakeCV: configure recurring preferences once in your template, use custom extraction fields, and let reprocessing do the work on unusual layouts. Source: https://www.remakecv.com/help/ai-tools/improving-ai-output Last updated: 2026-08-22 --- RemakeCV handles every common CV format out of the box, so getting more from it is mostly about configuration rather than technique. Encode your agency's recurring preferences in your template so they apply automatically, set up custom extraction fields for the details your desk always needs, and reprocess freely on unusual layouts — it never costs a credit. ## What RemakeCV reads Every common CV format goes through the same upload and comes out in your template: | Input | Notes | |---|---| | DOCX and DOC | Carries real document structure — the richest input | | Text-based PDF, any column count | Reading order reconstructed from the page layout | | Scanned and image-only PDF | Read page by page, including graphical headers | | Continuous-scroll exports (Canva, Notion) | Sliced, read and stitched back together | > **Tip:** Where a candidate has a Word version to hand it is the ideal input, since the structure is already explicit. It is a nice-to-have rather than something to chase — scans and designed PDFs go through the same workflow. ## Working through an unusual layout ### Reprocess Always free. On an ambiguous document a second pass can resolve it outright. ### Adjust in the editor Usually one or two fields rather than the whole document. See [reviewing and editing](https://www.remakecv.com/help/formatting-cvs/reviewing-and-editing.md). ### Tell us if the pattern recurs A layout your desk sees repeatedly is something we tune at the pipeline level. Email support@remakecv.com with an example. ## Configure once instead of editing every time If you find yourself making the same correction on every CV, it is a configuration problem, not an AI problem. | Recurring edit | Fix once | |---|---| | Reordering sections | Set section order in the template | | Renaming a heading | Set the heading in the template | | A consistent house date style | Configured for your agency once | | Deleting a section you never use | Hide it at template level | | Typing the same field | Add it to your template | | Extracting the same detail manually | Set up a [custom extraction field](https://www.remakecv.com/help/ai-tools/custom-extraction-fields.md) | See [date formats, section order and headings](https://www.remakecv.com/help/templates-and-branding/date-formats-and-sections.md). ## Where your judgement still adds value Occasionally a source document is ambiguous to any reader — a CV that lists a client name exactly where an employer normally sits, for instance. The document itself does not settle it, and you are the right arbiter. That is what the editor is for, and it takes seconds. ## Frequently asked questions ### Does reprocessing cost anything? No. Reprocessing is always free, so it is worth a pass on any unusual layout before you hand-edit. ### Which input format works best? RemakeCV reads PDF, DOCX and DOC, including scanned and multi-column files. A Word document carries the richest structure, so it is the ideal input where a candidate has one — but nothing about the workflow changes either way. ### Can I set rules for how my agency's CVs are read? Yes. Recurring rules are built into your template configuration so they apply to every CV automatically rather than being applied by hand each time. Email support@remakecv.com with the rule and we will set it up. --- # Integrations overview > RemakeCV connects to any ATS or CRM your agency runs. Bullhorn, Vincere, JobAdder, Salesforce and Mercury are live today, and our team builds new integrations on request using your provider's API credentials. Source: https://www.remakecv.com/help/integrations/integrations-overview Last updated: 2026-08-22 --- RemakeCV integrates with any ATS or CRM. Bullhorn, Vincere, JobAdder, Salesforce and Mercury are live today, and integrations with other platforms are built by our team using the API credentials your provider supplies — they behave exactly like the ones already listed. Our team configures each integration for your company, so there is nothing for you to install. ## Which platforms can RemakeCV connect to? Any of them. The table below covers the integrations already live, and the last row covers everything else — which is a build, not a barrier. | Platform | Workflow | Sends the formatted CV back | Connection scope | Setup guide | |---|---|---|---|---| | **JobAdder** | Read and write — pick from the candidate's attachments | Yes | Per company | [JobAdder](https://www.remakecv.com/help/integrations/jobadder.md) | | **Salesforce** | Read and write — format a stored file in place | Yes | Managed by RemakeCV | [Salesforce](https://www.remakecv.com/help/integrations/salesforce.md) | | **Bullhorn** | Write-back | Yes | Per consultant | [Bullhorn](https://www.remakecv.com/help/integrations/bullhorn.md) | | **Vincere** | Write-back | Yes — original and formatted | Per consultant | [Vincere](https://www.remakecv.com/help/integrations/vincere.md) | | **Mercury** | Write-back | Yes — as PDF | Managed by RemakeCV | [Mercury](https://www.remakecv.com/help/integrations/mercury.md) | | **Your platform** | Scoped to your workflow | Yes | Built to suit | [Ask us to build it](#can-you-integrate-with-our-ats) | > **Note:** Each platform exposes a slightly different set of hooks, so the exact in-ATS experience varies — JobAdder, for instance, installs a button directly on the candidate record. The formatting, templates and output are identical everywhere. ## Can you integrate with our ATS? Yes. This is routine work for us, and the process is short: ### Tell us what you run Email support@remakecv.com with the platform name and how your team works today — where CVs live, and where the formatted document needs to end up. ### Ask your provider for API credentials Every serious ATS has a public or partner API. Your provider's support team issues the credentials; most turn this around quickly for an existing customer. ### We build and configure it Our team implements the connection and enables it on your account. The connect option then appears in your dashboard. ### It works like every other integration Same templates, same editor, same anonymisation, same output. The integration only changes how the CV travels between systems. ## Platforms we are regularly asked about Each of these has a setup guide covering what we need from you and how the connection would work. If yours is not here, it is still a yes — email support@remakecv.com. **Recruitment agency CRM and ATS** [Access Recruitment](https://www.remakecv.com/help/integrations/access-recruitment.md) · [Avionté](https://www.remakecv.com/help/integrations/avionte.md) · [Bond Adapt](https://www.remakecv.com/help/integrations/bond-adapt.md) · [Ceipal](https://www.remakecv.com/help/integrations/ceipal.md) · [Crelate](https://www.remakecv.com/help/integrations/crelate.md) · [Eploy](https://www.remakecv.com/help/integrations/eploy.md) · [Firefish](https://www.remakecv.com/help/integrations/firefish.md) · [JobDiva](https://www.remakecv.com/help/integrations/jobdiva.md) · [Loxo](https://www.remakecv.com/help/integrations/loxo.md) · [Manatal](https://www.remakecv.com/help/integrations/manatal.md) · [Recruit CRM](https://www.remakecv.com/help/integrations/recruit-crm.md) · [RecruiterFlow](https://www.remakecv.com/help/integrations/recruiterflow.md) · [Recruitly](https://www.remakecv.com/help/integrations/recruitly.md) · [TargetRecruit](https://www.remakecv.com/help/integrations/targetrecruit.md) · [Tracker RMS](https://www.remakecv.com/help/integrations/tracker-rms.md) · [Zoho Recruit](https://www.remakecv.com/help/integrations/zoho-recruit.md) **In-house talent and HR platforms** [Ashby](https://www.remakecv.com/help/integrations/ashby.md) · [BambooHR](https://www.remakecv.com/help/integrations/bamboohr.md) · [Greenhouse](https://www.remakecv.com/help/integrations/greenhouse.md) · [iCIMS](https://www.remakecv.com/help/integrations/icims.md) · [Lever](https://www.remakecv.com/help/integrations/lever.md) · [SAP SuccessFactors](https://www.remakecv.com/help/integrations/sap-successfactors.md) · [SmartRecruiters](https://www.remakecv.com/help/integrations/smartrecruiters.md) · [Teamtailor](https://www.remakecv.com/help/integrations/teamtailor.md) · [Workable](https://www.remakecv.com/help/integrations/workable.md) · [Workday](https://www.remakecv.com/help/integrations/workday.md) If you would rather build it yourself, the [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) gives you the same processing, retrieval and template endpoints our own integrations use. See [connecting RemakeCV to any ATS](https://www.remakecv.com/help/integrations/using-the-api-instead.md). ## The two workflow shapes **Read-and-write.** Open the candidate, pick the CV already on their record, format it, send the result back. No manual download at either end. **Write-back.** Upload the CV to RemakeCV, format it, then push the formatted document onto the candidate record. This removes the download-and-re-attach step at the end, which is the fiddly half. Which shape a given platform uses depends on what its API exposes, and we will tell you which applies when we scope your integration. ## How do connections work? Once an integration is enabled for your company, **Connect** and **Disconnect** appear in the user menu on your dashboard. Who the connection belongs to differs by platform: - **Bullhorn and Vincere** — per consultant. Each person connects their own account, which keeps ATS-side permissions and audit trails intact per user. - **JobAdder** — per company. One connection serves everyone. - **Salesforce and Mercury** — no customer-side connection to manage. These run on credentials configured by our team. ## Does an integration change the formatting? No. Templates, editing, anonymisation, summaries and downloads behave identically. The integration only changes how the CV travels between systems, so you can adopt one without revisiting anything about your output. ## Which plan includes integrations? All of them. Integrations are available on Business and Enterprise alike — see [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). ## Frequently asked questions ### Which ATS platforms does RemakeCV support? Any of them. Bullhorn, Vincere, JobAdder, Salesforce and Mercury are live integrations today, and our team builds integrations with other platforms on request using the API credentials your provider supplies. Tell us what you run at support@remakecv.com. ### My ATS isn't on the list. Can you integrate with it? Yes. Ask your ATS provider's support team for API credentials, send them to support@remakecv.com, and our team builds the integration for you. It then works exactly like the integrations already listed — format a CV into your template and push the finished document back onto the candidate record. ### Do I need to install anything? No. Our team configures the integration for your company, and the connect option then appears in your dashboard. There is nothing to install and no plugin to maintain. --- # Connecting Bullhorn > Connect Bullhorn to push formatted CVs onto candidate records and to search, create and update candidates from inside RemakeCV. Each consultant connects their own account in a few seconds. Source: https://www.remakecv.com/help/integrations/bullhorn Last updated: 2026-08-22 --- Connecting Bullhorn lets you send a formatted CV onto a candidate record, and search, create and update candidates from inside RemakeCV. Each consultant connects their own Bullhorn account. It is a write-back integration: you format the CV in RemakeCV, then push the finished .docx straight onto the Bullhorn record, with no download-and-re-attach step at the end. ## What it can do | Capability | What happens | |---|---| | Search candidates by name | Searched from within RemakeCV | | View candidate details, work history and education | Read straight from the Bullhorn record | | Create a candidate | Yes | | Update a candidate | Yes | | Upload the formatted CV to a candidate | Yes, as `.docx` | | Workflow shape | **Write-back** — format in RemakeCV, then push the finished document to the Bullhorn record | | Connection scope | Per consultant | > **Note:** Bullhorn is a write-back integration, so the CV starts its journey in RemakeCV: upload the candidate's CV in the normal way, format it, then push the result onto the Bullhorn record. That removes the fiddly half of the job — the download and re-attach at the end. ## What you need first - Bullhorn enabled for your company — our team switches it on, so email support@remakecv.com - A Bullhorn login for each consultant who will use it ## How to connect ### Start from RemakeCV Open the user menu on your dashboard and choose Connect Bullhorn. ### Sign in to Bullhorn You are sent to Bullhorn to sign in. Each consultant does this with their own account, which keeps Bullhorn-side permissions and audit trails intact per user. ### Confirm you are connected You are returned to RemakeCV. Check the Bullhorn panel shows as connected before relying on it. > **Note:** Because connections are per consultant, rolling Bullhorn out to a team means each person connecting once — a few seconds each, and their own Bullhorn permissions carry across. ## The day-to-day workflow ### Upload the CV to RemakeCV From your desktop, in the normal way. See [uploading a CV](https://www.remakecv.com/help/formatting-cvs/uploading-a-cv.md). ### Format and review Choose a template, check the extraction, apply any AI tools. ### Find the candidate in Bullhorn Search from within RemakeCV, or create the candidate if they are new. ### Push the formatted CV across It is uploaded to the candidate record as `{First}_{Last}_CV.docx`. ## Troubleshooting | Symptom | Likely cause | Fix | |---|---|---| | "Bullhorn account is not connected" | Never connected, or tokens cleared | Connect from the user menu | | "Failed to refresh Bullhorn token" | Refresh token expired or revoked | Reconnect | | "Could not obtain Bullhorn session" | REST session could not be established | Reconnect | | "Missing REST URL, please reconnect" | Session data incomplete | Reconnect | | Works for you, not a colleague | Connections are per consultant | They connect their own account | | Upload rejected by Bullhorn | Entitlements on the Bullhorn user account | Check permissions with your Bullhorn administrator | > **Tip:** Uploaded files carry the logical type (`Resume` or `FormattedResume`) in the record's external identifier rather than the Bullhorn file-type field. If files appear under an unexpected type in Bullhorn, that is why — the document itself is correct. See [integration sync errors](https://www.remakecv.com/help/troubleshooting/integration-sync-errors.md), or email support@remakecv.com. ## Running another ATS or CRM as well? RemakeCV integrates with any ATS or CRM your agency runs, not only the platforms already live. Our team builds new integrations on request using the API credentials your provider supplies, and they behave exactly like this one — same templates, same editor, same output. Email support@remakecv.com with the platform name, or see the [integrations overview](https://www.remakecv.com/help/integrations/integrations-overview.md). ## Frequently asked questions ### How does a CV get from RemakeCV into Bullhorn? Bullhorn is a write-back integration. Upload the candidate's CV to RemakeCV, format it into your template, then push the finished document onto the Bullhorn candidate record as a .docx — the download-and-re-attach step disappears. ### Is the connection per user or per company? Per consultant. Each person connects their own Bullhorn account, which keeps Bullhorn-side permissions and audit trails intact per user. ### Do I need to reconnect Bullhorn? Rarely. Bullhorn's REST session runs on its own clock alongside the OAuth token, and RemakeCV re-establishes it automatically. On the occasions Bullhorn wants your sign-in again, reconnecting from the user menu takes a few seconds. --- # Connecting Vincere > Connect Vincere to push formatted CVs onto candidate records, choosing the Vincere document type they are filed under. Our team provisions your tenant in advance, and each consultant connects individually. Source: https://www.remakecv.com/help/integrations/vincere Last updated: 2026-08-22 --- Connecting Vincere lets you push a formatted CV onto a candidate record, choosing which Vincere document type it is filed under — and it is the one integration that can file the original CV and the formatted CV under separate document types on the same record. Each consultant connects individually, and our team provisions your tenant configuration in advance, so there is nothing for you to enter. ## What it can do | Capability | What happens | |---|---| | Search and list candidates | Yes, with name-variant fallbacks | | Create and update candidates | Yes | | Read and write work experience entries | Yes | | Upload the original CV **and** the formatted CV | Yes, under separate document types | | Assign a candidate owner | Yes | | Workflow shape | **Write-back** — format in RemakeCV, then push the finished document to the Vincere record | | Connection scope | Per consultant, on a tenant provisioned by RemakeCV | Vincere is the only integration that can file both the original and the formatted CV under different document types on the same record. ## What you need first - Vincere enabled and your tenant provisioned — our team does this for you, so email support@remakecv.com - A Vincere login for each consultant who will use it > **Note:** Your tenant identifier and API key are configured by our team, so there is no credential for you to source, enter or rotate. One Vincere tenant is assigned per company, and agencies operating separate regional tenants are set up as separate RemakeCV companies. ## How to connect ### Start from RemakeCV Open the user menu on your dashboard and choose Connect Vincere. ### Sign in to Vincere Authorise with your own Vincere account. Complete the consent screen in one go — the authorisation request stays valid for about ten minutes. ### Confirm and test Push one formatted CV onto a test candidate before rolling out. ## Two Vincere behaviours worth knowing ### Document type is checked on every upload Vincere sets which document types each user may write to, and RemakeCV re-checks your permitted types at the moment of upload. That means what you file a CV under is always something Vincere will accept from your account. If a type exists in Vincere but is not permitted for your user, you will see "The selected document type is not permitted for this Vincere user." That is a Vincere permissions setting rather than a RemakeCV connection matter — your Vincere administrator can grant the type, and the upload then goes through. ### Phone numbers need a country Vincere validates phone numbers against a country and will not accept a local-format number it cannot place. Rather than failing the whole save, RemakeCV keeps the candidate and tells you: > The candidate was saved without the phone/mobile number: Vincere could not validate it. Add a country code (e.g. +852) or set the candidate's country in Vincere, then try again. > **Note:** The candidate **was** created — the record is there. Add the number with a country code, or set the candidate's country in Vincere, and it is complete. Vincere is a write-back integration, so start by uploading the candidate's CV to RemakeCV in the normal way — see [uploading a CV](https://www.remakecv.com/help/formatting-cvs/uploading-a-cv.md) and the [integrations overview](https://www.remakecv.com/help/integrations/integrations-overview.md). ## Troubleshooting | Message | Meaning | Fix | |---|---|---| | "Vincere is not configured for this company" | Your tenant is not yet provisioned | Email support@remakecv.com | | "The requested Vincere tenant is not assigned to this company" | Tenant mismatch | Contact support | | "Not authenticated with Vincere… Please connect your account" | This consultant has not connected | Connect from the user menu | | "Unauthorized. Please reconnect to Vincere." | Token expired or revoked | Reconnect | | "The selected document type is not permitted" | Vincere user permissions | Adjust in Vincere | | "Too many Vincere requests. Please retry shortly." | Rate limited | Wait and retry | | "CV file must be 10 MB or smaller." | File too large for the Vincere upload | Reduce the file size | | "Unsupported CV file type" | Vincere accepts `.pdf .doc .docx .rtf .txt` | Convert the file | > **Tip:** Vincere connections are per consultant and, like any OAuth connection, are renewed periodically. If anything looks off, reconnecting from the user menu takes a few seconds and is always the first thing to try. See [integration sync errors](https://www.remakecv.com/help/troubleshooting/integration-sync-errors.md). ## Running another ATS or CRM as well? RemakeCV integrates with any ATS or CRM your agency runs, not only the platforms already live. Our team builds new integrations on request using the API credentials your provider supplies, and they behave exactly like this one — same templates, same editor, same output. Email support@remakecv.com with the platform name, or see the [integrations overview](https://www.remakecv.com/help/integrations/integrations-overview.md). ## Frequently asked questions ### Do I need to enter a tenant ID or API key? No. Our team provisions your Vincere tenant configuration in advance, so there is nothing for you to enter or keep up to date. If a connection reports that Vincere is not yet configured for your company, email support@remakecv.com and we will provision it. ### Why was my candidate saved without their phone number? Vincere validates phone numbers against a country. Rather than losing the whole record, RemakeCV saves the candidate without the number and tells you — add a country code such as +852, or set the candidate's country in Vincere, and the record is complete. ### Which Vincere document types can I file a CV under? The ones your Vincere user is permitted to write to. RemakeCV re-checks your permitted types on every upload, so what you see offered is always what Vincere will accept from your account. --- # Connecting JobAdder > The JobAdder integration installs a Choose and Process CV button on every candidate record and reads the CVs already attached there, so you format in place and the finished document goes straight back. Source: https://www.remakecv.com/help/integrations/jobadder Last updated: 2026-08-22 --- Connecting JobAdder installs a "Choose and Process CV" button on every candidate record. Clicking it opens RemakeCV with that candidate's attachments listed, so you pick which CV to format without downloading anything, and the finished document goes back onto the same record. It is a read-and-write integration, and the connection is per company — one person connects and everyone gets the button. ## What it can do | Capability | What happens | |---|---| | A button on every candidate record | "Choose and Process CV", installed at authorisation | | List the CVs already attached to a candidate | Yes, newest first | | Format an attachment in place | Yes — no download to your desktop | | Create and update candidates | Yes | | Send the formatted CV back | Yes, as `.docx` under `FormattedResume` | | Workflow shape | **Read and write** — pick from the candidate's attachments, format, send back | | Connection scope | Per company | ## What you need first - JobAdder enabled for your company — our team switches it on, so email support@remakecv.com - A JobAdder account that can authorise partner applications - At least one template configured in RemakeCV ## How to connect ### Start from RemakeCV Open the user menu on your dashboard and choose Connect JobAdder. The flow starts here, not inside JobAdder. ### Authorise in JobAdder You are sent to JobAdder's consent screen. Accept **every** permission requested — the integration asks for `read_candidate`, `write_candidate`, `offline_access`, `partner_ui_action` and `read_user`. `partner_ui_action` is what installs the button, and `offline_access` is what keeps the connection alive. Grant the full set at authorisation so every part of the workflow is available from the start. ### Check the button appeared Open any candidate in JobAdder. "Choose and Process CV" should be on the record. Worth confirming on one candidate before you roll out to the team. ### Test end to end Format one candidate and confirm the formatted CV lands back on the record before rolling out to the team. > **Note:** Reconnecting is self-healing: the existing button is removed and recreated, so disconnecting and reconnecting refreshes the whole setup in one step. ## The day-to-day workflow ### Open the candidate in JobAdder Find the candidate whose CV you need. ### Click Choose and Process CV RemakeCV opens with that candidate's attachments listed, newest first. ### Pick the CV to format Choose which attachment is the current CV — useful when a candidate has sent several versions. ### Format and review Choose a template, review the extraction, apply any AI tools. ### Send it back The original goes to the candidate's `Resume` attachments and the formatted document to `FormattedResume`, as a `.docx`. ## Sandbox mode Your company can be pointed at JobAdder's sandbox instead of production, which is useful while you are testing a rollout. Both environments use the same login screen, so tell us which one you want to be on and we will confirm which your account is connected to. ## Troubleshooting | Symptom | Likely cause | Fix | |---|---|---| | Was working, now fails for everyone | Company-level token expired or refresh failed | Reconnect | | Button missing on candidate records | The button is reinstalled on reconnect | Disconnect and reconnect | | "Candidate with this email already exists" | JobAdder rejected a duplicate | Use the existing record | | Validation error on candidate creation | First or last name missing | Supply both | | Cannot attach the formatted CV | `write_candidate` not granted | Reconnect, accept all permissions | | Data looks different from live JobAdder | Connected to sandbox rather than production | Contact support | See [integration sync errors](https://www.remakecv.com/help/troubleshooting/integration-sync-errors.md). ## Driving it from your own system If your team would rather own the connection, the [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) gives you the same processing, retrieval and template endpoints our own integrations use — see [connecting RemakeCV to any ATS or internal system](https://www.remakecv.com/help/integrations/using-the-api-instead.md). ## Running another ATS or CRM as well? RemakeCV integrates with any ATS or CRM your agency runs, not only the platforms already live. Our team builds new integrations on request using the API credentials your provider supplies, and they behave exactly like this one — same templates, same editor, same output. Email support@remakecv.com with the platform name, or see the [integrations overview](https://www.remakecv.com/help/integrations/integrations-overview.md). ## Frequently asked questions ### Where does the button appear? On the candidate record in JobAdder, labelled "Choose and Process CV". It is created automatically when the connection is made and removed again if you disconnect. ### Is the connection per user or per company? Per company. One authorisation serves everyone, so a new consultant has the button on their first day with nothing to set up. ### Can it read the CV already on the candidate record? Yes. JobAdder is a read-and-write integration: you choose from the candidate's existing attachments rather than uploading anything, and the formatted document goes back onto the same record. --- # Connecting Salesforce > The Salesforce integration formats a CV already stored against a candidate record, in place, and sends the finished document back. Our team configures it for your org, so there is nothing for consultants to set up. Source: https://www.remakecv.com/help/integrations/salesforce Last updated: 2026-08-22 --- The Salesforce integration lets you search candidate records, pick a CV already attached, and format it in place — no download and re-upload — then send the finished document back to the record. It is a read-and-write integration, configured by our team using credentials for a Salesforce integration user, so there is nothing for individual consultants to connect or renew. ## How setup works > **Note:** Salesforce is a managed setup: everything runs through a single integration user that our team configures. There is no consent screen for consultants to complete, no per-user authorisation to chase and no token for anyone to renew — once it is enabled, the whole team has it. What we need from you: ### Credentials for a Salesforce integration user Either a connected app configured for server-to-server access, or a dedicated integration user account. Your Salesforce administrator provisions this. ### Your candidate schema The integration reads a **Candidate** object with distinct first name, last name and email fields. Send us your object and field API names and we configure the integration to match your org before you roll out. ### Confirmation of which files hold CVs The integration looks for Word and PDF files attached to the candidate record, newest first. Because it runs as one integration user rather than as each consultant, per-user Salesforce permissions do not affect who can use it inside RemakeCV. ## What it can do | Capability | What happens | |---|---| | Search candidates by name or email | Yes — minimum three characters | | Look a candidate up directly by Salesforce ID | Yes | | List the files attached to a candidate | Yes, newest first | | **Format a CV stored in Salesforce, in place** | **Yes** | | Upload the formatted CV back to the record | Yes | | Workflow shape | **Read and write** — pick a stored file, format it, send the result back | | Connection scope | Managed by RemakeCV — nothing per consultant to connect | ## The day-to-day workflow ### Find the candidate Search by name or email from within RemakeCV. A link carrying the Salesforce candidate ID opens straight onto that candidate. ### Pick the CV The candidate's attached files are listed, most recent first. ### Format in place RemakeCV pulls the file from Salesforce and processes it — no download to your desktop. ### Review and send back Check the extraction, then upload the formatted CV to the candidate record. ## Specifications | Setting | Value | |---|---| | File types read from Salesforce | `.pdf`, `.docx`, `.doc` | | Upload size | 25MB | | Minimum search term | 3 characters | | Results per page | 25 | Credits are checked before a Salesforce CV is processed, so a company at zero credits gets a clear "No credits left" rather than a partial run. See [credits explained](https://www.remakecv.com/help/account-and-billing/credits-explained.md). ## Troubleshooting | Message | Meaning | |---|---| | "Salesforce integration is not configured properly" | Credentials need attention — email support@remakecv.com | | "The object 'Candidate__c' is not accessible or configured correctly" | Your org's object name differs, or the integration user needs access to it | | "Field Error…" naming first/last name or email fields | Your org's field API names differ — send them to us and we will map them | | "Invalid query cursor" | The search was too broad — refine the search term | | "Search term must be at least 3 characters long" | Type more | | "Unsupported file type" | PDF, DOCX and DOC are read from Salesforce — convert the file | | "File size exceeds limit (25MB)" | Reduce the file size | See [integration sync errors](https://www.remakecv.com/help/troubleshooting/integration-sync-errors.md), or email support@remakecv.com. ## Running another ATS or CRM as well? RemakeCV integrates with any ATS or CRM your agency runs, not only the platforms already live. Our team builds new integrations on request using the API credentials your provider supplies, and they behave exactly like this one — same templates, same editor, same output. Email support@remakecv.com with the platform name, or see the [integrations overview](https://www.remakecv.com/help/integrations/integrations-overview.md). ## Frequently asked questions ### How is the Salesforce integration set up? Our team configures it using credentials for a Salesforce integration user that your Salesforce administrator provisions. Because it runs on one integration user, there is no per-consultant authorisation to complete and nothing to renew. Email support@remakecv.com to start. ### Will it work with our Salesforce object and field names? Yes — we map the integration to your schema. It reads a Candidate object with distinct first name, last name and email fields, so if your org uses different API names, send them to us and we configure the integration to match before you roll out. ### Can it format a CV already in Salesforce? Yes. That is the point of this integration — you pick a file from the candidate record and format it without downloading anything, and the finished document goes back onto the same record. --- # Connecting Mercury > The Mercury integration searches Mercury contacts, attaches the formatted CV to a contact record as a PDF, and creates new contacts by letting Mercury parse the CV. Our team configures access, so there is nothing to install or renew. Source: https://www.remakecv.com/help/integrations/mercury Last updated: 2026-08-22 --- The Mercury integration lets you search Mercury contacts, attach a formatted CV to an existing contact as a PDF, or create a new contact by sending Mercury a CV to parse. It is a write-back integration: you format the CV in RemakeCV, then the finished document goes onto the Mercury record. Our team configures access for your company, so there is nothing to connect, sign in to or renew. > **Note:** Mercury is a managed setup: our team configures access for your company, so there is no Connect button to find, no sign-in to complete and no authorisation that expires. Email support@remakecv.com to have it enabled, and the Mercury actions appear on your dashboard. ## What it can do | Capability | What happens | |---|---| | Search Mercury contacts by name or email | Searched from within RemakeCV | | Attach a formatted CV to an existing contact | Filed on the contact record as a **PDF** | | Create a new contact from a CV | Mercury parses the CV and builds the record | | Workflow shape | **Write-back** — format in RemakeCV, then the finished document goes onto the Mercury record | | Connection scope | Managed by RemakeCV — nothing per consultant to connect | ## The day-to-day workflow ### Upload and format the CV in RemakeCV Start in RemakeCV as normal — upload the candidate's CV and format it into your template. See [uploading a CV](https://www.remakecv.com/help/formatting-cvs/uploading-a-cv.md). ### Search for the contact Search Mercury by name or email from within RemakeCV. ### Attach, or create a new contact Attach the formatted CV to the existing contact, or — if the candidate is new — send the CV to Mercury to parse into a fresh contact record. ## Two things worth knowing **The attachment is a PDF.** Mercury receives the formatted CV as a PDF, which is the form a Mercury contact record expects. If your team also wants the editable file, download the `.docx` of the same document from RemakeCV — see [downloading as DOCX or PDF](https://www.remakecv.com/help/formatting-cvs/downloading-docx-pdf.md). **Search on a precise term.** A full name or an email address returns the right contact fastest. A one- or two-letter search asks Mercury for a far wider set than you need, so give it enough to work with. ## Troubleshooting | Message | Meaning | |---|---| | "Mercury credentials not configured" | Mercury is not yet enabled for your account — email support@remakecv.com | | "Search term is required." | Enter a search term | | "Failed to search for candidates." | Mercury search did not return — retry, then contact support | | "Failed to upload CV." | The attachment did not reach the contact record | | "Failed to create contact from CV." | Mercury could not parse the CV into a new contact | There is no token to refresh and no connection to re-authorise, so Mercury never needs reconnecting. If something does look off, email support@remakecv.com with the time and what you were doing and we will check the configuration directly. See [integration sync errors](https://www.remakecv.com/help/troubleshooting/integration-sync-errors.md). ## Running another ATS or CRM as well? RemakeCV integrates with any ATS or CRM your agency runs, not only the platforms already live. Our team builds new integrations on request using the API credentials your provider supplies, and they behave exactly like this one — same templates, same editor, same output. Email support@remakecv.com with the platform name, or see the [integrations overview](https://www.remakecv.com/help/integrations/integrations-overview.md). ## Frequently asked questions ### How do I set Mercury up? Email support@remakecv.com and our team configures access for your company. Because we hold the configuration, there is no connect step, no sign-in and no authorisation to renew — the Mercury actions simply appear on your dashboard. ### What format does the CV arrive in on the Mercury record? PDF. Mercury receives the formatted CV as a PDF, and the editable .docx of the same document is always available to download from RemakeCV alongside it. ### How does a CV get from RemakeCV into Mercury? Mercury is a write-back integration. Upload the CV to RemakeCV, format it into your template, then attach the finished document to the Mercury contact — or send it to Mercury to parse into a brand-new contact record. --- # Connecting RemakeCV to any ATS or internal system > The RemakeCV public REST API lets any ATS, CRM or in-house system process CVs, list results and fetch templates — the same endpoints our own native integrations are built on. Source: https://www.remakecv.com/help/integrations/using-the-api-instead Last updated: 2026-08-22 --- RemakeCV connects to any ATS, CRM or internal system through its public REST API. It processes a CV from a file upload, returns the parsed candidate data and a download URL, and lets you list stored CVs and available templates. If you would rather not build it, our team builds the integration for you instead. ## When is the API the right choice? - You want CV formatting inside your own candidate portal or careers site - You have an in-house recruitment system - You want to script a back-catalogue migration - Your workflow has a shape you would rather control end to end - You are connecting a platform we have not built a native integration for yet — though our team will happily build that for you instead, see [integrations overview](https://www.remakecv.com/help/integrations/integrations-overview.md) ## 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 Email support@remakecv.com and we will enable the API 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 ### Can RemakeCV connect to our ATS? Yes. Either our team builds the integration for you using API credentials from your provider, or you build it yourself against the public REST API. Email support@remakecv.com to start. ### Do I need a developer? Only if you want to build it yourself. Our team can build and configure the integration for you instead. If you do build it, it is a small piece of work by most standards — six REST endpoints. ### Does the API cost extra? No. API usage draws on the same credit pool as the web app: one credit per CV processed, on every plan. --- # Connecting Access Recruitment > RemakeCV connects to Access Recruitment. Our team builds and configures the integration using API credentials from your Access Recruitment account, so branded CVs return to the candidate record instead of being downloaded and re-attached by hand. Source: https://www.remakecv.com/help/integrations/access-recruitment Last updated: 2026-08-22 --- RemakeCV connects to Access Recruitment. Our team builds and configures the integration for your agency using API credentials from your Access Recruitment account, and once it is enabled it works the same way as every other RemakeCV ATS integration: a candidate's CV goes into your branded template and the finished document returns to their record. Email support@remakecv.com and we will scope it with you. ## How the integration is set up ### Tell us you run Access Recruitment Email support@remakecv.com with your agency name and a few lines on how CVs move through your desk today — where they are stored, who formats them, and where the client-ready version has to end up. ### Request API credentials for your account Ask your provider's support or account team for API access on your Access Recruitment account. This is a routine request from an existing customer, and they will tell you what they can issue and on what terms. ### Get the credentials to us securely We will tell you how to send them safely. Treat them like any credential that reaches candidate data: never over an unencrypted channel, and never left sitting in a shared inbox thread. ### We build it and switch it on Our team implements the connection and enables it for your company. The relevant options then appear in your RemakeCV dashboard, so your consultants have nothing to install or maintain. > **Note:** What the integration can do depends on what the API exposes to your account — commonly fetching a candidate's CV, writing the branded document back to their record, or both. We confirm exactly what yours will do when we scope it with you, before any build work begins. Connection scope is settled in that same conversation. Some of our integrations are held once for a whole company and others belong to each consultant individually, which keeps permissions and audit trails sitting with the person doing the work. We will agree which shape fits your agency rather than assume it. For how credentials and candidate data are handled more generally, see [security and sub-processors](https://www.remakecv.com/help/anonymisation-and-compliance/security-and-subprocessors.md). ## What the workflow looks like With the integration live, turning a raw CV into something you can send to a client stops involving a trip through your downloads folder: 1. Work the candidate in Access Recruitment exactly as your team does now. 2. Their CV is formatted into your agency's branded template, using the same template, editor and options as every other RemakeCV workflow. 3. The finished document comes back to the candidate record, ready to go out with the shortlist. The middle step is unchanged from what your consultants already know — 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 arrives over an integration or is dragged into the browser. [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 what your clients receive looks the same the day before go-live and the day after. If your branded template has not been built yet, that runs alongside the integration work rather than after it — our team builds the template 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 own the connection, the [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) gives you the processing, retrieval and template endpoints directly, so you can wire RemakeCV into Access Recruitment on your own 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? Every plan includes integration work, Business and Enterprise both. See [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). ## Start the conversation Email support@remakecv.com with **Access Recruitment** and your agency name. We will confirm what the integration will do on your account, what we need from you, and how your consultants will use it day to day. ## Frequently asked questions ### Does RemakeCV integrate with Access Recruitment? Yes. Our team builds and configures the Access Recruitment integration for your agency using API credentials from your Access Recruitment account. Once it is enabled it works like our other ATS integrations. Email support@remakecv.com and we will scope it with you. ### What do I need to provide? API credentials for your Access Recruitment account, which you request from your provider's support or account team, along with a short account of how your consultants handle CVs today. Send both to support@remakecv.com and our team does the build. ### Will it work the same as the other integrations? Yes. The same templates, editor, anonymisation, summaries and downloads apply. An integration decides how a CV travels between systems and nothing else, so the finished document is identical either way. ### Can I use RemakeCV with Access Recruitment before the integration is set up? Yes. RemakeCV runs standalone in your browser — upload a CV, format it into your branded template, download it and attach it wherever you need. The integration saves the manual steps at each end; it is not a condition of using RemakeCV. --- # 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. --- # Connecting Avionté > RemakeCV connects to Avionté. Our team builds the connection from API credentials issued on your Avionté account, so branded CVs come back onto candidate records at the volumes a contract staffing desk actually runs at. Source: https://www.remakecv.com/help/integrations/avionte Last updated: 2026-08-22 --- RemakeCV connects to Avionté. Our team builds and configures the connection for your staffing firm from API credentials issued on your Avionté account, so a candidate's CV becomes a branded, client-ready document and lands back on their record rather than passing through somebody's desktop. Tell us about your volumes at support@remakecv.com and we will take it from there. ## Volume is what makes this worth doing Avionté serves the US staffing market, and the weight of that market sits in contract and temporary placement — light industrial, clerical, healthcare — where a single branch can fill more roles in a week than a permanent desk fills in a quarter. That changes the arithmetic of CV presentation. On a retained search, twenty minutes tidying a document is nothing against the fee. At contract volume, the same twenty minutes repeated across every submission is not an overhead on the job; it is the job. So the question here is not whether a formatted CV lands better with a client. It is what each one costs in recruiter minutes, and whether that cost holds when an account manager needs fifteen people in front of a client by Thursday. ## How the integration is set up ### Tell us Avionté is your system of record Email support@remakecv.com with your firm's name, roughly how many candidate documents go out in a week, and whether one branch or several are in scope to begin with. ### Establish what API access your account allows Avionté determines what credentials can be issued to you and on what terms. Their answer sets the boundary of what we build against, so it is the first thing to get moving. ### Pass the credentials to us on a secure channel We will point you at one. Anything with reach into candidate data deserves the handling you would give a production secret — never plain email, never a shared inbox thread. ### We build the connection, then enable it Our team implements it and switches it on for your company. The controls surface in your RemakeCV dashboard, so no recruiter has anything to install or maintain. > **Note:** What the connection is able to do is set by the API access granted on your Avionté account rather than by us — commonly collecting a candidate's CV, filing the branded version back against them, or both. That scope is agreed with you before any build work begins, rather than assumed here. ## Where bulk formatting fits A connection removes handling per CV. [Bulk formatting](https://www.remakecv.com/help/formatting-cvs/bulk-formatting.md) removes it per batch, and on a contract desk the two answer different halves of the same problem. Drop a set of CVs in together and they queue and process unsupervised — what you want when a branch is standing up a new account or clearing a backlog. Credits pool at company level, so a branch running hot one week needs no allocation of its own — though [per-user limits and team pools](https://www.remakecv.com/help/account-and-billing/credits-explained.md) exist if you would rather it did. ## What actually changes for a recruiter | | Without a connection | Once it is live | |---|---|---| | **Getting the CV in** | Someone saves the candidate's file out and uploads it | The CV on the record is picked up directly | | **The formatting itself** | Your template, editor and options as normal | Identical — this part is untouched | | **Getting the result back** | Download, then reattach it to the record by hand | The branded document is filed against the candidate | The first and third rows follow the API access your account is granted, which is the scoping conversation above. The middle row never varies. 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) for what a recruiter sees while it happens. ## Does the integration change the formatting? No. A connection governs the route a file takes and nothing else, so your template, the editor, anonymisation, summaries and downloads behave as they do for a CV dragged into the browser. The document a client opens is the same either way. Firms placing into several sectors often want a submission to look different depending on who receives it. [Template variants](https://www.remakecv.com/help/templates-and-branding/template-variants.md) handle that — a client-branded version, an anonymised one, one without a cover page — over the same underlying structure. If your design has not been built with us yet, our team builds it from your existing document: see [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## Owning the connection yourself Avionté gets asked about often enough to be worth a page, but the pages here are not a limit: whatever your firm runs, including an internal system, our team will build against the credentials that provider issues. If you would rather your own developers held it, the [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) exposes 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 plan includes it? Both of them. Business and Enterprise each cover integration work; [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md) explains what separates the two. ## Start the conversation Email support@remakecv.com with **Avionté**, your firm's name and the branches you would begin with. We will confirm what the connection can do on your account, what we need from you, and how your recruiters will use it. ## Frequently asked questions ### Does RemakeCV integrate with Avionté? Yes. Our team builds and configures the Avionté connection for your staffing firm from API credentials issued on your Avionté account, and it then behaves like the rest of our ATS connections. Tell us about your volumes at support@remakecv.com and we will take it from there. ### What do I need to provide? API credentials issued on your Avionté account, which Avionté arranges for you as an existing customer, and a rough sense of how many candidate documents your branches put in front of clients in a typical week. Send both to support@remakecv.com and our team handles the build. ### Will it work the same as the other integrations? Yes. The same templates, editor, anonymisation, summaries and downloads apply, and bulk formatting is unaffected. A connection determines how a CV moves between two systems and decides nothing about the document a client receives. ### Can I use RemakeCV with Avionté before the integration is set up? Yes. RemakeCV runs standalone in a browser, and bulk formatting means a batch of CVs can be dropped in together rather than one at a time. High-volume desks often prove the format that way first and add the connection afterwards; it was never a prerequisite. --- # Connecting BambooHR > RemakeCV connects to BambooHR. Our developers build and configure the integration from API credentials issued for your BambooHR account, so your HR team gets branded candidate CVs without taking on a technical project. Source: https://www.remakecv.com/help/integrations/bamboohr Last updated: 2026-08-22 --- RemakeCV connects to BambooHR. Our developers build and configure the integration for your HR team using API credentials issued for your BambooHR account, and it then behaves like every other RemakeCV ATS integration — a candidate's CV is formatted into your branded template and the finished document is returned to their record. Email support@remakecv.com and we will scope it with you. ## Who usually owns this on your side BambooHR is an HR platform, so recruitment tends to be one strand of a much wider people-operations remit rather than somebody's whole job. The person who ends up arranging a CV formatting integration is normally an HR generalist — the same colleague fielding policy questions, chasing references and running onboarding — not a recruiter with a sourcing dashboard open all day, and certainly not a developer. That changes what a page like this owes you. The useful question is not which API methods exist; it is how much of the setup lands on your desk. The answer is: the request, the credentials, and a description of how you work today. The build is ours — no plugin to keep updated, no scripts to host, and no API documentation for anyone on your side to read. ## How the integration is set up ### Write to us and say you run BambooHR Email support@remakecv.com with your organisation name and a couple of lines on the present routine — who tidies up candidate CVs at the moment, and who reads the finished version. ### Obtain API credentials for your BambooHR account Whoever administers your account, or BambooHR's own support team, determines what credentials can be issued and on what terms. You do not need to interpret their answer — forward it to us and we will read it. ### Pass the credentials to us on a secure route We will give you one. Credentials that reach candidate and employee data deserve the same care as a password: not plain email, and not parked in an inbox several people can open. ### We build it and enable it for your organisation Our developers implement the connection against BambooHR's API and switch it on for your company. The relevant controls then appear in your RemakeCV dashboard, with nothing for your colleagues to install on their machines. > **Note:** What your finished connection can do is bounded by the API access granted on your BambooHR account — commonly reading a candidate's CV across, writing the branded version back to their record, or both. We would rather establish that with you during scoping and tell you plainly what your build covers than promise a shape before anyone has looked. ## What the workflow looks like With the connection running, the branded CV is produced as part of moving a candidate forward: 1. Applicants are reviewed and progressed in BambooHR the way your team already handles them. 2. The CV is rendered into your organisation's branded template, using the same template, editor and options as any other RemakeCV job. 3. The finished document returns to the candidate's record, where the hiring manager or interviewer collects it. Only the middle step belongs to us, so what your colleagues already know about the rest of BambooHR 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) for what happens inside it. This suits generalist HR teams for a practical reason. When formatting is occasional — a handful of candidates one month, none the next — any process resting on somebody remembering a sequence of steps quietly decays. A connection that lives on the record survives annual leave, a job share and a handover to a new starter, because there is nothing to remember. ## Does the integration change the formatting? No. Templates, editing, anonymisation, summaries and downloads behave identically whether a CV arrives over a connection or is dragged into the browser. The integration decides the route the file takes and nothing about how it looks, so adopting one never obliges you to reopen a decision about your output. If your branded template has not been designed yet, that runs as its own piece of work beside the connection — our team builds it to your organisation's brand. See [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## Building it yourself Where you do have engineering capacity to call on and would rather own the connection, the [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) exposes the processing, retrieval and template endpoints directly, on your own timetable. 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 **BambooHR** and your organisation name. We will confirm what the integration will do on your account, exactly what we need from you, and how the people who handle your hiring alongside everything else will use it. ## Frequently asked questions ### Does RemakeCV integrate with BambooHR? Yes. Our developers build and configure the BambooHR integration for your HR team using API credentials issued for your BambooHR account, and it then behaves like 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 issued for your BambooHR account, arranged by whoever administers it or by BambooHR's own support team, and a short note on who prepares candidate CVs today. Send both to support@remakecv.com. The build itself is ours, so nobody in your organisation needs development skills to get this running. ### Will it work the same as the other integrations? Yes. The same templates, editor, anonymisation, summaries and downloads apply. An integration settles only how a CV travels between systems, so the document a hiring manager opens is identical either way. ### Can I use RemakeCV with BambooHR before the integration is set up? Yes. RemakeCV runs standalone in your browser — upload a CV, format it into your branded template, download it and file it wherever it belongs. HR teams often work that way first and add the connection once they know how much formatting they actually do; it is never a prerequisite. --- # Connecting Bond Adapt > RemakeCV connects to Bond Adapt. Our team builds and configures the integration using API credentials issued for your Adapt account, so branded CVs land back on the candidate record instead of being downloaded and re-attached. Source: https://www.remakecv.com/help/integrations/bond-adapt Last updated: 2026-08-22 --- RemakeCV connects to Bond Adapt. Our team builds and configures the integration for your agency using API credentials issued for your Adapt account, after which your consultants work exactly as they do with every other RemakeCV integration — a candidate's CV goes into your branded template and the finished document lands back on their record. Email support@remakecv.com and we will scope it with you. ## How the integration is set up ### Tell us you run Bond Adapt Email support@remakecv.com with your agency name, how your Adapt instance is hosted, and a sentence or two on the way your consultants work today — where candidate CVs sit, and where the branded version needs to end up. ### Obtain API credentials for your Adapt account Ask your Adapt support contact for API access. This is an ordinary request from an existing customer, and they are the ones who can tell you what is available on your account and on what terms. ### Get the credentials to us securely We will tell you how to send them safely. Treat them the way you would treat anything that reaches candidate data — not over an unencrypted channel, and not left sitting in a shared inbox. ### We build it and switch it on Our team writes the connection against the API your account exposes and enables it for your company. The relevant options then show up in your RemakeCV dashboard, with nothing for your consultants to install or maintain. > **Note:** What the integration is able to do depends on what your Adapt account's API exposes — typically pulling a candidate's CV across, putting the branded document back on the record, or both. We confirm the precise shape when we scope the work with you, before anything is built, so there are no assumptions carried into the build. Because Adapt has been deployed in a range of ways across the agencies that run it, scoping is a real conversation rather than a form. We ask how your instance is hosted and who administers it, then work out from there what the connection should look like and where it should sit. Ownership is part of that discussion too — across our existing integrations, some connections belong to an individual consultant and some are held once for the whole company, and we would rather agree which suits your agency than default to one. For how credentials and candidate data are handled in general, see [security and sub-processors](https://www.remakecv.com/help/anonymisation-and-compliance/security-and-subprocessors.md). ## What the workflow looks like With the integration in place, getting a candidate into your house style stops being a round trip through your downloads folder: 1. Work the candidate in Adapt exactly as your team does today. 2. Their CV is formatted into your agency's branded template — same template, same editor, same options as any other RemakeCV job. 3. The finished document returns to the candidate record, ready to go out to the client. The middle step is unchanged from what your consultants already know. 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. A CV that arrives through an integration is treated identically to one dragged into the browser, so [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 over untouched. What your clients receive looks the same the day before the integration goes live and the day 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 developers or your Adapt administrator would rather hold the connection in-house, 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 the two systems together on your own schedule. See [connecting RemakeCV to any ATS or internal system](https://www.remakecv.com/help/integrations/using-the-api-instead.md). ## Which plan includes it? It is included whichever plan you are on. See [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). ## Start the conversation Email support@remakecv.com with **Bond Adapt** and your agency name. We will come back with what the integration will do on your account, what we need from your side, and how your consultants will use it day to day. ## Frequently asked questions ### Does RemakeCV integrate with Bond Adapt? Yes. Our team builds and configures the Bond Adapt integration for your agency using API credentials issued for your Adapt account. Once it is enabled it behaves like our other ATS integrations — email support@remakecv.com and we will scope it with you. ### What do I need to provide? API credentials for your Bond Adapt account, obtained through your Adapt support contact, along with a short note on how your consultants work today and how your Adapt instance is hosted. Send that to support@remakecv.com and our team handles the build. ### 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 travels between systems and nothing else — the finished document is identical either way. ### Can I use RemakeCV with Bond Adapt 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 attach it wherever you need. The integration saves the manual download-and-re-attach step; it is not a prerequisite for using RemakeCV. --- # Connecting Ceipal > RemakeCV connects to Ceipal. Our team builds and configures the integration using API credentials issued for your Ceipal account, so branded CVs arrive back on the candidate record instead of being downloaded and re-attached by hand. Source: https://www.remakecv.com/help/integrations/ceipal Last updated: 2026-08-22 --- RemakeCV connects to Ceipal. Our team builds and configures the integration for your firm using API credentials issued for your Ceipal account, and from that point it behaves like every other RemakeCV ATS integration — a candidate's CV is formatted into your branded template and the finished document is returned to their record. Email support@remakecv.com and we will scope it with you. ## How the integration is set up ### Tell us you run Ceipal Email support@remakecv.com with your firm's name and a picture of how your recruiters work today — where candidate CVs sit, who formats them, and where the branded document has to end up before it reaches a client. ### Request API credentials for your Ceipal account Ask Ceipal's support team for API access. This is a routine request from an existing customer, and they will tell you what can be issued for your account and on what terms. ### Get the credentials to us securely We will point you at a safe way to send them. Treat them like any other credential that reaches candidate data — not over an unencrypted channel, and not left sitting in a shared inbox. ### We build it and turn it on Our team implements the connection against Ceipal's API and enables it for your company. The relevant options then appear in your RemakeCV dashboard, with nothing for your recruiters to install or maintain. > **Note:** What the finished integration does depends on what Ceipal's API exposes to your account — commonly pulling a candidate's CV across, writing the branded document back onto their record, or both. We confirm the precise shape when we scope it with you, before any build work starts, so you know what you are getting rather than what we assume. 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 ATS-side permissions and audit trails attached to the person who acted. Which of those suits you depends on how your Ceipal account is organised and how you want permissions to sit, and we will agree it with you rather than pick for you. Our approach to credentials and candidate data generally is set out in [security and sub-processors](https://www.remakecv.com/help/anonymisation-and-compliance/security-and-subprocessors.md). ## What the workflow looks like With the integration live, the manual round trip in the middle of your day disappears: 1. Work the candidate in Ceipal the way your team already does. 2. Their CV is formatted into your firm's branded template, using the same template, editor and options as any other RemakeCV job. 3. The finished document lands back on the candidate record, ready to go out to the client or the account manager. The parts your recruiters actually touch are unchanged — 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) for what happens between those steps. ## Does the integration change the formatting? No. Templates, editing, anonymisation, summaries and downloads behave identically whether a CV arrives over an integration or is dragged into the browser. The connection decides how the document moves between systems and nothing more, so switching one on never means revisiting your output — [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 over untouched. If your branded template has not been built with us yet, that work 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 Ceipal 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 those endpoints cover. ## Which plan includes it? Neither plan treats integrations as an extra. See [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). ## Start the conversation Email support@remakecv.com with **Ceipal** and your firm's name. We will come back to you on what the integration will do for your account, what we need from you, and how your recruiters will use it day to day. ## Frequently asked questions ### Does RemakeCV integrate with Ceipal? Yes. Our team builds and configures the Ceipal integration for your firm using API credentials issued for your Ceipal account. Once it is enabled it behaves like our other ATS integrations, formatting a candidate's CV into your branded template and returning it to their record. Email support@remakecv.com to begin. ### What do I need to provide? Two things: API credentials for your Ceipal account, which Ceipal's support team issues to you as an existing customer, 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 only how a document travels between systems, so the CV your client receives is identical either way. ### Can I use RemakeCV with Ceipal before the integration is set up? Yes. RemakeCV runs standalone in the browser — upload a CV, format it into your branded template, download the result and attach it wherever you need it. The integration saves that round trip; it is not a condition of using RemakeCV. --- # Connecting Crelate > RemakeCV connects to Crelate. Our team builds the connection from API credentials issued on your Crelate account, so candidates leave your desk in your house template or in the format a particular client insists on. Source: https://www.remakecv.com/help/integrations/crelate Last updated: 2026-08-22 --- RemakeCV connects to Crelate. Our team builds the connection for your firm from API credentials issued on your Crelate account, and it then behaves like every RemakeCV integration — a candidate's CV becomes a branded document, in your house template or in a client-specific variant of it, and returns to their record. Write to support@remakecv.com with Crelate in the subject line and we will take it from there. ## Why specialist firms ask for this Crelate tends to be run by smaller staffing and search firms — a few consultants working a defined vertical, where the business rests on a short list of client companies rather than an open market. When you submit to the same eight or ten clients repeatedly, the format each one expects becomes part of the account relationship. One requires their own letterhead under a preferred-supplier agreement. Another sifts blind and will not take a name on the first page. A third wants the CV by itself, cover sheet removed. Kept up by hand that is a small tax on every submission, and an occasional embarrassment when the wrong version goes out. It is also precisely the situation [template variants](https://www.remakecv.com/help/templates-and-branding/template-variants.md) exist for. ## Working to each client's format A variant is a complete version of your template for one situation: a client's branding reproduced as they specify it, an anonymised layout, a build with no cover page. Consultants pick the right one while the CV is processed, and there is no cap on how many you keep. Where an account is worked by one or two people, ask us to scope that client's variant to them. > **Tip:** Name variants after the client or the situation, never after the design. Under submission pressure, the wording in that dropdown is the only thing standing between the right document and the wrong recipient. Everything a variant covers survives the connection intact — which matters more than any of the setup detail below. Linking Crelate removes a file-shuffling step; it does not narrow which version of your template a consultant can reach for. ## Setting the connection up ### Describe your desk to us Email support@remakecv.com with your firm's name and a short account of how a candidate gets from Crelate to a client today, including which clients need their own format. ### Obtain API credentials on your Crelate account Crelate's support team issues these to you as their customer and will tell you what your account can be granted. Whatever they allow is what we have to build against. ### Hand the credentials over on a secure channel Ask us for one first. Anything reaching candidate records deserves password-grade handling — not plain email, and not parked in a thread that outlives the project. ### We build it and switch it on centrally Our team writes the connection and enables it for your company, after which the relevant controls appear in your dashboard. Individual consultants install nothing. > **Note:** What can be built is bounded by the API access Crelate grants your account — usually retrieving a candidate's CV, filing the finished document back against them, or both. We put that scope in writing with you before any code is written rather than assuming it. The same conversation settles whether the connection is held once for the firm or made by each consultant. On credential and candidate-data handling generally, see [security and sub-processors](https://www.remakecv.com/help/anonymisation-and-compliance/security-and-subprocessors.md). ## Where the CV goes, and what it looks like 1. Consultants carry on running candidates through Crelate as they do today. 2. The CV is rendered into whichever version your client expects, through the usual editor and options. 3. The finished file returns to the candidate's record, on hand when the submission goes out. Formatting is untouched by any of this. [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 the editor behave the same whether a CV came over the connection or was dragged into the browser: a connection governs the file's journey and nothing about the document itself. If the underlying template has not been designed yet, that build runs alongside — see [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## Building it yourself instead Crelate not appearing on our live list changes nothing about whether it can be connected: we build against whatever platform a firm actually runs, from credentials that platform issues. If you would rather own the code, the [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) exposes 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). ## Plans, and how to open the conversation Integrations come with Business and with Enterprise, on the same terms — see [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). To start, email support@remakecv.com with **Crelate**, your firm's name and the client formats you would want covered first. We will come back with what the connection can do on your account and what we need from you. ## Frequently asked questions ### Does RemakeCV integrate with Crelate? Yes. Our team builds the Crelate connection for your firm from API credentials issued on your Crelate account, and it then behaves like the RemakeCV integrations already running elsewhere. Write to support@remakecv.com with Crelate in the subject line to begin. ### What do I need to provide? Two things: API credentials issued on your Crelate account, which Crelate's support team arranges for you as their customer, and a short account of how a candidate currently travels from Crelate to a client. Send both to support@remakecv.com and our team does the build. ### Will it work the same as the other integrations? Yes. The same templates, client-branded variants, editor, anonymisation, summaries and downloads apply. A connection decides only how a CV travels between two systems — the document your client opens is identical either way. ### Can I use RemakeCV with Crelate before the integration is set up? Yes. RemakeCV runs standalone in the browser — upload a CV, format it into your template, anonymise it if the client sifts blind, and download it. Small teams often work this way for months and add the connection later; it was never a prerequisite. --- # 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. --- # Connecting Firefish > RemakeCV connects to Firefish. Our team builds the integration from API credentials issued on your Firefish account, so the CV your client opens carries the same branding as everything else your agency puts in front of them. Source: https://www.remakecv.com/help/integrations/firefish Last updated: 2026-08-22 --- RemakeCV connects to Firefish. Our team builds the integration for your agency from API credentials issued on your Firefish account, so a candidate's CV can be pulled through, rebuilt in your branded design and filed back against their record without anyone downloading a file. Write to support@remakecv.com to open the conversation. ## The CV is the last mile of your candidate marketing Firefish tends to be chosen by small and mid-sized UK agencies that take attraction seriously — the ones running their own careers site, their own campaigns and their own tone of voice rather than leaving a job board to speak for them. If that describes your agency, you have already accepted the argument this page rests on: how something is presented changes how it is received. The client-facing CV is where that argument gets its final test. Everything upstream is aimed at the candidate. The formatted CV is aimed at the person deciding whether to interview, and it is often the only artefact of yours they open all week. An agency that has spent real money looking deliberate everywhere else has an obvious reason not to send that document out in whatever shape the candidate happened to write it in. ## What it looks like on the desk Agencies of this size rarely have a spare person for admin, so what a connection buys you is that formatting stops being a separate errand: 1. A consultant works the candidate in Firefish as they always have. 2. The CV passes through RemakeCV and comes back in your house design, with the same editor and the same options your team already uses in the browser. 3. The branded version is filed against the candidate, ready for the client. The middle step is simply the product — 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). What goes away is the manual handling either side of it. ## Getting it built for your agency > **Note:** Firefish is a connection our team builds on request rather than one you switch on from a list — and that offer is not limited to the platforms named on this site, so if your agency also runs another CRM or an internal system, say so. How far any given connection reaches is set by the API access your own account is granted, commonly reading a candidate's CV, writing the branded copy back, or both. We put the scope in writing with you before a line of it is built. ### Tell us how your desk runs Email support@remakecv.com with your agency name and a few lines on where CVs sit today, who formats them, and where the branded copy has to end up. ### Ask Firefish for API access on your account Their support team decides what credentials your account can be issued and on what terms. Their answer is what we build against. ### Hand the credentials over on a channel that is safe We will point you at one. Anything that reaches candidate data deserves the care you would give a password — not plain email, and not left in a thread someone forwards on months later. ### We build it, then turn it on Our team writes the implementation and enables it for your company, after which the relevant controls appear in your RemakeCV dashboard. Nobody installs anything and there is no plug-in to keep current, which matters when there is no in-house IT to look after it. We will ask early whether the connection should be held once for the whole agency or made by each consultant individually. Small teams usually prefer the former, but it is your call rather than our default. [Security and sub-processors](https://www.remakecv.com/help/anonymisation-and-compliance/security-and-subprocessors.md) covers how credentials and candidate data are held. ## Formatting is unaffected Nothing about the output shifts because a CV arrived over a connection instead of by drag and drop. The template, the editor, [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 behave as they do now. A connection settles how the file travels and has no say in what it looks like, so taking one on never means reopening a design your clients already recognise. If that design does not exist yet, our team builds it to your brand — see [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). Agencies with strong attraction branding usually want the CV to sit alongside the rest of it rather than merely near it, and this is the point at which to say so. ## Or wire it up yourself Where you have a developer — in-house, or the freelancer who looks after your website — the [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) hands them the processing, retrieval and template endpoints directly. [Connecting RemakeCV to any ATS or internal system](https://www.remakecv.com/help/integrations/using-the-api-instead.md) sets out what those cover. ## Plans, and what happens next Business and Enterprise subscriptions both include integrations, so nothing here is held back for the larger plan — see [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). Email support@remakecv.com with **Firefish** and your agency name, and we will come back to you on what the connection can do on your account, what we need from you, and how it will feel to the consultants using it. ## Frequently asked questions ### Does RemakeCV integrate with Firefish? Yes. A Firefish connection is one our team builds for your agency from API credentials issued on your Firefish account, and it then works like the other ATS and CRM connections we run. Write to support@remakecv.com with your agency name to open the conversation. ### What do I need to provide? Two things: API credentials for your Firefish account, which you request from Firefish's support team as their customer, and a short description of how your consultants handle candidate CVs today. Send both to support@remakecv.com and the build is ours to do from there. ### Will it work the same as the other integrations? Yes. Your template, the editor, anonymisation, candidate summaries and downloads are untouched by how a CV reached RemakeCV. A connection decides only the route the file takes between two systems, so the document your client opens is the same either way. ### Can I use RemakeCV with Firefish before the integration is set up? Yes. RemakeCV works on its own in a browser — upload a CV, format it into your branded design, download it and attach it wherever you like. Plenty of agencies work that way for months first. The connection removes a manual step; it is not a condition of using RemakeCV. --- # Connecting Greenhouse > RemakeCV connects to Greenhouse. Our team builds and configures the integration from API credentials issued for your Greenhouse account, so every candidate reaches your hiring managers in one consistent branded format. Source: https://www.remakecv.com/help/integrations/greenhouse Last updated: 2026-08-22 --- RemakeCV connects to Greenhouse. Our team builds and configures the integration for your talent team using API credentials issued for your Greenhouse account, after which it behaves like every other RemakeCV ATS integration — format a candidate's CV into your branded template and return the finished document to their record. Email support@remakecv.com and we will scope it with you. ## Why in-house teams ask for this Greenhouse sits mostly with internal talent acquisition teams rather than staffing agencies, and that changes what a formatting integration is for. You are not packaging a candidate to win a client — you are handing a shortlist to a hiring manager and an interview panel who have to compare four people fairly, often in a rush, often on a phone between meetings. CVs that arrive in four different layouts make that harder than it needs to be. One house format puts the same information in the same place every time, and it carries your employer brand into a document the candidate's own work is being judged on. That is the value here: internal comparability first, presentation second. ## How the integration is set up ### Tell us Greenhouse is where your hiring runs Email support@remakecv.com with your organisation name and a short picture of the current path — who prepares candidate CVs, and how they reach the hiring manager today. ### Arrange API access on your Greenhouse account Your Greenhouse administrator, or their support team, decides what credentials can be issued and under what terms. Their answer defines what we have to build against. ### Send the credentials over securely We will point you to a safe channel. Anything that touches applicant records deserves the same handling as a password — not plain email, and not left in a shared inbox. ### We build the connection and enable it Our team implements it against Greenhouse's API and switches it on for your company. The relevant controls then appear in your RemakeCV dashboard, with nothing for individual recruiters or coordinators to install. > **Note:** How much the integration can do is set by the API access your Greenhouse account is granted — commonly pulling a candidate's CV across, placing the branded version back on their record, or both. We agree that scope with you during the scoping conversation, before any code is written, rather than assuming it. ## What the workflow looks like With the connection in place, producing a panel-ready CV becomes part of moving the candidate along rather than a separate errand: 1. Your recruiters and coordinators keep progressing candidates in Greenhouse as they do today. 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 record, where the hiring manager and the interview panel find it. The middle step is untouched, so anything your team already knows about RemakeCV still holds. 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). One thing worth raising early: whether the connection is held once centrally or made by each user individually. In-house teams often have strong opinions here, because it affects how permissions and audit trails line up on the ATS side. We settle it with you rather than choosing for you. ## Does the integration change the formatting? No. Templates, editing, anonymisation, summaries and downloads behave the same whether a CV arrives over a connection or is dragged into the browser. An integration only governs the journey the file takes, which means adopting one never forces a review of your output. [Auto-anonymisation](https://www.remakecv.com/help/anonymisation-and-compliance/auto-anonymisation.md) matters more to in-house teams than most — it is what lets you run a blind first sift without maintaining two versions of every CV by hand. It carries over untouched, as do [candidate summaries](https://www.remakecv.com/help/ai-tools/candidate-summaries.md). If your branded template does not exist yet, our team builds it to your design alongside the connection: see [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## Building it yourself Where you have internal engineering capacity and would rather own the connection, the [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) exposes 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) for what they cover. ## Which plan includes it? It is included whichever plan you are on. See [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). ## Start the conversation Email support@remakecv.com with **Greenhouse** and your organisation name. We will confirm what the integration will do on your account, what we need from you, and how your talent team will use it day to day. ## Frequently asked questions ### Does RemakeCV integrate with Greenhouse? Yes. Our team builds and configures the Greenhouse integration for your talent team using API credentials issued for your Greenhouse account, and it then behaves like our other ATS integrations. Email support@remakecv.com and we will scope it with you. ### What do I need to provide? API credentials issued for your Greenhouse account, which your own Greenhouse administrator or their support team arranges, plus a short description of how candidates currently reach your hiring managers. Send both to support@remakecv.com and our team handles the build. ### Will it work the same as the other integrations? Yes. The same templates, editor, anonymisation, summaries and downloads apply. An integration decides how a CV moves between systems and nothing else — the document your interview panel opens is identical either way. ### Can I use RemakeCV with Greenhouse before the integration is set up? Yes. RemakeCV runs standalone in your browser — upload a CV, format it into your branded template, download it and file it wherever you need. Many talent teams start this way and add the connection later; it is not a prerequisite. --- # Connecting iCIMS > RemakeCV connects to iCIMS. Our team builds and configures the integration from API credentials issued for your iCIMS account, so branded candidate documents reach the record without anyone leaving the system. Source: https://www.remakecv.com/help/integrations/icims Last updated: 2026-08-22 --- RemakeCV connects to iCIMS. Our team builds and configures the integration for your talent function using API credentials issued for your iCIMS account, after which it behaves like every other RemakeCV ATS integration — format a candidate's CV into your branded template and return the finished document to their record. Email support@remakecv.com and we will scope it with you. ## Who is usually in the room iCIMS tends to sit at the centre of a large talent acquisition organisation, and that changes the shape of the conversation. Recruiting rarely owns the decision alone. An internal IT or HRIS team usually administers the account and decides what API access can be issued; information security wants to know where candidate data travels and under what contract. None of that is an obstacle — it is simply the process, and we plan around it. So bring your HRIS contact to the first call if you can. They will know what your iCIMS account is able to issue, which is the fact that determines everything downstream. ## How the integration is set up ### Introduce us to the systems owner Email support@remakecv.com with your organisation name, and say who administers your iCIMS account. We will work with whoever that is, alongside your talent function. ### Establish what API access can be issued Your iCIMS administrator or their support team determines the credentials available to your account and the terms attached. Their answer defines what we build against, so it comes first. ### Hand the credentials over securely We will nominate a safe channel. Anything that reaches applicant records deserves password-grade handling — never plain email, never a thread with the whole project team copied in. ### We build it and switch it on Our team implements the connection and enables it for your company. The relevant controls appear in your RemakeCV dashboard, with no desktop software and nothing for individual recruiters to install. > **Note:** How far the integration reaches is decided by the API access your iCIMS account is granted — commonly collecting a candidate's CV, placing the branded version back on their record, or both. We agree that scope with you in writing during scoping, before any code is written. ## What your security review will need Because this conversation usually reaches an information security team, here are the points they ask about first. AI processing runs on **OpenAI under an enterprise agreement with zero data retention**. Candidate data is not retained by OpenAI once your request has been processed, and it is contractually excluded from model training. **EU data residency is available on request** — say the word and we configure it for your account. A signed Data Processing Agreement is available from support@remakecv.com, along with the current sub-processor list. The rest — encryption, access control, two-factor authentication, how API keys are stored and revoked — is set out in [security, DPAs and sub-processors](https://www.remakecv.com/help/anonymisation-and-compliance/security-and-subprocessors.md). Send your reviewers straight there. ## What the workflow looks like Once the connection is live, the branded document is produced where hiring already happens: 1. Your recruiters and coordinators progress candidates in iCIMS as they do today. 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 record, where the hiring manager and interview panel find it. Ownership of the connection is settled at scoping rather than assumed. Some of our integrations are held once at company level; others belong to each user, which keeps ATS-side permissions and audit trails attached to the person who acted. In a large talent function that distinction matters, so we put it on the agenda. ## Does the integration change the formatting? No. Templates, editing, anonymisation, summaries and downloads behave identically whether a CV arrives over a connection or is dragged into the browser. Transport is the only thing an integration decides, so adopting one never obliges you to revisit your output — useful when the template has already been signed off by a brand team. Where the branded template has yet to be designed, that runs as its own workstream: our team builds it to your organisation's brand and the connection then delivers it. See [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## Building it yourself Large organisations often have engineering capacity in-house. The [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) exposes the processing, retrieval and template endpoints directly, so your own team can wire RemakeCV into iCIMS on its own release schedule — see [connecting RemakeCV to any ATS or internal system](https://www.remakecv.com/help/integrations/using-the-api-instead.md). ## 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 **iCIMS** and your organisation name. Tell us who administers the account and whether a security review is expected, and we will confirm what the integration will do, what we need from you, and what your reviewers will want to see. ## Frequently asked questions ### Does RemakeCV integrate with iCIMS? Yes. Our team builds and configures the iCIMS integration for your organisation using API credentials issued for your iCIMS account, and it then behaves like our other ATS integrations. Email support@remakecv.com and we will scope it with you. ### What do I need to provide? API credentials issued for your iCIMS account, which your own iCIMS administrator or their support team arranges, plus a short description of how candidate documents move through your talent function today. Send both to support@remakecv.com and our team takes on the build. ### Will it work the same as the other integrations? Yes. The same templates, editor, anonymisation, summaries and downloads apply. An integration governs only where a CV is collected from and where the finished document is placed; the output itself is identical either way. ### Can I use RemakeCV with iCIMS 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. Large organisations often begin this way while procurement and security review run in parallel, then add the connection afterwards. --- # 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. --- # Connecting Lever > RemakeCV connects to Lever. Our team builds and configures the integration from API credentials issued for your Lever account, so the branded candidate document sits on the record where your whole hiring panel can read it. Source: https://www.remakecv.com/help/integrations/lever Last updated: 2026-08-22 --- RemakeCV connects to Lever. Our team builds and configures the integration for your talent team using API credentials issued for your Lever account, and once it is enabled it behaves like every other RemakeCV ATS integration — turn a candidate's CV into your branded document and return the finished file to their record. Email support@remakecv.com and we will scope it with you. ## How the integration is set up ### Tell us Lever is where your hiring lives Email support@remakecv.com with your organisation name and a short account of how your talent team works today — where candidate CVs sit, and who needs to read the branded version once it exists. ### Ask Lever for API access on your account Lever's own support team decides what access they can grant and on what basis. Asking is ordinary account administration, and their answer tells us what we have to build against. ### Send the credentials across securely We will point you to a safe channel. Anything that reaches candidate records deserves the care you would give a password — not plain email, and not a thread with half the department on it. ### We build the connection and turn it on Our team implements it against Lever's API and enables it for your organisation. The relevant controls then appear in your RemakeCV dashboard, and there is nothing for individual recruiters or interviewers to install. > **Note:** What the connection is able to do is governed by whatever Lever's API makes available on your account — commonly reading a candidate's existing CV, writing the branded document back onto their record, or both. We pin that down with you during scoping, so the shape of the build is agreed rather than assumed on either side. ## What the workflow looks like Once your integration is live, the branded CV arrives where your hiring team is already working: 1. Source, screen and progress the candidate in Lever as usual. 2. Their CV is rendered into your organisation's branded document — the same template, the same editor and the same options as any other RemakeCV job. 3. The finished file returns to the candidate's record, where everyone involved in the decision opens the same version. The third point is where a talent team running a collaborative process gets most of the value. A CV that goes out to a client is sent once and read once. A CV inside your own hiring process is opened again and again by different people at different points in the week — whoever screened the candidate, the hiring manager drafting questions, an interviewer skimming it twenty minutes beforehand, someone writing up notes afterwards. All of them should be looking at the same file. Keeping the branded version on the candidate's record, rather than in one person's inbox, means nobody quotes a line the next interviewer cannot find, and nobody is left reading the raw original because the tidied copy was never circulated to them. Teams that anonymise CVs for a first sift get the same behaviour through the integration as they 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) for what happens between steps one and three. ## Does the integration change the formatting? No. Templates, editing, anonymisation, summaries and downloads behave identically whether a CV arrives over an integration or is dragged into the browser. All the connection does is carry the file in and out, so switching one on never means reopening any decision about your output — what your panel reads is the same before and after. If your branded document has not been designed yet, that runs as its own piece of work alongside the integration: our team builds the template to your organisation's own brand, and the connection then delivers it. See [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## Building it yourself If your own engineers would rather own 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 Lever on your own schedule and to your own design. 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? Integration work is part of both plans rather than an upgrade. See [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). ## Start the conversation Email support@remakecv.com with **Lever** and your organisation name. We will confirm what the integration will do on your account, what we need from you, and how your recruiters and interviewers will use it day to day. ## Frequently asked questions ### Does RemakeCV integrate with Lever? Yes. Our team builds and configures the Lever integration for your organisation using API credentials issued for your Lever account, and it then behaves like our other ATS integrations. Email support@remakecv.com and we will scope it with you. ### What do I need to provide? API credentials issued for your Lever account, which you request from Lever's own support team, together with a short account of how your talent team works today and who reads the finished CV. Send both to support@remakecv.com and our team takes on the build. ### Will it work the same as the other integrations? Yes. The same templates, editor, anonymisation, summaries and downloads apply. An integration decides only where the CV comes from and where it goes afterwards; what comes out the other end is unchanged. ### Can I use RemakeCV with Lever before the integration is set up? Yes. RemakeCV runs standalone in the browser — upload a CV, format it into your branded document, download it and attach it wherever you need. The integration takes the manual step out of that; it is not a condition of using RemakeCV. --- # Connecting Loxo > RemakeCV connects to Loxo. Our team builds the connection from API credentials issued on your Loxo account, so the mixed bag of documents a sourced shortlist produces comes back to each record as one branded CV. Source: https://www.remakecv.com/help/integrations/loxo Last updated: 2026-08-22 --- RemakeCV connects to Loxo. Working from API credentials issued on your Loxo account, our team builds and configures the connection for your firm, so a sourced candidate's CV can be rebuilt in your branded template and filed back against them without leaving the record. Write to support@remakecv.com and we will work out the shape of it together. ## Sourcing-led search has a CV problem Loxo tends to sit with teams who build a shortlist outwards rather than wait for one to arrive. Names are researched, approached and talked round; applications are the exception. That changes the raw material. Somebody who applied for a job sends a document tidied up for the occasion. Somebody you found and persuaded sends whatever exists — a file last touched three roles ago, or a PDF exported from a professional profile. None of that reflects on the candidate, but all of it lands on whoever prepares the submission, and it lands late, when the client is already waiting. Turning four documents of four different provenances into one comparable set is the least interesting hour in a search. It is the hour this connection is aimed at. ## What changes day to day Your researchers and consultants stay in Loxo. When a candidate is ready to go out, the CV held against them is rebuilt in your firm's design and filed back where it came from, so the record becomes what you submit from. [Adding information that was not on the original CV](https://www.remakecv.com/help/formatting-cvs/adding-missing-information.md) earns more here than on an inbound desk — availability, package, what would actually move them — because that came out of your conversation and was never going to be in the file they sent. The middle of it is ordinary RemakeCV: 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). > **Note:** How much the connection can carry is decided by the API access granted on your Loxo account rather than by us — often reading a candidate's CV across, often writing the branded version back, sometimes both. We put that scope in writing during the scoping conversation, before anyone writes code, and the same conversation settles whether the connection is held once for the firm or made by each user. ## Setting it up ### Tell us Loxo is where your search runs Email support@remakecv.com with your firm's name and a short picture of the current path — who prepares candidate documents today, and what a client receives at the end of it. ### Arrange API access on your Loxo account Loxo decides what credentials can be issued to you and on what terms. Their answer draws the boundary of what we are able to build against, so it is worth asking early. ### Get the credentials to us on a secure channel We will point you at one. Anything reaching candidate data deserves the handling you would give a production secret: not plain email, and not left in a shared inbox. ### We build it, then switch it on Our team implements the connection and enables it for your company. The controls appear in your RemakeCV dashboard, so there is nothing for a researcher or consultant to install. ## Formatting is identical either way A connection governs how a file travels and nothing beyond that. Your template, the editor, anonymisation, summaries and downloads all work as they do when someone drags a CV into the browser, so adopting one never reopens a decision about your output. Two features earn their keep on sourced candidates in particular. [Neutralising first-person language](https://www.remakecv.com/help/anonymisation-and-compliance/first-person-neutralisation.md) evens out CVs written in wildly different voices, which is the usual state of a researched shortlist. And [checking what was extracted](https://www.remakecv.com/help/formatting-cvs/checking-the-extraction.md) is worth the glance on profile exports and scans, where the source was never meant to be read by anything but a human. If your firm's design has not been built with us yet, our team builds it from your own document — see [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## If you would rather build it yourself The platforms with pages here are the ones we are asked about most, not the limit of what we will connect to; if your firm runs something else, including an in-house system, our team builds against whatever credentials that provider issues. Where you have engineers of your own, the [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) exposes 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). ## Plans, and where to start There are two plans, Business and Enterprise, and integration work is included on both — [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md) sets out how they differ otherwise. To begin, email support@remakecv.com with **Loxo** and your firm's name. We will come back with what the connection can do on your account, what we need from you, and how a consultant will use it. ## Frequently asked questions ### Does RemakeCV integrate with Loxo? Yes. Our team builds and configures the Loxo connection for your firm from API credentials issued on your Loxo account, and it then behaves like the rest of our ATS connections. Write to support@remakecv.com and we will work out the shape of it together. ### What do I need to provide? Two things: API credentials issued on your Loxo account, which Loxo arranges for you as an existing customer, and a short picture of how a candidate currently gets from your researchers to a client-ready document. Send both to support@remakecv.com and our team takes the build from there. ### Will it work the same as the other integrations? Yes. Your templates, the editor, anonymisation, summaries and downloads are all untouched by it. A connection settles how a CV travels between two systems and decides nothing about the document itself. ### Can I use RemakeCV with Loxo before the integration is set up? Yes. RemakeCV runs on its own in a browser — upload a sourced candidate's CV, rebuild it in your branded template, download it and send it on. Search firms often start that way and add the connection once the design is settled; it was never a prerequisite. --- # Connecting Manatal > RemakeCV connects to Manatal. Our team builds and configures the integration from API credentials issued for your Manatal account, so the branded CV lands back on the candidate record instead of passing through a manual download. Source: https://www.remakecv.com/help/integrations/manatal Last updated: 2026-08-22 --- RemakeCV connects to Manatal. The integration is built and configured by our team using API credentials issued for your Manatal account, and once it is switched on it behaves like every other RemakeCV ATS integration — format a candidate's CV into your branded template and return the finished document to their record. Email support@remakecv.com and we will scope it with you. ## How the integration is set up ### Tell us Manatal is your system of record Email support@remakecv.com with your company name and a sketch of how your recruiters work today — where candidate CVs sit, and where the branded version needs to end up once it exists. ### Ask Manatal for API access on your account Manatal's own support team decides what credentials they can issue and on what terms. It is a normal request to make as a paying customer, and their answer tells us what we have to work with. ### Hand the credentials over on a secure channel We will point you to a safe way to send them. Anything that reaches candidate records deserves the same care as a password — never in plain email, and never in a shared inbox thread. ### We build the connection and switch it on Our team implements it against Manatal's API and enables it for your company. The relevant controls then appear in your RemakeCV dashboard, with nothing for individual recruiters to install. > **Note:** What the integration can do is governed by what Manatal's API exposes to your account — commonly pulling a candidate's CV across, putting the branded document back onto their record, or both. We pin that down with you during scoping, before any code is written, so the shape of the thing is agreed rather than assumed. It is worth being plain about the sequence. A Manatal connection is built to order: your email is the trigger, the credentials Manatal issues you are the input, and the scoping conversation happens before the build rather than after it. That is the same route every integration we run has taken, and it is routine work for our team — see the [integrations overview](https://www.remakecv.com/help/integrations/integrations-overview.md) for the ones already live and how they are configured. ## What the workflow looks like Once your integration is live, getting a candidate into your house template stops involving the file system at all: 1. Source and progress the candidate in Manatal exactly as your team does now. 2. Their CV is rendered into your agency's branded template — the same template, the same editor and the same options as any other RemakeCV job. 3. The finished document goes back onto the candidate record, ready to go out to your client. The middle step is untouched by the integration, so anything your recruiters 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). One detail we settle during scoping is who the connection belongs to. Some of our integrations are held once for the whole company and some are made by each recruiter individually, which changes how permissions and audit trails sit on the ATS side. Which arrangement suits you depends on how your Manatal account is organised, and we will agree it with you rather than pick for you. ## Does the integration change the formatting? No. Templates, editing, anonymisation, summaries and downloads behave identically whether a CV arrives over an integration or is dragged into the browser. The integration is a transport layer and nothing more, so adopting one never means revisiting your output — the CVs your clients receive read exactly the same before and after. If your branded template has not been built yet, that runs as its own piece of work alongside the integration: our team builds it to your design, and the connection then delivers it. 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 own 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 Manatal on your own schedule and to your own design. 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? Neither plan treats integrations as an extra. See [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). ## Start the conversation Email support@remakecv.com with **Manatal** and your company name. We will confirm what the integration will do on your account, what we need from you, and how your recruiters will use it day to day. ## Frequently asked questions ### Does RemakeCV integrate with Manatal? Yes. Our team builds and configures the Manatal integration for your company using API credentials issued for your Manatal account, and it then behaves like 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 issued for your Manatal account, which you request from Manatal's own support team as a paying customer, and a short description of how your recruiters work today. Send both to support@remakecv.com and our team handles the build. ### 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 travels between systems and nothing else — the finished document is identical either way. ### Can I use RemakeCV with Manatal before the integration is set up? Yes. RemakeCV runs standalone in your browser — upload a CV, format it into your branded template, download it and attach it wherever you like. The integration removes the manual download-and-re-attach step; it is not a condition of using RemakeCV. --- # Connecting Recruit CRM > RemakeCV connects to Recruit CRM. Our team builds and configures the integration using API credentials from Recruit CRM, so branded CVs reach the candidate record without anyone downloading and re-attaching a file. Source: https://www.remakecv.com/help/integrations/recruit-crm Last updated: 2026-08-22 --- RemakeCV connects to Recruit CRM. Our team builds and configures the integration for your agency using API credentials issued by Recruit CRM, after which it behaves like every other RemakeCV ATS integration — format a candidate's CV into your branded template and send the finished document back to their record. Email support@remakecv.com to begin. ## How the integration is set up ### Tell us you run Recruit CRM Email support@remakecv.com with your agency name and a short description of your current process — where candidate CVs are held, and where the branded version needs to land once it has been formatted. ### Request API credentials from Recruit CRM Ask Recruit CRM's support team for API access on your account. This is an ordinary request for an existing customer, and they will tell you what they can issue and on what terms. ### Send the credentials to us securely We will tell you how to pass them to us safely. Treat them as you would any credential that reaches candidate data, and never send them over an unencrypted channel. ### We build and enable it Our team implements the connection against Recruit CRM's API and switches it on for your company. The relevant options then appear in your RemakeCV dashboard, with nothing for your recruiters to install or maintain. > **Note:** What the integration can do depends on what Recruit CRM's API exposes to your account — typically pulling a candidate's CV across, putting the branded document back on their record, or both. We confirm exactly what your integration will do when we scope it with you, before any build work begins. ## What the workflow looks like Once the integration is live, turning a raw CV into a client-ready one stops involving your desktop at all: 1. Work the candidate in Recruit CRM the way your team already does. 2. Their CV is formatted into your agency's branded template — the same template, the same editor and the same options as every other RemakeCV workflow. 3. The finished document goes back onto the candidate record, ready to send on to your client. Nothing about the formatting step itself changes. 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) for what happens in the middle. Whether the connection belongs to each recruiter individually or to your company as a whole is something we settle at scoping, alongside the rest of the shape — different platforms suit different arrangements, and the [integrations overview](https://www.remakecv.com/help/integrations/integrations-overview.md) shows how the live ones are set up. Until yours is enabled, your team can format Recruit CRM candidates in the browser exactly as they would any other CV. ## Does the integration change the formatting? No. Templates, editing, anonymisation, summaries and downloads behave identically whether a CV arrives through an integration or a drag-and-drop upload in the browser. An integration governs only how the document travels between systems, so your agency can take one on without reviewing anything about your output — the CVs your clients open look the same before and after. ## Building it yourself If your own developers would rather own 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 Recruit CRM on your own schedule and to your own design. See [connecting RemakeCV to any ATS or internal system](https://www.remakecv.com/help/integrations/using-the-api-instead.md) for what those endpoints cover. ## Which plan includes it? Every plan includes integration work, Business and Enterprise both. See [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). ## Start the conversation Email support@remakecv.com with **Recruit CRM** and your agency name. We will confirm what the integration will do on your account, what we need from you, and how your recruiters will use it day to day. ## Frequently asked questions ### Does RemakeCV integrate with Recruit CRM? Yes. Our team builds and configures the Recruit CRM integration for your agency using API credentials issued by Recruit CRM. Once it is enabled it behaves like our other ATS integrations — email support@remakecv.com to begin. ### What do I need to provide? API credentials for your Recruit CRM account, which Recruit CRM issues to you as an existing customer, together with a short note on how your recruiters work today. Send both to support@remakecv.com and our team handles the build. ### Will it work the same as the other integrations? Yes. The same templates, editor, anonymisation, summaries and downloads apply. An integration changes only how a CV moves between systems — the formatted document your client receives is identical either way. ### Can I use RemakeCV with Recruit CRM before the integration is set up? Yes. RemakeCV runs standalone in your browser — upload a CV, format it into your branded template, download it. The integration saves the manual download-and-re-attach step; it is not something you have to wait for. --- # Connecting RecruiterFlow > RemakeCV connects to RecruiterFlow. Our team builds and configures the integration using API credentials from RecruiterFlow, so formatted CVs land back on the candidate record without a manual download. Source: https://www.remakecv.com/help/integrations/recruiterflow Last updated: 2026-08-22 --- RemakeCV connects to RecruiterFlow. Our team builds and configures the integration for your agency using API credentials issued by RecruiterFlow, after which it works like every other RemakeCV ATS integration — format a candidate's CV into your branded template and send the finished document back to their record. Email support@remakecv.com to start. ## How the integration is set up ### Tell us you run RecruiterFlow Email support@remakecv.com with your agency name and how your team works today — where candidate CVs live, and where the formatted document needs to end up. ### Request API credentials from RecruiterFlow Ask RecruiterFlow's support team for API access on your account. This is a standard request for an existing customer, and they will tell you exactly what they can issue. ### Send the credentials to us securely We will tell you how to get them to us safely. Treat them as you would any credential with access to candidate data — never over an unencrypted channel. ### We build and enable it Our team implements the connection against RecruiterFlow's API and enables it for your company. The relevant options then appear in your RemakeCV dashboard. > **Note:** The exact capabilities depend on what RecruiterFlow's API exposes to your account — typically retrieving a candidate's CV, attaching the formatted document back to their record, or both. We will confirm precisely what your integration will do when we scope it, before any work starts. ## What the workflow looks like Once the integration is live, formatting a candidate CV stops being a download-and-re-attach job: 1. Work the candidate in RecruiterFlow as you do now. 2. Their CV is formatted into your agency's branded template — the same template, editor and options as every other RemakeCV workflow. 3. The finished document goes back onto the candidate record, ready to send to your client. Everything else is unchanged. 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 arrives through an integration or a drag-and-drop upload. The integration only changes how the CV travels between systems, so you can adopt one without revisiting anything about your output. ## Building it yourself If your team would rather own the integration, 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 plan includes it? It is included whichever plan you are on. See [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). ## Start the conversation Email support@remakecv.com with **RecruiterFlow** and your agency name. We will confirm what the integration will do on your account and what we need from you. ## Frequently asked questions ### Does RemakeCV integrate with RecruiterFlow? Yes. Our team builds and configures the RecruiterFlow integration for your agency using API credentials issued by RecruiterFlow. Once enabled it works like our other ATS integrations — email support@remakecv.com to get started. ### What do I need to provide? API credentials for your RecruiterFlow account. RecruiterFlow's support team issues these, and they are usually straightforward to obtain as an existing customer. Send them to support@remakecv.com and we handle the rest. ### Will it work the same as the other integrations? Yes. The same templates, editor, anonymisation, summaries and downloads apply. An integration only changes how the CV travels between systems — it never changes the formatting. ### Can I use RemakeCV with RecruiterFlow before the integration is set up? Yes. RemakeCV works standalone in the browser — upload a CV, format it, download it. The integration removes the manual download-and-re-attach step rather than being a prerequisite. --- # Connecting Recruitly > RemakeCV connects to Recruitly. Our team builds and configures the integration against the API credentials your Recruitly account provides, so branded CVs reach the candidate record without anyone downloading a file. Source: https://www.remakecv.com/help/integrations/recruitly Last updated: 2026-08-22 --- RemakeCV connects to Recruitly. Our team builds and configures the integration for your agency using API credentials from your Recruitly account, and from then on it behaves like every other RemakeCV ATS integration — a candidate's CV goes into your branded template and the finished document returns to their record. Email support@remakecv.com and we will scope it with you. ## How the integration is set up ### Tell us Recruitly is your CRM Email support@remakecv.com with your agency name and a picture of how the desk runs today — where candidate CVs sit, who formats them, and where the branded version has to end up before it reaches a client. ### Ask Recruitly for API credentials Recruitly's support team issues API access against your own account. This is an ordinary request for an existing customer, and they are the right people to tell you what they can issue and on what terms. ### Hand the credentials over securely We will tell you the safe route for sending them. Credentials that reach candidate data deserve the same care as any other — not an unencrypted channel, and not a shared inbox thread that outlives the setup. ### We build it and turn it on Our team writes the connection against Recruitly's API and enables it for your company. The relevant options appear in your RemakeCV dashboard afterwards, with nothing for individual consultants to install or maintain. > **Note:** What the finished integration does depends on what Recruitly's API makes available to your account — commonly pulling a candidate's CV across, putting the branded document back on their record, or both directions. We establish exactly which of those applies while we scope the work with you, ahead of anything being built. Connection scope is settled in the same conversation. Some of our integrations are held once for an entire company and others belong to each consultant individually; which pattern fits depends on how your account is arranged and where you want permissions to sit. We agree that with you rather than deciding it for you. ## What the workflow looks like Once the integration is live, getting a candidate into your house style stops involving a file on somebody's desktop: 1. Work the candidate in Recruitly the way your consultants already do. 2. Their CV is formatted into your agency's branded template — same template, same editor, same options as any other RemakeCV job. 3. The finished document lands back on the candidate record, ready for the client. The middle step is unchanged from what your team knows. 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) for what a consultant actually does there. ## Does the integration change the formatting? No. Templates, editing, anonymisation, summaries and downloads behave the same whether a CV arrived through an integration or was dragged into the browser. Because the integration only decides how the document travels, adopting one costs you nothing in output — clients receive the same CVs the week after go-live as the week before. That extends to the rest of the toolkit: [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 apply untouched. If your branded template has not been built yet, that runs alongside the integration work — 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 Recruitly on your own schedule and against your own release cycle. See [connecting RemakeCV to any ATS or internal system](https://www.remakecv.com/help/integrations/using-the-api-instead.md) for what those endpoints cover. ## Which plan includes it? Both plans carry it — Business and Enterprise alike. See [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). ## Start the conversation Email support@remakecv.com with **Recruitly** and your agency name. We will come back with what the integration will do on your account, what we need from you, and how your consultants will use it once it is running. ## Frequently asked questions ### Does RemakeCV integrate with Recruitly? Yes. Our team builds and configures the Recruitly integration for your agency using API credentials from your Recruitly account. Once it is enabled it behaves like 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 Recruitly account, which Recruitly's support team issues to you as an existing customer, and a short account of how your consultants handle CVs today. Send both to support@remakecv.com and our team picks it up 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 else — the finished document is identical either way. ### Can I use RemakeCV with Recruitly before the integration is set up? Yes. RemakeCV runs standalone in your browser — upload a CV, format it into your branded template, download it and attach it wherever you need. The integration exists to remove that manual step, not to gate access to the product. --- # Connecting SAP SuccessFactors > RemakeCV connects to SAP SuccessFactors. Our team builds the integration against API credentials issued on your own tenant, so candidates from every country and business area reach decision-makers in one consistent branded format. Source: https://www.remakecv.com/help/integrations/sap-successfactors Last updated: 2026-08-22 --- RemakeCV connects to SAP SuccessFactors. Our team builds and configures the integration for your talent function using API credentials issued on your own SuccessFactors tenant, and from there it sits alongside our other ATS integrations — a candidate's CV becomes a branded, optionally anonymised document and goes back to their record. Email support@remakecv.com and we will scope it with you. ## Why scoping is real work on a SuccessFactors tenant Most ATS platforms look broadly the same from one customer to the next. SuccessFactors does not. A tenant is configured around one organisation's job architecture, country requirements and approval routes, often over several years, so two customers running the identical product can present very different surfaces to anything connecting to them. The first conversation we have with you is therefore genuine discovery rather than a form to complete: we ask what your tenant permits instead of carrying assumptions over from somebody else's. Geography is the other constant at this scale. When hiring runs across several countries, CVs arrive in whatever each local market treats as normal — different lengths, different ordering, different ideas about what belongs on the page at all. A single house structure is what lets a panel in one country read a shortlist assembled in another without decoding the layout first. ## How the integration is set up ### Describe how your hiring runs today Email support@remakecv.com with your organisation name, the countries and business areas involved, and who prepares a candidate document before a decision-maker sees it. ### Find out what your own tenant can issue Whoever owns SuccessFactors internally decides what API access is available and on what terms. That answer belongs to your tenant alone, and it is the thing we build against. ### Hand the credentials over safely We will nominate a channel for it. Anything that reaches applicant data deserves the care a production secret gets, so keep it out of ordinary mail threads and shared mailboxes. ### We build it, then switch it on for you Our team implements the connection and enables it for your company. The relevant controls appear in your RemakeCV dashboard afterwards — recruiters and coordinators install nothing locally. > **Note:** How far the finished integration reaches is set by the access your tenant grants, not by us: collecting a candidate's CV, filing the branded version back against them, or both directions. Given how much SuccessFactors configurations differ, we put that scope in writing with you during scoping and confirm it before any build work begins. ## What the workflow looks like With the connection running, the branded CV arrives as a by-product of work your recruiters are doing anyway: 1. They stay in SuccessFactors, on the same requisitions and the same candidate records as before. 2. The CV is rendered into your organisation's branded template, anonymised on the way through where your process calls for it. 3. The finished version is filed back against the candidate, ready for whoever opens that record next. The middle step is ordinary RemakeCV, so anything a pilot team has already learned 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). One practical note: on a platform this size, the people who use the output and the people who control the tenant are rarely the same team. Bringing your HR systems contact into the conversation early saves scoping the work twice. ## Does the integration change the formatting? No. Templates, editing, anonymisation, summaries and downloads behave identically whether a CV arrived over a connection or was dropped into the browser by hand. The connection settles the route the file takes and nothing beyond that, so adopting one asks nothing of your existing output. Groups hiring under more than one employer brand, or presenting differently by region, usually ask whether that can be reconciled. [Template variants](https://www.remakecv.com/help/templates-and-branding/template-variants.md) exist for exactly that — the visible identity changes while the underlying structure stays fixed, and the fixed part is what keeps candidates comparable across the group. Where the design has yet to be drawn, it is built alongside the connection: see [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## Building it yourself Where your organisation has engineering capacity in-house and would rather own the connection, the [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) exposes 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) for what they cover. ## Which plan includes it? Neither plan treats integrations as an extra. See [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). ## Start the conversation Email support@remakecv.com with **SAP SuccessFactors**, your organisation name and the countries you would start with. We will confirm what the integration can do on your tenant, what we need from you, and how your talent function will use it day to day. ## Frequently asked questions ### Does RemakeCV integrate with SAP SuccessFactors? Yes. Our team builds and configures the SAP SuccessFactors integration for your talent function using API credentials issued on your own tenant, and it then works alongside our other ATS integrations. Because SuccessFactors tenants are configured differently from one organisation to the next, we scope yours specifically — email support@remakecv.com to start that. ### What do I need to provide? API credentials issued on your SuccessFactors tenant, arranged by whoever owns the platform internally — often an HR systems group rather than the recruiters themselves — plus a short note on the countries and business areas you would begin with. Send both to support@remakecv.com and our team takes the build from there. ### Will it work the same as the other integrations? Yes. The same templates, template variants, editor, anonymisation, summaries and downloads apply. An integration decides only how a CV travels between two systems; the document a hiring manager opens is the same either way. ### Can I use RemakeCV with SAP SuccessFactors before the integration is set up? Yes. RemakeCV works standalone in the browser — upload a CV, format it into your branded template, anonymise it where needed and download it. Talent functions often begin this way with a single country or team while tenant-side access is being arranged. --- # Connecting SmartRecruiters > RemakeCV connects to SmartRecruiters. Our team builds and configures the integration from API credentials issued for your account, so candidates from every business unit and country reach hiring panels in one consistent branded format. Source: https://www.remakecv.com/help/integrations/smartrecruiters Last updated: 2026-08-22 --- RemakeCV connects to SmartRecruiters. Our team builds and configures the integration for your talent function using API credentials issued for your SmartRecruiters account, and once it is running it behaves like every other RemakeCV ATS integration — a candidate's CV becomes a branded, optionally anonymised document and returns to their record. Email support@remakecv.com and we will scope it with you. ## Why this comes up in enterprise talent functions SmartRecruiters usually sits at the centre of a sizeable talent acquisition operation: several business units, more than one country, and enough recruiters and coordinators that no two people prepare a candidate document quite the same way. Scale is precisely what makes format matter. A hiring panel weighing a shortlist assembled by three colleagues in two regions needs the same information in the same place on each CV, otherwise the first differences anyone notices are differences in typography rather than in experience. Anonymised presentation carries more weight at this size too. In many large organisations a blind first sift is set down in hiring policy or in a public commitment, and it has to hold on every requisition rather than being left to individual judgement. Doing that by hand across hundreds of candidates is where the commitment tends to come apart — [auto-anonymisation](https://www.remakecv.com/help/anonymisation-and-compliance/auto-anonymisation.md) applies the same treatment every time, whichever team the candidate came through. ## How the integration is set up ### Tell us SmartRecruiters is your system of record Email support@remakecv.com with your organisation name and a short picture of today's path: who prepares candidate documents, which teams or regions are involved, and where the finished CV has to be available. ### Establish what API access your account allows Whoever administers SmartRecruiters inside your organisation, or their support team, determines what credentials can be issued and on what terms. Their answer sets the boundaries of what we build against. ### Pass the credentials over on a secure channel We will point you to one. Anything that reaches applicant data deserves the same handling as a production secret — not plain email, and not parked in a shared inbox thread where it outlives the project. ### We build the connection, then enable it Our team implements it and switches it on for your company. The relevant controls surface in your RemakeCV dashboard afterwards, so there is nothing for recruiters or coordinators to install on their own machines. > **Note:** How far the integration reaches is set by the API access granted on your SmartRecruiters account rather than by us — commonly 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 the scoping conversation, before any build work starts, so it is agreed rather than assumed. ## What the workflow looks like With the connection running, producing a panel-ready CV becomes part of moving the candidate forward rather than a separate task someone has to remember: 1. Recruiters and coordinators carry on in SmartRecruiters, on the same requisitions and the same records as before. 2. The CV is rendered into your organisation's branded template, and anonymised on the way through where that applies. 3. The finished version is filed back against the candidate, so whoever opens that record next finds it waiting. The middle step is the ordinary RemakeCV experience, so anything a pilot team has already learned still holds. 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). Rollout order is worth raising early, since talent functions this size rarely switch everything on at once. Which business units or countries go first, and whether they share one design, is something we work through with you. ## Does the integration change the formatting? No. Templates, editing, anonymisation, summaries and downloads behave the same whether a CV arrives over a connection or is dropped into the browser by hand. The connection decides only how the file travels, which means adopting one never obliges you to reopen decisions about your output. Groups running several employer brands often ask whether one design can cover all of them. [Template variants](https://www.remakecv.com/help/templates-and-branding/template-variants.md) are how that is handled — a different logo or colour set per business unit over an identical underlying structure, with visibility scoped so each team sees the variants it works with. The shared structure is the part that keeps candidates comparable across the group. If your design has not been built yet, that runs alongside the connection: see [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## Building it yourself Where your organisation has internal engineering capacity and prefers to own the connection, the [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) exposes 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) for what they cover. ## Which plan includes it? There is no integration tier: Business and Enterprise both include it. See [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). ## Start the conversation Email support@remakecv.com with **SmartRecruiters**, your organisation name and the teams or regions you would start with. We will confirm what the integration will do on your account, what we need from you, and how your talent function will use it day to day. ## Frequently asked questions ### Does RemakeCV integrate with SmartRecruiters? Yes. Our team builds and configures the SmartRecruiters integration for your talent function using API credentials issued for your SmartRecruiters account, and it then behaves like our other ATS integrations. Email support@remakecv.com and we will scope it with you. ### What do I need to provide? API credentials issued for your SmartRecruiters account, arranged by whoever administers it inside your organisation, together with a short note on which business units or countries are in scope first. Send both to support@remakecv.com and our team takes the build from there. ### Will it work the same as the other integrations? Yes. The same templates, template variants, editor, anonymisation, summaries and downloads apply. An integration settles how a CV moves between two systems and nothing more — the document a hiring panel opens is identical either way. ### Can I use RemakeCV with SmartRecruiters before the integration is set up? Yes. RemakeCV runs standalone in the browser — upload a CV, format it into your branded template, anonymise it if you need to, and download it. Large talent functions often pilot with one team this way and add the connection once the format is agreed. --- # Connecting TargetRecruit > RemakeCV connects to TargetRecruit. Our team builds the integration against API credentials for your account, working with whoever administers the Salesforce org it runs on, so branded CVs land back on the candidate record. Source: https://www.remakecv.com/help/integrations/targetrecruit Last updated: 2026-08-22 --- RemakeCV connects to TargetRecruit. Our team builds the integration for your agency using API credentials for your TargetRecruit account, so a candidate's CV can be formatted into your branded template and returned to their record instead of being exported and re-attached by hand. Tell us about your setup at support@remakecv.com and we will work out the shape of it together. ## How the integration is set up ### Get in touch and describe the desk Email support@remakecv.com with your agency name, a note on who prepares candidate CVs today, and where the branded document has to end up once it exists. ### Arrange API access on your account Your TargetRecruit administrator, or their support team, determines what credentials can be issued and on what terms. Their answer defines the boundaries of the build. ### Pass the credentials across securely We will point you at a safe channel. Treat anything that reaches candidate data the way you would treat a production secret — never plain email, never parked in a shared inbox where it outlives the project. ### We implement it and enable it for your company The relevant controls then surface in your RemakeCV dashboard. There is nothing for consultants to install and nothing for them to reconnect. > **Note:** What a connection is able to do is decided by the API access granted on your own account rather than by us — usually collecting a candidate's CV, filing the branded version back against them, or both directions. We agree that scope with you in writing before any build work begins. The same applies to platforms not named anywhere on this site: if your agency runs something else alongside TargetRecruit, or an internal system of your own, that is a build we will take on request too. ## Bring your Salesforce administrator to the scoping call TargetRecruit is built on the Salesforce platform, and that has a practical consequence worth acting on: the agency running it almost always has someone who understands the org underneath — an in-house administrator, or a consultancy on a retainer. That person is the one to have on the call. The questions that shape a build are theirs to answer. How are candidate records arranged in your org? Where do CV files actually live against them? What is an integration user permitted to see? Which of your customisations does a connection have to respect? None of that makes a TargetRecruit build faster or cheaper — we would not promise that before scoping it — but it does mean the answers already exist somewhere in your business rather than having to be discovered. Your administrator is also the right person to settle whether the connection is held once for the whole company or made by each consultant, since that decision lands on the permissions model they maintain. For how we hold credentials and candidate data generally, see [security and sub-processors](https://www.remakecv.com/help/anonymisation-and-compliance/security-and-subprocessors.md). One thing to raise with them while you are talking: RemakeCV already runs a [Salesforce integration](https://www.remakecv.com/help/integrations/salesforce.md) for agencies whose recruiting happens directly in Salesforce rather than through TargetRecruit. Your administrator will recognise the shape of it immediately, and which of the two suits your agency is worth settling before anything gets built. ## What the workflow looks like With a connection running, producing a client-ready CV becomes part of progressing the candidate rather than a task somebody has to remember: 1. Consultants carry on working candidates in TargetRecruit, on the same records as before. 2. The CV is rendered into your agency's branded design, through the same editor and options your team uses in the browser. 3. The branded document is filed back against the candidate, where whoever opens that record next will find it. The middle step is ordinary RemakeCV — 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. Your template, the editor, anonymisation, summaries and downloads work the same whether a CV arrived over a connection or was dropped into the browser by hand. A connection only decides the route the file takes, which means adopting one never obliges you to revisit decisions about your output. [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 over untouched. Where the branded design has not been built yet, that work runs in parallel with the connection — see [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## Building it yourself Agencies on the Salesforce platform frequently have development capacity to hand already, whether that is a staff developer or the partner who did the original implementation. If they would rather own the connection, the [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) exposes 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) for what those cover. ## Which plan includes it? Integrations sit on the Business plan as well as Enterprise — there is no upgrade gate on this. See [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). ## Start the conversation Email support@remakecv.com with **TargetRecruit**, your agency name and a line on who administers your Salesforce org. We will confirm what the connection can do on your account, what we need from you, and how your consultants will use it day to day. ## Frequently asked questions ### Does RemakeCV integrate with TargetRecruit? Yes. A TargetRecruit connection is one our team builds for your agency using API credentials for your account, after which it works like the other ATS and CRM connections we run. Because TargetRecruit is built on the Salesforce platform, whoever administers your org is a useful person to have in the first conversation. Write to support@remakecv.com to arrange it. ### What do I need to provide? API credentials for your TargetRecruit account, plus enough detail about the Salesforce org underneath it for us to know what we are building against — how candidate records are arranged and where CV files are held against them. Your Salesforce administrator will have those answers. Send them to support@remakecv.com. ### Will it work the same as the other integrations? Yes. Your template, the editor, anonymisation, candidate summaries and downloads are unaffected by the route a CV took to reach RemakeCV. A connection governs how the file moves between two systems and nothing beyond that, so what your client receives is identical either way. ### Can I use RemakeCV with TargetRecruit before the integration is set up? Yes. RemakeCV runs on its own in a browser — upload a CV, format it into your branded template, download it and attach it where you need it. Agencies often settle the template that way first and add the connection afterwards; it is not a prerequisite. --- # Connecting Teamtailor > RemakeCV connects to Teamtailor. Our team builds and configures the integration from API credentials issued for your Teamtailor account, so the CV a hiring manager opens carries the same brand as everything else a candidate has seen. Source: https://www.remakecv.com/help/integrations/teamtailor Last updated: 2026-08-22 --- RemakeCV connects to Teamtailor. Our team builds and configures the integration for your talent team using API credentials issued for your Teamtailor account, and once enabled it behaves like every other RemakeCV ATS integration — a candidate's CV becomes a document in your own brand, and the finished file goes back onto their record. Write to support@remakecv.com to open the conversation. ## How the integration is set up ### Describe your hiring process to us Email support@remakecv.com with your organisation name and a short picture of how candidates move today — who prepares a CV for review, and whose desk it lands on afterwards. ### Arrange API access on your Teamtailor account Your own administrator, or Teamtailor's support team, decides what credentials can be issued and on what terms. Their answer sets the boundaries of what we build against. ### Get the credentials to us safely We will tell you which channel to use. Anything with reach into applicant records deserves password-grade handling — not a plain email, and not a thread that half the department is copied on. ### We build it and switch it on Our team writes the connection against Teamtailor's API and enables it for your organisation. The controls surface in your RemakeCV dashboard; recruiters and hiring managers install nothing. > **Note:** What your integration ends up doing is bounded by the API access granted on your Teamtailor account — commonly reading the CV a candidate applied with, commonly writing the branded version back to them, sometimes both. We would rather agree that scope with you at scoping than assume it, so the conversation happens before any code is written. ## What the workflow looks like With the connection running, the branded document is produced in the course of moving someone forward: 1. Your team screens and progresses candidates in Teamtailor as they already do. 2. The CV is built into your organisation's template — same template, same editor, same options as every other RemakeCV job. 3. The finished file returns to the candidate's record, where whoever is making the decision opens it. 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) for what happens in the middle. ## Carrying the brand past the application Teamtailor tends to be chosen by in-house talent teams who take how their organisation appears to candidates seriously — a careers page written in the company's own voice, an application that feels considered rather than transactional. Then the shortlist reaches the hiring manager as whatever the candidates happened to send: one PDF exported from a design tool, one document last saved in 2019, one file someone in the team retyped by hand at eleven at night. Recruitment agencies solved that years ago, because a scruffy CV loses them the placement. The reasoning holds just as well inside a company. A house document keeps the same sections in the same order for every candidate, so an interview panel is weighing experience rather than layout, and it puts your organisation's mark on the page that the decision is actually made from. It also travels: a CV forwarded to a second interviewer, a board paper, an offer discussion. Consistency there is worth as much internally as polish is externally. Where the connection is held — once for the whole organisation, or separately by each user — is decided with you rather than for you. It affects how permissions and audit trails line up on the Teamtailor side, and in-house teams usually have a view. ## Does the integration change the formatting? No. Templates, editing, anonymisation, summaries and downloads behave identically whether a CV arrives over the connection or is dragged into a browser window. The integration governs transport only, so switching it on never obliges you to revisit your output. [Auto-anonymisation](https://www.remakecv.com/help/anonymisation-and-compliance/auto-anonymisation.md) comes across unchanged, which matters if you run a blind first sift, as do [candidate summaries](https://www.remakecv.com/help/ai-tools/candidate-summaries.md). If the branded document itself does not exist yet, that is designed alongside the integration — our team builds the template to your brand, and the connection then delivers it. See [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## Building it yourself If you have engineers who would rather own this, the [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) exposes the processing, retrieval and template endpoints directly, letting you wire RemakeCV into Teamtailor on your own timetable. [Connecting RemakeCV to any ATS or internal system](https://www.remakecv.com/help/integrations/using-the-api-instead.md) covers what those endpoints do. ## Which plan includes it? Business and Enterprise both include 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 **Teamtailor** and your organisation name. We will confirm what the integration can do on your account, what we need from you, and how it will sit in your talent team's week. ## Frequently asked questions ### Does RemakeCV integrate with Teamtailor? Yes. Our team builds and configures the Teamtailor integration for your organisation using API credentials issued for your Teamtailor account, and it then behaves like our other ATS integrations. Write to support@remakecv.com to open the conversation. ### What do I need to provide? Two things: API credentials issued for your Teamtailor account, which your own administrator or Teamtailor's support team arranges, and a sketch of how a candidate currently reaches the people who decide. Send both to support@remakecv.com and the build sits with our team from there. ### Will it work the same as the other integrations? Yes. The same templates, editor, anonymisation, summaries and downloads apply. An integration settles how a CV travels between two systems and stops there — what your hiring manager reads is the same document either way. ### Can I use RemakeCV with Teamtailor before the integration is set up? Yes. RemakeCV works on its own in a browser: upload a CV, format it into your branded document, download it and file it wherever it belongs. Plenty of talent teams run that way for months before asking us to connect anything. --- # Connecting Tracker RMS > RemakeCV connects to Tracker RMS. Our team builds and configures the integration from API credentials issued on your Tracker RMS account, so perm and contract submissions both leave in the right branded format. Source: https://www.remakecv.com/help/integrations/tracker-rms Last updated: 2026-08-22 --- RemakeCV connects to Tracker RMS. Our team builds and configures the integration for your agency from API credentials issued on your Tracker RMS account, and once it is running a candidate's CV can be formatted into whichever of your branded templates the submission calls for and returned to their record. Tell us what you need at support@remakecv.com. ## One system, two desks Tracker RMS is generally chosen by mid-market agencies running permanent and contract work side by side, frequently across both the UK and the US, and wanting the lot on one platform rather than a system per desk. That is a sensible way to run an agency and an awkward one to format for: a perm submission and a contract submission are not the same document. A permanent shortlist for a retained client is a considered piece of work: full career history, a written summary, your branding on the front. A contractor put forward against a live requirement is skim-read in minutes by someone who wants availability and the last three assignments — and often has to arrive in the client's own layout, because a preferred-supplier agreement says so. One house format cannot serve both without being wrong for one of them. ## Which version goes out That is the job [template variants](https://www.remakecv.com/help/templates-and-branding/template-variants.md) do. A variant is a full version of your template built for a particular situation, and the consultant picks the right one while processing the CV: | Submission | Version that usually fits | |---|---| | Perm shortlist under your own brand | Your house template | | Client on a preferred-supplier list requiring their layout | Client-branded variant | | Client running a blind first sift | Anonymised variant | | Contract role where the client wants the CV only | Variant with no cover page | | Separate perm and contract brands | One variant per brand | There is no cap on how many you run, and visibility can be scoped so each desk sees the versions it actually works with. ## Setting it up ### Tell us Tracker RMS is your system of record Email support@remakecv.com with your agency name, which desks are in scope first, and where a finished submission has to end up. ### Establish what API access your account allows Ask Tracker RMS what credentials can be issued against your account and on what terms. Their answer sets the boundaries of what we build against. ### Hand the credentials over on a secure channel We will point you to one. Anything reaching candidate data warrants the care you would give a production secret, not plain email or a shared inbox thread. ### We build the connection, then enable it Our team implements it and switches it on for your company. The relevant controls surface in your RemakeCV dashboard, so there is nothing for consultants to install or look after. > **Note:** How far the connection reaches is decided by the API access granted on your Tracker RMS account rather than by us — commonly collecting a candidate's CV, filing the branded version back against them, or both. That scope is agreed with you in writing at the scoping stage, before any build work starts. The same conversation settles whether the connection is held once for the agency or made by each consultant. ## What it looks like once it is running Choosing a version and getting the finished file back onto the record happens inside the flow the consultant is already in. They keep progressing the candidate in Tracker RMS; the CV is rendered into whichever template the submission calls for, through the same editor and options as any other RemakeCV job; and the branded document is filed back against the candidate for whoever picks that record up next. 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) for the middle part. ## Does the integration change the formatting? No. Whether a CV arrives over a connection or is dropped into the browser by hand, the templates, variants, editor, anonymisation, summaries and downloads work in exactly the same way. All a connection settles is how the file gets between systems, so you can take this on in stages — connect first and build variants later, or the reverse. If the templates do not exist yet, our team builds them to your design: see [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## Owning the build yourself Agencies with development resource sometimes prefer to hold the connection in-house. The [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) exposes the processing, retrieval and template endpoints directly; [connecting RemakeCV to any ATS or internal system](https://www.remakecv.com/help/integrations/using-the-api-instead.md) covers what they reach. ## Which plan includes it? Business and Enterprise both carry integrations, on the same terms — see [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). Tracker RMS is no special case either: any ATS or CRM your agency runs can be connected once its provider issues credentials, whether or not it already appears in our list. ## Start the conversation Email support@remakecv.com with **Tracker RMS**, your agency name and the desks you would start with. We will confirm what the integration will do on your account, what we need from you, and how your consultants will use it day to day. ## Frequently asked questions ### Does RemakeCV integrate with Tracker RMS? Yes. Our team builds and configures the Tracker RMS integration for your agency from API credentials issued on your Tracker RMS account, after which it behaves like our other ATS integrations. Tell us what you need at support@remakecv.com. ### What do I need to provide? API credentials for your Tracker RMS account, which you arrange with Tracker RMS as their customer, and a short account of how your perm and contract desks prepare submissions today. Send both to support@remakecv.com and our team handles the build. ### Will it work the same as the other integrations? Yes. The same templates, template variants, editor, anonymisation, summaries and downloads apply. A connection settles only how a CV moves between two systems; the finished document is identical whichever way it got there. ### Can I use RemakeCV with Tracker RMS before the integration is set up? Yes. RemakeCV runs standalone in the browser — upload a CV, pick the template version the submission calls for, and download it. Agencies often start on one desk this way and connect Tracker RMS once the formats are agreed. --- # Connecting Workable > RemakeCV connects to Workable. Our team builds and configures the integration from API credentials issued for your Workable account, so a branded, consistent candidate CV is produced without anyone on your hiring team retyping one. Source: https://www.remakecv.com/help/integrations/workable Last updated: 2026-08-22 --- RemakeCV connects to Workable. Our team builds and configures the integration for your hiring team using API credentials issued for your Workable account, and it then behaves like every other RemakeCV ATS integration — a candidate's CV is formatted into your branded template and the finished document is returned to their record. Email support@remakecv.com and we will scope it with you. ## Why smaller hiring teams ask for this Workable is commonly run by small and mid-sized employers, where hiring is handled by one or two people — and often by someone whose job is not only recruiting. An office manager, a head of operations, a founder. That shapes what a formatting integration is actually worth. Nobody in that setup has an afternoon spare to retype a CV into the company layout before it goes to an interviewer, so in practice the tidying either does not happen or it happens at the expense of something else. Automating the document step is the point here. The candidate paperwork keeps arriving in whatever shape the applicant sent it, and it still reaches your interviewers looking like it came from your organisation — without a person having to make that true by hand each time. ## How the integration is set up ### Let us know you hire through Workable Email support@remakecv.com with your organisation name and a couple of lines on the present routine: who handles candidate CVs, and who needs to read the finished version. ### Arrange API access on your Workable account Whoever administers your account, or Workable's own support team, decides which credentials can be issued and on what terms. Their answer sets the boundaries we build within. ### Get the credentials to us safely We will give you a secure route. Anything with reach into applicant data warrants password-grade handling — not plain email, and not sitting in a shared inbox where the whole team can read it. ### We build it and turn it on Our team writes the connection against Workable's API and enables it for your organisation. The controls surface in your RemakeCV dashboard afterwards, and no one on your side installs anything. > **Note:** How far the integration reaches is decided by the API access your Workable account is granted — usually fetching a candidate's CV, returning the branded version to their record, or both. We agree that scope with you in the scoping conversation, before any code is written, rather than promising it in advance. ## What the workflow looks like With the connection running, producing a presentable CV becomes part of moving a candidate forward rather than a task somebody has to remember: 1. Applications are reviewed and progressed in Workable the way your team already handles them. 2. The CV is rendered into your organisation's branded template, using the same template, editor and options as any other RemakeCV job. 3. The finished document returns to the candidate record, where the hiring manager or interviewer picks it up. Only the middle step is ours, so whatever your team has already learned 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). One question we like to settle early, because it matters more when the team is small: whether the connection is held once for the organisation or set up per user. With two or three people doing the hiring, a single shared connection is usually simpler to live with — but it affects how permissions and audit trails line up on the ATS side, so we agree it with you instead of assuming. ## Does the integration change the formatting? No. Templates, editing, anonymisation, summaries and downloads behave identically whether a CV arrives over a connection or is dragged into the browser. The integration governs the file's journey and nothing about its appearance, so taking one on never obliges you to revisit your output. If your branded template does not exist yet, our team builds it to your design as its own piece of work alongside the connection — see [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## Building it yourself If you have engineering capacity in-house and would rather own the connection, the [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) gives you the processing, retrieval and template endpoints directly, on your own schedule. See [connecting RemakeCV to any ATS or internal system](https://www.remakecv.com/help/integrations/using-the-api-instead.md) for what they cover. ## Which plan includes it? Both plans carry it — Business and Enterprise alike. See [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). ## Start the conversation Email support@remakecv.com with **Workable** and your organisation name. We will confirm what the integration will do on your account, what we need from you, and how the people who actually run your hiring will use it week to week. ## Frequently asked questions ### Does RemakeCV integrate with Workable? Yes. Our team builds and configures the Workable integration for your hiring team using API credentials issued for your Workable account, and it then behaves like our other ATS integrations. Email support@remakecv.com and we will scope it with you. ### What do I need to provide? API credentials issued for your Workable account, arranged by whoever administers it or by Workable's own support team, plus a couple of lines on who prepares candidate CVs today. Send both to support@remakecv.com and our team does the build — there is no development work at your end. ### Will it work the same as the other integrations? Yes. The same templates, editor, anonymisation, summaries and downloads apply. An integration decides only how a CV moves between systems, so the document your hiring manager opens is the same either way. ### Can I use RemakeCV with Workable before the integration is set up? Yes. RemakeCV runs standalone in your browser — upload a CV, format it into your branded template, download it and file it wherever you need. Small hiring teams often start there and add the connection once the volume justifies it; it is never a prerequisite. --- # Connecting Workday > RemakeCV connects to Workday. Our team builds and configures the integration from API credentials issued for your Workday tenant, so a branded candidate document is produced alongside your system of record rather than in spite of it. Source: https://www.remakecv.com/help/integrations/workday Last updated: 2026-08-22 --- RemakeCV connects to Workday. Our team builds and configures the integration for your talent function using API credentials issued for your Workday tenant, and it then behaves like every other RemakeCV ATS integration — a candidate's CV is rendered into your branded template and the finished document returns to their record. Email support@remakecv.com and we will scope it with your recruiting and HR systems people together. ## Where RemakeCV sits next to your system of record Workday Recruiting is one part of a wider HCM suite, and that suite is usually the authoritative record for far more than hiring. RemakeCV works alongside it rather than reproducing any of it: it takes a candidate's CV, produces a branded version, and returns it. That is the whole remit — worth saying at the top, because it is almost always the first thing the people who own the suite want to establish. ## How the integration is set up ### Tell us your hiring runs on Workday Recruiting Email support@remakecv.com with your organisation name, who prepares candidate CVs today, and what happens to the document afterwards. ### Arrange API access on your Workday tenant In practice this sits with the HR systems or HRIS team who administer the tenant rather than with recruiting. What they are able to issue, and under what conditions, is the ground we build on. ### Hand the credentials over through a secure channel We will nominate one. Credentials reaching into a live HR system should not travel by ordinary email, nor sit as an attachment on a ticket that stays open. ### We build the connection and enable it Our team implements it against the access granted and switches it on for your organisation. The controls surface in your RemakeCV dashboard, with nothing for recruiters or hiring managers to install. > **Note:** Scope follows access. What your integration ends up doing is a function of the API access granted on your tenant, which differs between organisations — commonly fetching a candidate's existing CV, placing the branded version back on their record, or both. We establish that with you and your HR systems team during scoping, and agree it before any build work starts. ## Who to bring into the scoping conversation Because Workday Recruiting shares a suite with the rest of your HR systems, the people who can answer our questions are rarely all in recruiting. Three perspectives usually cover it: - **Talent acquisition** — what CV preparation looks like now, and who reads the finished document. - **The HR systems or HRIS team** — who administers the tenant, what access can be granted, and how that fits the change process you already run. - **Whoever signs off on data handling** — often IT security or privacy, since candidate documents leave one system and return to it. None of that needs assembling before you write to us; a first conversation with recruiting alone works fine. Knowing early who will be involved just saves a round of forwarding. ## What the workflow looks like With the connection running, the branded CV is produced as part of moving a candidate forward: 1. Requisitions, applications and progression carry on in Workday Recruiting as they do now. 2. The CV is rendered into your branded template, using the same editor and options as any other RemakeCV job. 3. The finished document returns to the candidate's record, where the hiring manager and interviewers pick it up. Only the second step is ours. In a suite deployment that matters, because "can we add something for this?" usually turns on how much of the established process it disturbs — and here it disturbs none. 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) for what happens in between. ## Does the integration change the formatting? No. A CV arriving over a connection is treated exactly as one dropped into the browser — same template, same editing, same anonymisation, same summaries, same download options. The connection settles where the file comes from and where it goes, so taking one on never reopens a decision your brand or talent team has already made. If your organisation has never had a house CV layout — plenty of talent functions have not — our team designs and builds the template as its own strand of the same project. See [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). ## Building it yourself Organisations running a suite this size often have an integration team and a settled way of doing this work. Where that is true, the [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) exposes the processing, retrieval and template endpoints directly, so your engineers can wire RemakeCV in on your own change calendar. See [connecting RemakeCV to any ATS or internal system](https://www.remakecv.com/help/integrations/using-the-api-instead.md). ## Which plan includes it? Business and Enterprise both include 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 **Workday** and your organisation name. We will tell you what we need, confirm what the integration will do on your tenant, and — if it helps — take the technical questions directly with your HR systems team, rather than leaving recruiting to relay them in both directions. ## Frequently asked questions ### Does RemakeCV integrate with Workday? Yes. Our team builds and configures the Workday integration for your talent function using API credentials issued for your Workday tenant, and it then behaves like our other ATS integrations. Email support@remakecv.com and we will scope it with you. ### What do I need to provide? API credentials issued for your Workday tenant, plus a short account of who prepares candidate CVs today and who reads them. Because Workday Recruiting sits inside a wider HCM suite, the credentials are usually arranged by the HR systems team who administer the tenant rather than by recruiting. Send both to support@remakecv.com and our team takes on the build. ### Will it work the same as the other integrations? Yes. The same templates, editor, anonymisation, summaries and downloads apply. An integration settles only where a CV comes from and where it goes afterwards, so the document a hiring manager opens is identical either way. ### Can I use RemakeCV with Workday before the integration is set up? Yes. RemakeCV runs standalone in your browser — upload a CV, format it into your branded template, download it and file it wherever you need. Talent functions waiting on an internal approval cycle often work this way in the meantime; the connection is never a prerequisite. --- # Connecting Zoho Recruit > RemakeCV connects to Zoho Recruit. Our team builds and configures the integration from API credentials issued on your Zoho Recruit account, so CV formatting joins the rest of your stack instead of happening in a tab of its own. Source: https://www.remakecv.com/help/integrations/zoho-recruit Last updated: 2026-08-22 --- RemakeCV connects to Zoho Recruit. Our team builds and configures the integration for your organisation from API credentials issued on your Zoho Recruit account, and it then does what every other RemakeCV ATS integration does — turn a candidate's CV into a branded document and put it back on their record. Write to support@remakecv.com and we will work out the shape of it with you. ## Why Zoho Recruit customers ask for this Zoho Recruit rarely turns up on its own. It is one product in a suite, and organisations that choose it usually run two or three of its siblings alongside — the CRM, the mail, the finance side — because they would rather hold a small number of tools that already know about each other than a long list that does not. That preference is the whole reason this page exists. A team which has deliberately consolidated does not want CV formatting to become the one job that happens somewhere else, in an unlogged browser tab, with the finished file carried back by hand. The teams asking also tend to be small: an agency of a handful of consultants, or one or two internal recruiters in a growing company. There is rarely a developer to spare, which is why our team does the building and the configuring rather than yours, and why there is nothing left for anyone to maintain once it is on. ## What changes day to day With the connection running: 1. Your recruiters carry on in Zoho Recruit, on the candidate records they already keep there. 2. The CV is rendered into your branded template, through the same editor and the same options as any other RemakeCV job. 3. The branded version is filed back against the candidate, so whoever opens that record next finds it waiting. The middle step is ordinary RemakeCV, so nothing your team has already learned goes stale. 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. The templates, the editor, anonymisation, summaries and downloads all behave the same way whether a CV came over a connection or was dragged into the browser. A connection settles the route the file takes and nothing about the document at the end of it — which is what makes it safe to add later, once your output is already agreed. Smaller teams frequently do exactly that: work standalone for a few weeks, settle what the branded CV should look like, then connect. Where the template itself has not been built yet, 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). ## Getting it built The reach of any connection is set by the API access your provider grants, so we agree the scope before writing code rather than promising it here: > **Note:** How much the integration can do is decided by the API access granted on your Zoho Recruit account, not by us — commonly fetching a candidate's CV, filing the branded version back against them, or working in both directions. We put that scope in writing with you first, and only then start building. ### Tell us Zoho Recruit is where your candidates live Email support@remakecv.com with your organisation name and a short picture of today's path: who prepares candidate CVs, and where the branded document has to end up. ### Arrange API access on your account Whoever administers Zoho Recruit for you asks Zoho what credentials can be issued and on what terms. Their answer defines what we build against. ### Get the credentials to us on a secure channel We will point you to one. Anything with reach into candidate records deserves the handling you would give a password — not plain email, and not left sitting in a shared inbox. ### We build it and switch it on Our team implements the connection and enables it for your company. The relevant controls appear in your RemakeCV dashboard afterwards, with nothing to install on anyone's machine. Worth settling early: whether the connection is held once for the company or made by each recruiter individually. Which shapes are available depends on your account, and we tell you at scoping rather than choosing for you. ## The rest of your stack Zoho Recruit is unlikely to be the only system a candidate document touches, and RemakeCV is not confined to the platforms with a live integration today — whatever else your organisation runs, our team can build against it once the provider issues credentials. If you do have engineering capacity and would rather own the connection, the [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) exposes the processing, retrieval and template endpoints directly; [connecting RemakeCV to any ATS or internal system](https://www.remakecv.com/help/integrations/using-the-api-instead.md) covers what they reach. Either route is included on the Business and Enterprise plans without distinction — see [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). ## Start the conversation Email support@remakecv.com with **Zoho Recruit** and your organisation name. We will confirm what the integration will do on your account, what we need from you, and how your recruiters will use it day to day. ## Frequently asked questions ### Does RemakeCV integrate with Zoho Recruit? Yes. Our team builds and configures the Zoho Recruit integration for your organisation from API credentials issued on your Zoho Recruit account, and it then behaves like our other ATS integrations. Write to support@remakecv.com and we will work out the shape of it with you. ### What do I need to provide? API credentials for your Zoho Recruit account, arranged by whoever administers Zoho for your organisation, plus a few lines on how candidate CVs are prepared today. Send both to support@remakecv.com and our team takes the build from there — no developer time is needed on your side. ### Will it work the same as the other integrations? Yes. The same templates, editor, anonymisation, summaries and downloads apply. A connection settles only how a CV travels between two systems, so the document your client or hiring manager opens is the same either way. ### Can I use RemakeCV with Zoho Recruit before the integration is set up? Yes. RemakeCV runs standalone in the browser — upload a CV, format it into your branded template, download it. Smaller teams often work this way while they settle on their format and add the connection afterwards; it is not a prerequisite. --- # Plans and pricing > RemakeCV offers a per-seat Business plan and a volume-based Enterprise plan. Custom templates, bulk formatting, anonymisation and ATS integrations are included on both. Each Business seat includes 30 credits per month, pooled across the company. Source: https://www.remakecv.com/help/account-and-billing/plans-and-pricing Last updated: 2026-08-22 --- RemakeCV has two plans. Business is priced per user per month, billed monthly or annually, and each seat contributes 30 credits per month to a shared company pool. Enterprise is priced to volume and adds priority support and dedicated setup. Custom templates, bulk formatting, anonymisation and ATS integrations are included on both plans. Annual billing is cheaper per seat than monthly. ## What are the plans? | | Business | Enterprise | |---|---|---| | **Price** | $35 per user/month, or $25 billed annually | Based on volume | | **Credits** | Allocation sized from seats, at 30 per user/month, pooled | Sized to your volume | | **Custom templates** | Yes | Yes | | **Bulk formatting** | Yes | Yes | | **Auto-anonymisation** | Yes | Yes | | **ATS integrations** | Yes | Yes | | **Support** | Same-day response | Priority 24/7 | | **Onboarding** | 1:1 onboarding session | Dedicated setup | Current figures are always on the [pricing page](https://www.remakecv.com/pricing). ## How does per-seat pricing work with pooled credits? You buy seats, and your account gets a **single monthly credit allocation** shared across everyone. Business allocations are sized from seat count at 30 credits per user. The pooling is the useful part: if one consultant formats 80 CVs and another formats 10, that is fine — they draw from the same allocation. > **Warning:** Adding a user does not automatically raise the allocation. If you add seats, confirm with us that your credit allocation has been resized to match. > **Tip:** Because credits pool, you do not need to buy seats for capacity. Buy seats for the number of people who need to log in; if the allocation is short, buy top-ups or talk to us about resizing rather than adding seats nobody uses. If you want to ring-fence usage — a cap per consultant, or a pool per team — that is configurable. See [credits explained](https://www.remakecv.com/help/account-and-billing/credits-explained.md). ## Monthly or annual? Annual is meaningfully cheaper per seat. Monthly is the right choice if your headcount moves a lot, since you are not committing to seats you may not need in six months. If you are already annual and need to add seats mid-term, the additional seats are pro-rated for the remainder of the year. ## Which plan do I need? Both plans include the full product — custom templates, bulk formatting, anonymisation, AI tools and [ATS integrations](https://www.remakecv.com/help/integrations/integrations-overview.md). The difference is commercial shape, not capability. Choose **Enterprise** if any of these apply: - Your volume makes per-seat pricing the wrong shape - You need priority support commitments - You need dedicated onboarding across a larger team - You need bespoke arrangements around data handling or contracts Otherwise **Business** is the right fit. ## How do I change plan? Email support@remakecv.com. Upgrades can happen at any time, and on annual plans the upgraded fee is pro-rated for the remaining year. See [upgrading and downgrading](https://www.remakecv.com/help/account-and-billing/upgrading-and-downgrading.md). ## Frequently asked questions ### How much does RemakeCV cost? The Business plan is $35 per user per month billed monthly, or $25 per user per month billed annually. Enterprise pricing is based on volume — see the pricing page for current figures. ### How many credits come with a seat? Business allocations are sized at 30 credits per user per month, pooled across the company. The allocation is set when your plan is agreed rather than adjusting automatically, so confirm it with us when your headcount changes. ### Is there a free trial? Contact us to arrange a trial and a walkthrough of your agency's setup. --- # Credits, limits and shared pools > Credits pool at company level and refresh each billing cycle. Our team can cap individual consultants or ring-fence an allocation for a team — email support@remakecv.com. Source: https://www.remakecv.com/help/account-and-billing/credits-explained Last updated: 2026-08-21 --- RemakeCV credits sit in one company pool and refresh at the start of each billing cycle. On top of that pool, our team sets per-user limits capping an individual consultant, or shared pools ring-fencing an allocation for a team — email support@remakecv.com with the split you want. A per-user limit always takes precedence over any pool the user also belongs to. ## The three layers Credit checks run in this order: ### Company balance Does the company have any credits at all? If the balance is zero, processing stops for everyone with "No credits left". ### Per-user limit If the consultant has an individual limit, their usage in the current billing cycle is checked against it. **If a user limit exists, the check stops here** — pools are not consulted. ### Shared pool Otherwise, if the consultant belongs to a pool, the pool's combined usage is checked against its limit. > **Tip:** Running out unexpectedly? You can buy a credit top-up yourself from the dashboard without waiting for us — see [invoices and payment](https://www.remakecv.com/help/account-and-billing/invoices-and-payment.md). > **Warning:** A per-user limit overrides pool membership entirely. If someone with an individual limit is also in a team pool, they draw against their own limit and the pool ignores them. When you ask us for a split, give each person one or the other, not both, unless that is genuinely what you want. ## When would I use per-user limits? - **Preventing runaway usage.** A new consultant bulk-processing a back catalogue can consume a month's pool in an afternoon. - **Cost allocation.** Where consultants are on different desks with different budgets. - **Contractors.** A defined allocation for someone not on the permanent team. ## When would I use shared pools? - **Per-team budgets.** The tech desk gets 300 credits, the finance desk gets 150. - **Per-client ring-fencing.** A dedicated allocation for a large account. - **Regional splits.** Where offices are budgeted separately. A pool is a combined cap: five consultants sharing 200 credits can distribute them however the work falls, with no individual ceiling. ## What does a consultant see when they hit a limit? "Credit limit reached" — deliberately the same message for both an individual limit and a pool limit, so a consultant is not shown other people's allocations. Our team can tell you which applies. The distinction that matters for diagnosis: | Message | Meaning | |---|---| | "No credits left" | The **company** balance is exhausted | | "Credit limit reached" | An **individual or pool** cap was hit while the company still has credits | For what does and does not consume a credit in the first place, see [how credits and usage work](https://www.remakecv.com/help/getting-started/credits-and-usage.md). ## When does usage reset? At the start of each billing cycle, not the calendar month. Usage is counted against the cycle that began at your last renewal date. ## How do I change limits? Per-user limits and shared pools are set up by our team — email support@remakecv.com with the consultants and allocations you want, and we apply them for you. One constraint to know when planning: **the total of all per-user limits and shared pools cannot exceed your company's monthly allocation.** Over-allocating is rejected rather than silently accepted, so decide the split against your real allocation. ## What does not consume credits? Only processing a new CV does. Editing, anonymising, summarising, regenerating and re-downloading are all free — see [how credits and usage work](https://www.remakecv.com/help/getting-started/credits-and-usage.md). ## Frequently asked questions ### Why does a consultant see 'credit limit reached' when the company has credits? They have hit an individual or shared-pool cap rather than the company balance. Per-user limits and shared pools are set up by our team — email support@remakecv.com to change them. ### Which wins, a user limit or a pool? The per-user limit. If a consultant has an individual limit, it is checked and the pool is skipped entirely. ### Do credits roll over? Not on standard accounts — they refresh at the start of each billing cycle and unused credits lapse. Rollover is available on some agreements. ### Is there a limit on how much I can allocate? Yes. The total of all per-user limits and shared pools cannot exceed your company's monthly allocation, so over-allocating is rejected. --- # Upgrading, downgrading and adding seats > Change your RemakeCV plan or seat count at any time. Upgrades on annual plans are pro-rated for the remainder of the year, and reductions normally take effect at your next renewal. Source: https://www.remakecv.com/help/account-and-billing/upgrading-and-downgrading Last updated: 2026-08-21 --- You can upgrade your RemakeCV plan at any time by emailing support@remakecv.com. If you upgrade mid-term on an annual plan, the additional fee is pro-rated for the remaining year. Downgrades and seat reductions normally take effect at your next renewal. ## How do I upgrade? Email support@remakecv.com with what you need — more seats, a different plan, or more credits. Upgrades are available at any time on any package. On an annual plan, an upgrade is pro-rated: you pay the difference for the remaining months rather than a full additional year. ## Should I add seats or ask for more credits? These solve different problems, and picking the wrong one is expensive. | Problem | Fix | |---|---| | More people need to log in | Add seats | | The same people need to process more CVs | More credits, not more seats | | One consultant keeps hitting a cap | Raise their [per-user limit](https://www.remakecv.com/help/account-and-billing/credits-explained.md) — no purchase needed | | Occasional overflow in busy months | Buy a credit top-up yourself from the dashboard | > **Tip:** Check your usage log before buying anything. A team that appears to be out of credits is often just one consultant with a low individual limit, which costs nothing to change. ## What happens to credits when I add a seat? Your credit allocation is a figure we set on your account — it does not change automatically when a user is added. > **Warning:** When you add seats, **ask us to resize the allocation at the same time**. Otherwise you gain a login and no additional capacity, and the team hits the limit sooner than expected. For a short-term shortfall, buy a credit top-up from the dashboard instead — see [invoices and payment](https://www.remakecv.com/help/account-and-billing/invoices-and-payment.md). ## How do I downgrade? Email support@remakecv.com. Reductions normally apply at your next renewal rather than immediately, since the current term is already paid. Before downgrading, confirm: - **Seats.** Which users will be removed — removal is permanent, with no deactivated state. See [user roles and permissions](https://www.remakecv.com/help/account-and-billing/user-roles-and-permissions.md). - **Credits.** Whether the reduced pool covers your actual monthly volume — check the usage log rather than estimating. - **Features.** If you are moving off Enterprise, whether you rely on an [ATS integration](https://www.remakecv.com/help/integrations/integrations-overview.md). ## What happens to my templates and CV history? Templates are unaffected by plan changes. CV history is retained according to your storage settings, not your plan — see [GDPR and data retention](https://www.remakecv.com/help/anonymisation-and-compliance/gdpr-and-data-retention.md). ## How do I cancel? Email support@remakecv.com. Download anything you need from CV history before your access ends. ## Frequently asked questions ### How do I upgrade? Email support@remakecv.com. Upgrades can be made at any time on any package. ### What happens if I upgrade mid-year on an annual plan? The upgraded fee is pro-rated for the remaining year, so you only pay for the period you actually use at the higher tier. ### Can I reduce seats? Yes, normally at your next renewal. Contact support to discuss timing on an annual commitment. --- # Invoices and payment methods > RemakeCV billing runs through Stripe. Invoices are issued each billing cycle and payment details are updated through the billing portal. Source: https://www.remakecv.com/help/account-and-billing/invoices-and-payment Last updated: 2026-08-21 --- Billing runs through Stripe. **Credit top-ups are self-serve** — any user can buy additional credits from the dashboard by card. Subscription billing, invoices, payment methods and billing contacts are handled by our team, so email support@remakecv.com for those. ## Buying credit top-ups This is the one billing action you can complete yourself, and it is the fastest fix when the team runs short mid-cycle. ### Open the top-up dialog The Top Up Credits option appears on the dashboard. ### Choose a quantity Available in increments of 10, from 10 up to 100 credits. ### Pay by card You are taken to a secure Stripe checkout. Credits are added to your company pool as soon as the payment completes. > **Note:** Top-ups are not restricted to administrators — any user can buy them. If you would rather that were not the case, tell us at support@remakecv.com. Rates depend on your agreement. For anything larger than a top-up, talk to us about resizing your allocation — see [upgrading and adding seats](https://www.remakecv.com/help/account-and-billing/upgrading-and-downgrading.md). ## When am I billed? At the start of each billing cycle. Your renewal date is set when you subscribe, not on the first of the month — an account started on the 12th renews on the 12th. Your [credits refresh on the same date](https://www.remakecv.com/help/getting-started/credits-and-usage.md). ## How do I update a payment method? Email support@remakecv.com and we will update it for you. Card details never pass through RemakeCV — payment information goes directly to Stripe. > **Warning:** Never send card details by email, to us or to anyone else. If a message claiming to be from RemakeCV asks you to email card numbers, it is not from us — forward it to support@remakecv.com. ## What if a card payment fails? The usual causes: | Cause | Fix | |---|---| | Card expired | Update the card | | Insufficient funds | Retry once funds are available | | Bank blocked an international payment | Authorise the payment with your bank | | Card cancelled or replaced | Provide the new card | If a payment keeps failing, contact support@remakecv.com — we would rather sort it out than have your team blocked mid-week. To change what you are billed for rather than how, see [upgrading and downgrading](https://www.remakecv.com/help/account-and-billing/upgrading-and-downgrading.md) and [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). ## Can I change the billing contact? Yes. Billing notices often need to go to finance rather than the person who set up the account. Email support@remakecv.com with the address to use. ## Do you provide VAT invoices? Invoices are issued with the details we hold for your company. If your VAT number or registered address is missing or wrong, send the correct details to support@remakecv.com and we will reissue. ## Can I get a purchase order arrangement? For annual and Enterprise agreements, invoice-based billing against a PO is usually workable. Contact support@remakecv.com with your procurement requirements. ## Frequently asked questions ### How do I get a copy of an invoice? Invoices are issued for each billing cycle. If you need a copy or a reissue for your finance team, email support@remakecv.com. ### Can I buy more credits without contacting you? Yes. Credit top-ups are self-serve from the dashboard, in increments of 10 up to 100 credits, paid by card. ### Can we pay by bank transfer? Card payment through Stripe is standard. For invoice-based payment on annual or Enterprise agreements, contact support@remakecv.com. ### Why did my payment fail? Usually an expired card, insufficient funds or a bank block on international payments. Update the card and the retry will succeed. --- # Two-factor authentication > Add a second authentication factor to RemakeCV logins. The highest-value security setting on an account holding candidate personal data. Source: https://www.remakecv.com/help/account-and-billing/two-factor-authentication Last updated: 2026-08-21 --- Two-factor authentication requires a time-based code from an authenticator app in addition to your password. Because RemakeCV accounts hold candidate personal data, enabling it is the single highest-value security change you can make. It is configured per user in account settings. ## Why does it matter here specifically? A RemakeCV login can reach every CV your agency has processed. A compromised password without a second factor is therefore a personal-data breach affecting candidates who never had a relationship with the attacker — and a reportable one. Recruitment credentials are also actively targeted, because candidate databases have resale value. This is not a theoretical risk. ## How do I set it up? ### Open your account settings Find the two-factor authentication section. ### Scan the QR code Use any authenticator app — Google Authenticator, Microsoft Authenticator, Authy, 1Password, or your password manager's built-in support. ### Enter the six-digit code This confirms the app and RemakeCV are in sync. ### Save your eight backup codes You are shown eight codes, each usable **once**. Store them somewhere that is **not** the phone running the authenticator — a password manager or a physical safe. This is the step people skip and later regret. > **Warning:** Backup codes stored only on the device running your authenticator app are useless — losing the phone loses both. Keep them somewhere separate. They are single-use, so cross them off as you spend them. They also work in place of an authenticator code when disabling two-factor authentication. ## Who should turn it on? | Situation | Recommendation | |---|---| | Any account holding candidate CVs | Enable it | | Clients audit your security | Enable and enforce company-wide | | Regulated sector recruitment | Enforce, and pair with prompt [offboarding](https://www.remakecv.com/help/account-and-billing/user-roles-and-permissions.md) | | Consultants sharing a device | Enforce | ## What if I lose access? Use a recovery code. If you have none, contact support@remakecv.com. We will need to verify your identity before resetting the factor, which necessarily takes longer than using a code you saved. ## Can we require it for everyone? Not with a switch — there is no company-wide enforcement setting. Two-factor authentication is enabled by each user on their own account, because setup needs their own device. In practice that makes it a rollout task rather than a configuration one: ### Make it part of onboarding Set it up on day one, before the account is used in anger. ### Ask existing users to enable it, with a date An open-ended request gets ignored. ### Check coverage Ask us at support@remakecv.com if you need to confirm who has it enabled. This matters most if your clients audit your security or you recruit in a regulated sector — the accounts most likely to be compromised are exactly the ones that would opt out. Two-factor authentication is one part of a wider picture — see [security, DPAs and sub-processors](https://www.remakecv.com/help/anonymisation-and-compliance/security-and-subprocessors.md). ## What about single sign-on? SAML single sign-on is supported and in use by enterprise customers. Users signing in through your identity provider are provisioned automatically on first login, and your provider's own MFA policy applies. Setup is handled by RemakeCV — email support@remakecv.com with your identity provider and the email domains it covers. ## Frequently asked questions ### Which authenticator apps work? Any app supporting time-based one-time passwords — Google Authenticator, Microsoft Authenticator, Authy, 1Password and most password managers. ### What if I lose my phone? Use one of your eight backup codes. Without them, recovery requires contacting support@remakecv.com to verify your identity, which takes longer. ### Can 2FA be required for everyone? Not through a setting — each user enables it on their own device, so company-wide adoption is a rollout task. If you need SSO instead, with MFA enforced by your identity provider, we support that. ### Do you support single sign-on? Yes. SAML SSO is available for enterprise accounts, with automatic user provisioning on first login. Email support@remakecv.com with your identity provider and email domains. --- # User roles and permissions > RemakeCV has administrators and standard users. Administrators manage company details, API keys and templates; formatting preferences are per user and CV history is shared. Source: https://www.remakecv.com/help/account-and-billing/user-roles-and-permissions Last updated: 2026-08-21 --- RemakeCV distinguishes administrators from standard users. Administrators manage company details, API keys and — where enabled — user accounts. Everything else is more open than people expect: formatting preferences are per user, CV history is visible across the company, and templates can be created by anyone who can see them. ## What can each role do? | Capability | Administrator | Standard user | |---|---|---| | Format, edit and download CVs | Yes | Yes | | See CV history across the company | Yes | Yes | | Set their own formatting preferences | Yes | Yes | | Create and edit templates they can see | Yes | Yes | | See templates restricted to other users | Yes | No | | Buy credit top-ups | Yes | Yes | | See the company credit usage log | Where enabled | No | | Edit company details, logo and branding | Yes | No | | Create and revoke API keys | Yes | No | | Add and remove users | Where enabled | No | > **Warning:** Note the second and third rows. **CV history is company-wide, not personal** — a consultant can see CVs processed by colleagues. And **formatting preferences are per user**, so two people can produce differently formatted output from the same template. Neither behaves the way most agencies assume, so check both against your expectations before rolling out. ## What is genuinely administrator-only? Four things: - **Company details** — logo, header logo, address, office number, licence number, header and footer colours. Non-administrators see a message telling them to contact their administrator. - **API keys** — creating and revoking keys in Company Settings → Public API. See [authentication](https://www.remakecv.com/help/api-reference/authentication.md). - **User management**, where your plan includes it. - **The credit usage log**, where your plan includes it. It names the consultant behind every credit spent, so only administrators can open it. See [credits and usage](https://www.remakecv.com/help/getting-started/credits-and-usage.md). ## Why can everyone change formatting settings? Because those settings belong to the user, not the company. Date format, section toggles, headers, footers and cover-page options are stored against each individual login. > **Tip:** This is the single most common cause of "why does my colleague's CV look different from mine?". Agree the settings as a team during onboarding and have each consultant apply them. See [date formats, section order and headings](https://www.remakecv.com/help/templates-and-branding/date-formats-and-sections.md). ## Restricting templates to specific users Separately from roles, individual templates can be limited to named users — most usefully for client-branded variants that should not be selectable by consultants working other accounts. This is configured by RemakeCV rather than self-serve; email support@remakecv.com with the template and who should see it. Administrators bypass the restriction and always see everything. See [template variants](https://www.remakecv.com/help/templates-and-branding/template-variants.md). ## Offboarding ### Remove the account on their last day Removal is permanent — there is no deactivated or suspended state. A dormant login with access to candidate data is a standing risk and a common audit finding. ### Revoke any API keys they created Company Settings → Public API. Check `last_used_at` afterwards to confirm nothing is still calling with that key. ### Reassign their credit allocation If they had a per-user limit or belonged to a shared pool, email support@remakecv.com to redistribute it. ### Check an administrator remains Make sure at least one active administrator is left — ideally more than one. ### Reauthorise any integration they connected Bullhorn and Vincere connect per consultant, and JobAdder connects once for the whole company. If the leaver made the JobAdder connection, it will fail for everyone. See [integration sync errors](https://www.remakecv.com/help/troubleshooting/integration-sync-errors.md). > **Warning:** Removing a user does not delete the CVs they processed. Those remain subject to your company retention window — see [GDPR and data retention](https://www.remakecv.com/help/anonymisation-and-compliance/gdpr-and-data-retention.md). ## How do I change someone's role? Email support@remakecv.com and we will promote them. Administrator rights carry company-wide control over templates, billing and users, so the change is made deliberately rather than by a stray click. ## Frequently asked questions ### Can consultants see each other's CV history? Yes. CV history is scoped to the company, not the individual, so consultants can see CVs processed across the agency. ### Can administrators add and remove users themselves? On some plans. Where self-serve user management is not enabled, the administrator tab does not appear and changes go through support@remakecv.com. ### How do I remove someone who has left? Ask an administrator, or email support@remakecv.com. Removal is permanent — there is no deactivated state — and it does not delete the CVs they processed. --- # Adjusting a formatted CV > How to adjust a formatted CV when a field, section or date needs changing — and how to make a recurring adjustment permanent in your template so you never make it twice. Source: https://www.remakecv.com/help/troubleshooting/formatting-looks-wrong Last updated: 2026-08-22 --- Every formatted CV is fully editable before it goes to a client. Adjust any field, role, date or bullet directly in the editor, and reprocess at any time without spending a credit. If you find yourself making the same adjustment on every CV, that is a template setting rather than a per-CV edit — tell us and we will build it in so it never comes up again. ## Adjusting a single CV The editor gives you the whole document. Open the CV, change what you need, and download — there is no limit on edits and no credit cost. | What you want to change | Where | |---|---| | A role, employer, title or date | Edit the field directly in the editor | | Which bullets sit under which role | Reassign them in the editor | | Content order within a section | Reorder entries and bullets in the editor | | A field the candidate never supplied | Add it — see [adding missing information](https://www.remakecv.com/help/formatting-cvs/adding-missing-information.md) | | The candidate summary | Edit or regenerate it | | The whole template | Switch template and regenerate, free of charge | > **Tip:** Reprocessing is free, so it is always worth one pass before hand-editing an unusual layout — a second read of an ambiguous document can resolve it for you. See [multi-column and design-heavy CVs](https://www.remakecv.com/help/troubleshooting/jumbled-and-multi-column-cvs.md). ## Making an adjustment permanent This is the part that saves the most time. Anything you change on *every* CV is configuration, not editing: | Recurring adjustment | Permanent fix | |---|---| | Reordering sections | Set section order in your template | | Renaming a heading | Set the heading in your template | | A consistent house date style | Configured for your agency once | | Removing a section you never use | Hide it at template level | | Adding a field to every CV | Build it into your template | See [date formats, section order and headings](https://www.remakecv.com/help/templates-and-branding/date-formats-and-sections.md), or email support@remakecv.com with the rule and we will apply it to your template. ## Working from a difficult source document Some source CVs are harder to read than others — a photographed scan, a design-led layout, an unusual heading like "My Journey" instead of "Work Experience". RemakeCV handles these automatically, and where a source is genuinely ambiguous the editor is there to finish the job in a few seconds. Two things worth knowing: - **A DOCX gives the richest result.** Word files carry real structure — headings are headings, tables are tables — so if a candidate has one, it is the best input you can give. - **A graphical heading has no text to read.** If a section heading in the original is an image rather than text, add the heading in the editor and the content follows. > **Tip:** Select the heading text in the source PDF. If you cannot select it, it is an image — which tells you immediately why it needs a heading adding rather than anything about the rest of the document. ## Tell us about a layout you see often If your desk sees the same source layout repeatedly and you would rather it needed no adjustment at all, that is something we tune at the pipeline level. Email support@remakecv.com with the **source file** and what the ideal output looks like — the source is what lets us reproduce and improve it. ## Frequently asked questions ### Does reprocessing cost a credit? No. Reprocessing an existing CV is free, so you can retry as often as you like. One credit covers a CV for all subsequent editing, reprocessing, anonymising and downloading. ### Can I change anything on a formatted CV before sending it? Yes. Every field is editable — roles, employers, dates, bullet points, section content and the summary. Nothing is locked, and edits never cost a credit. ### I make the same adjustment on every CV. Can that be automatic? Yes, and it should be. Recurring adjustments belong in your template — section order, headings, date style, hidden sections and custom fields are all configurable. Email support@remakecv.com and we will build it in. --- # Scanned and image-only PDFs (OCR) > RemakeCV reads scanned, photographed and image-only PDFs automatically using OCR, recovering content that has no text layer at all — including names held inside header graphics. Source: https://www.remakecv.com/help/troubleshooting/scanned-pdfs-and-ocr Last updated: 2026-08-22 --- RemakeCV reads scanned and image-only PDFs automatically. When a PDF has no usable text layer, optical character recognition runs over the page images and the CV is rebuilt from what it recovers — so a scan of a printed CV formats into your template like any other file. You can also invoke it deliberately with the **Image Process** option, which is the quickest way to recover a candidate name held inside a header graphic. ## When does OCR run? Automatically, whenever the document calls for it: 1. **The PDF has no text layer at all** — a scan or a photograph of a printed CV. OCR happens transparently during extraction. 2. **The text layer is present but sparse**, which indicates a broken or partial layer. 3. **The extracted text needs the page layout to be read properly** — see [multi-column and design-heavy CVs](https://www.remakecv.com/help/troubleshooting/jumbled-and-multi-column-cvs.md). A DOCX carries real structure and is read directly, so it never needs this path. ## Can I invoke OCR myself? Yes, and on some documents it is the fastest route. Alongside the default **Standard Process**, there is an **Image Process** option — settable for a whole upload or per file — plus a *reprocess as image* action on a CV you have already run. Reprocessing is always free. > **Tip:** Reach for Image Process when a CV's header is a graphic. The text layer of a designed PDF often omits header content entirely, which means the candidate's **name** can be held only in the image while the rest of the CV parses perfectly. OCR reads the header as a human sees it. ## What is worth a quick check Any CV that arrives as a scan is worth the same thirty-second review you would give it if you had retyped it yourself. In rough order of value: ### The candidate's name Names frequently sit inside a header graphic or stylised banner. If it looks off, Image Process is the fix. ### Email addresses and phone numbers Character-level detail matters most where it is a contact route, so it is worth a glance before the CV goes out. ### Dates `2013` and `2018` are one character apart on a poor scan. ### Registration and licence numbers Anything carrying legal or safety weight. See [custom extraction fields](https://www.remakecv.com/help/ai-tools/custom-extraction-fields.md). ## Why does a scanned CV take longer? Reading page images is a separate pass before parsing can begin, so a scanned document takes longer than a Word file — a few seconds on a typical CV. A large batch of scans takes correspondingly longer than the same number of DOCX files, which is worth knowing when you plan a bulk run. See [bulk formatting](https://www.remakecv.com/help/formatting-cvs/bulk-formatting.md). ## Very tall and continuous-scroll pages CVs exported from Canva, Notion and web page-builders are sometimes a single continuous page metres long rather than a set of A4 pages. Most tools render these too small to read anything. RemakeCV detects unusually tall pages, slices them into overlapping windows before reading, then stitches the results back together — so a continuous-scroll CV formats into your template like a normal document. ## Getting the best result from a scan | Source | Advice | |---|---| | Word version available | Best possible input, if the candidate has one to hand | | Clean flatbed scan | Reads well | | Phone photo of a printed CV | Usable; a flatter, better-lit photo reads more cleanly | | Skewed or low-contrast scan | Worth a quick review of names, dates and contact details | > **Tip:** None of this needs managing day to day — scans go through the same upload as everything else. It only matters when you are handling a large batch of them at once and want the cleanest possible run. ## Frequently asked questions ### Can RemakeCV read a scanned CV? Yes, automatically. If a PDF has no usable text layer, RemakeCV runs OCR over the page images and rebuilds the CV from the recovered content — no separate step and no different workflow. ### Do I need to do anything to enable OCR? No. RemakeCV switches to OCR by itself when a PDF needs it. You can also invoke it deliberately with the Image Process option, which helps when the candidate's name sits in a header graphic. ### The candidate's name is missing. What now? Names often sit inside header graphics, which a PDF's text layer omits. Reprocess with Image Process and the name is normally recovered — reprocessing is free. ### Can RemakeCV handle a CV exported from Canva or Notion? Yes. These export as a single continuous page rather than A4 sheets, and RemakeCV slices tall pages into overlapping windows before reading them, then stitches the result back together. --- # Multi-column, sidebar and design-heavy CVs > RemakeCV reconstructs the intended reading order of multi-column, sidebar and heavily designed PDFs automatically, so a creative CV becomes a clean branded document. Source: https://www.remakecv.com/help/troubleshooting/jumbled-and-multi-column-cvs Last updated: 2026-08-22 --- Multi-column and heavily designed PDFs store text as positioned fragments with no reading order, which is why copying and pasting one produces interleaved nonsense. RemakeCV checks the reading order of every PDF it extracts and, where the layout calls for it, re-reads the page the way a person would — recovering the intended order before the CV is rebuilt in your template. ## Why multi-column CVs defeat most tools A PDF does not store a document. It stores instructions for painting glyphs at coordinates. There is no "this is column one, read it first" — that structure exists only in the visual arrangement. So a naive text extraction of a two-column CV reads across the page, producing lines that alternate between the sidebar and the main body: ```text Alex Morgan Operations Manager SKILLS Northwind Logistics Lean Six Sigma 2019 – Present SAP Led a team of 12 across three Stakeholder mgmt distribution centres, reducing ``` Parsed as written, that is unusable — skills interleaved with employment history. This is the single most common reason a generic CV parser produces a scrambled result, and it is one of the specific problems RemakeCV was built to solve. ## How RemakeCV handles it Every PDF goes through a reading-order assessment after its text is extracted. Where the extracted order does not read coherently — the signature of columns, sidebars or a designed layout — RemakeCV re-reads the document from the page layout itself, recovering the order a person would read, and the CV is then parsed from that. This is automatic and applies to every PDF you upload. There is no setting to find and nothing to flag. > **Note:** You can also force a full page-layout read yourself with the **Image Process** option — useful if you already know a CV is heavily designed and want to skip straight to it. See [scanned PDFs and OCR](https://www.remakecv.com/help/troubleshooting/scanned-pdfs-and-ocr.md). ## Which layouts benefit most | Layout | What RemakeCV does | |---|---| | Two- and three-column CVs | Reconstructs column order before parsing | | Skills or contact sidebars | Associates sidebar content with the right section | | Timeline and infographic designs | Reads dates back to the roles they belong to | | Tables used for visual layout | Recovers reading order from the page rather than the cell order | | Designed headings and graphical section titles | Recognised from the page layout rather than the text layer | > **Tip:** Design-heavy CVs are most common in marketing, design and creative recruitment. If you work those desks, this is the part of the pipeline doing the most work for you — and it is worth a quick review of the output on the first few, so you can see how your template handles them. ## If something still needs adjusting Some source documents are genuinely ambiguous even to a human reader — a sidebar with no visual boundary, or a date floating between two roles. Where that happens: ### Reprocess Free, and never costs a credit. On an ambiguous layout a second pass can resolve it differently. ### Adjust the affected section in the editor Usually it is one section rather than the whole document. Fix that rather than starting over — see [reviewing and editing](https://www.remakecv.com/help/formatting-cvs/reviewing-and-editing.md). ### Tell us if a layout recurs A layout your desk sees repeatedly is something we can tune for at the pipeline level. Email support@remakecv.com with the source file. ## Does the client see the original layout? No, and that is the point. The output uses your agency template regardless of how the source looked. A candidate's two-column creative CV becomes a standard branded document — the layout is handled on the way in, and is never something your client sees. ## Frequently asked questions ### Can RemakeCV handle a two-column CV? Yes, and it is handled automatically. RemakeCV assesses the reading order of every PDF it extracts and re-reads the page layout where the columns would otherwise interleave. There is nothing to flag or configure. ### Do I need to tell RemakeCV that a CV is multi-column? No. Detection and handling are part of processing. You can also force a full page-layout read yourself with the Image Process option if you want to. ### Why does a two-column PDF need special handling at all? A PDF stores positioned text fragments, not reading order. Extracted naively, a two-column layout reads across both columns line by line, interleaving unrelated content. RemakeCV reconstructs the order a human would read instead. ### Will my client see the candidate's original layout? No. The output always uses your agency template, so a candidate's two-column creative CV arrives with your client as a clean, consistent branded document. --- # Upload failed or timed out > Diagnose a CV that will not upload — unsupported file type, a corrupted or unreadable PDF, duplicate filenames, or an account credit limit. Source: https://www.remakecv.com/help/troubleshooting/upload-failed Last updated: 2026-08-22 --- Uploads fail for two distinct reasons: a file problem or an account problem. Credit limits raise a dialog naming the limit; anything else surfaces as "Failed to upload and process file", which almost always means the document's text could not be extracted. The web app itself imposes no file size limit. ## First: which kind of failure is it? | What you see | Kind | |---|---| | A dialog titled **"No Credits Left"** or **"Credit Limit Reached"** | Account | | **"Failed to upload and process file"** | File | | **"Upload functionality is restricted for this account."** | Account | | **"Please select a file to upload"** | Nothing was attached | | A red error state on a file during a bulk upload | File — see below | The two kinds have nothing in common, so establishing which you have saves most of the diagnosis. ## Account problems | Dialog | Meaning | Fix | |---|---|---| | **No Credits Left** — "You have run out of credits. Please top up to continue using the service." | The company balance is exhausted | Top up, or wait for the billing cycle | | **Credit Limit Reached** — "You have reached your individual or shared credit limit for this period." | A per-user or shared-pool cap, while the company still has credits | Email support@remakecv.com — our team adjusts the limit at no cost | > **Tip:** These are genuinely different. "Credit Limit Reached" is a limit setting, not an empty balance — per-user limits and shared pools are set up by our team and changed at no cost. See [credits explained](https://www.remakecv.com/help/account-and-billing/credits-explained.md). ## File problems ### Check the format Only `.pdf`, `.doc` and `.docx` are supported for CVs. Convert anything else first. Note that the attachment pickers for interview notes and job descriptions accept a wider range including `.txt` — that is a different feature, and a `.txt` file cannot be used as a CV. ### Check the file opens on your machine If it will not open locally, it is corrupted and RemakeCV cannot read it either. Ask for a fresh copy. ### Check for protection or restrictions A PDF with encryption or permission restrictions may fail text extraction. Open it with the password and re-save without protection, then retry. ### Try a different CV If another file uploads fine, the problem is that document. If nothing uploads at all, it is your account, network or the service — see [service status](https://www.remakecv.com/help/reference/service-status.md). > **Warning:** "Failed to upload and process file" covers a few different causes, so it is worth working through the steps below in order rather than inferring a cause from the wording. In practice the great majority are resolved by the first two. ## Bulk uploads: two behaviours to know **Duplicate filenames are dropped before upload.** If you select several files with the same name, the duplicates are skipped with a warning, and only one is processed. A candidate whose CV "never processed" was often a second file with an identical name. **Failed files in a batch show a red status but no message.** In single-file mode you get "Failed to upload and process file"; in a batch you get a status indicator only. To see the actual error, retry that file on its own. See [bulk formatting](https://www.remakecv.com/help/formatting-cvs/bulk-formatting.md). ## What about file size? There is no size limit in the web app itself. Very large files still take longer to upload and process, and can hit limits imposed by your own network or a corporate proxy. The **10MB default does apply to the [public API](https://www.remakecv.com/help/api-reference/endpoints/process-a-cv.md)**, where it is configurable per company. If you are integrating and hitting that cap, email support@remakecv.com. ## Nothing uploads at all Then it is not the file: - Try a different browser, to rule out an extension blocking uploads - Check your network — corporate firewalls sometimes block large uploads - Check [`GET /health`](https://www.remakecv.com/help/api-reference/endpoints/health.md) if you use the API - Email support@remakecv.com with the time and what you saw ## Frequently asked questions ### Is there a file size limit in the web app? No. The 10MB limit applies to the public API, where it is configurable per company. The web app itself does not enforce one, though very large files take longer and may hit network limits. ### Can I upload a .txt CV? No. CVs must be .pdf, .doc or .docx. The .txt option you may have seen belongs to the interview-notes and job-description attachment fields, which are a separate feature. ### Does a failed upload use a credit? No. A credit is deducted only after a CV parses successfully. --- # The downloaded DOCX doesn't look right in Word > Fonts substituted, spacing shifted, an extra page appearing — almost always caused by fonts that aren't installed on the machine opening the file. Source: https://www.remakecv.com/help/troubleshooting/docx-wont-open Last updated: 2026-08-21 --- If a downloaded DOCX looks different from what you saw in RemakeCV, the cause is nearly always font substitution. A DOCX references fonts by name rather than embedding them, so Word substitutes a different font when the original is not installed — and substituted fonts have different metrics, which shifts spacing and line breaks. ## Why fonts cause this | Format | Font handling | Consequence | |---|---|---| | **PDF** | Fonts embedded in the file | Renders identically on every machine | | **DOCX** | Fonts referenced by name | Falls back to a substitute when not installed | A substitute font is rarely the same width. Slightly wider characters push a line onto the next line, which pushes a paragraph onto the next page — so a two-page CV becomes three. > **Tip:** The test that proves it: open the same DOCX on a machine that has the template's fonts installed. If it looks correct there and wrong elsewhere, it is font substitution, not a template fault. ## How do I fix it? ### Send PDF instead The complete fix. Fonts are embedded, so the document looks the same for everyone. See [downloading as DOCX or PDF](https://www.remakecv.com/help/formatting-cvs/downloading-docx-pdf.md). ### Or install the font on the affected machines Works internally where you control the machines. Does not work for clients. ### Or switch the template to an Office-safe font The right answer if your agency must send DOCX files. Email support@remakecv.com. Office-safe fonts include Calibri, Cambria, Georgia, Garamond, Arial, Times New Roman, Verdana and Trebuchet MS. ## Other DOCX symptoms | Symptom | Cause | Fix | |---|---|---| | Extra blank page at the end | Substituted font pushing content over | Fix the font, or send PDF | | Bullets misaligned | Font substitution changing list metrics | As above | | Logo blurry | Low-resolution source logo | Send us an SVG or high-resolution PNG | | Different on Mac vs Windows | Different installed font sets | Send PDF | | Won't open at all | Corrupted download | Download again | | Opens in Protected View | Windows marking a downloaded file | Click Enable Editing — this is normal Windows behaviour | ## Should we standardise on PDF? For client submissions, yes. PDF removes this entire class of problem, and it is also the right format for [anonymised CVs](https://www.remakecv.com/help/anonymisation-and-compliance/auto-anonymisation.md), because DOCX carries document metadata that can identify a candidate. Keep DOCX for the cases that genuinely need it: a client who asks for an editable file, or a CV you will tailor further before sending. ## Frequently asked questions ### Why does the CV look fine for me but wrong for my client? You have the template's fonts installed and they do not. Send PDF, which embeds fonts and renders identically everywhere. ### Why is there an extra page at the end? Substituted fonts are usually slightly wider, so content that fitted on two pages spills onto a third. Fixing the font fixes the page count. ### Should we just always send PDF? Unless the client specifically needs an editable file, yes. It removes this whole category of problem. --- # Integration sync errors > Diagnose a broken ATS connection — expired authorisation, insufficient permissions, or per-user access — across Bullhorn, Vincere, JobAdder, Salesforce and Mercury. Source: https://www.remakecv.com/help/troubleshooting/integration-sync-errors Last updated: 2026-08-21 --- Most integration failures are authorisation problems. Reauthorise the connection first — tokens expire and can be revoked when ATS passwords change. If reauthorising does not fix it, check the permissions granted at authorisation, then whether the affected consultant has access in the ATS itself. ## Diagnose by symptom | Symptom | Likely cause | Fix | |---|---|---| | Was working, now fails | Token expired or revoked | Reauthorise | | Authorisation error on connect | Insufficient rights to authorise apps | Have an ATS administrator do it | | Connects, cannot read candidates | Read permission not granted | Reauthorise, accept all permissions | | Connects, cannot attach the result | Write permission not granted | Reauthorise, accept all permissions | | Works for some users only | Bullhorn and Vincere connect **per consultant** | That consultant connects their own account | | Nothing appears on the candidate record | Integration not enabled for that user | Check integration settings | | Vincere: "not configured for this company" | Tenant not provisioned by RemakeCV | Contact support — there is no field for you to fill in | | Vincere: document type rejected | Vincere user permissions, not the connection | Adjust permissions in Vincere | | Mercury: "credentials not configured" | Not enabled for your account | Contact support | | Salesforce: object or field errors | Your org's schema differs from what the integration expects | Send us your object and field names | ## The standard sequence ### Reauthorise Expired or revoked tokens are the most common cause on Bullhorn, Vincere and JobAdder. Do this before investigating anything else — it takes a minute and is non-destructive. It does not apply to Salesforce or Mercury, which have no customer-side authorisation to renew. ### Accept every permission A partial grant connects successfully and then fails at the first operation that needs the missing scope. That looks like an intermittent fault but is not. ### Check who authorised The authorising account needs rights to grant access to third-party applications. In most agencies that is an ATS administrator, not a consultant. ### Test with one candidate Confirm the full round trip on a single record before concluding it is fixed. ### Check the affected user specifically If it works for you and not for a colleague, the difference is their ATS permissions, not the connection. > **Warning:** Reauthorising is safe and non-destructive — it refreshes the connection without affecting templates, CV history or credits. There is no reason to hesitate before trying it. ## Why do connections expire? Delegated authorisations are deliberately time-limited, and are revoked by: - The authorising user changing their ATS password - An ATS administrator revoking third-party application access - The authorising user being deactivated — a common one after someone leaves - A security policy change in the ATS or identity provider > **Tip:** For JobAdder, which connects once for the whole company, authorise with an account that will outlast individual staff. When the authorising consultant leaves and their ATS account is deactivated, the integration goes with them — for everyone. ## Still not working? Email support@remakecv.com with: - Which platform, and which consultant is affected - What you were doing and what happened - Whether reauthorising was tried - The approximate time, so we can find it in the logs Platform-specific causes are covered on each setup page — [Bullhorn](https://www.remakecv.com/help/integrations/bullhorn.md), [Vincere](https://www.remakecv.com/help/integrations/vincere.md), [JobAdder](https://www.remakecv.com/help/integrations/jobadder.md), [Salesforce](https://www.remakecv.com/help/integrations/salesforce.md) and [Mercury](https://www.remakecv.com/help/integrations/mercury.md). ## Is there a workaround while it is broken? Yes — upload manually. Download the CV from your ATS, upload it to RemakeCV, and attach the result back by hand. Slower, but nothing is blocked. See [uploading a CV](https://www.remakecv.com/help/formatting-cvs/uploading-a-cv.md). ## Frequently asked questions ### Why did a working integration suddenly stop? On Bullhorn, Vincere and JobAdder, usually an expired or revoked token — reauthorise. Salesforce and Mercury have no token to expire, so there the cause is configuration or a service problem. ### Why does it work for some consultants and not others? Bullhorn and Vincere connect per consultant, so each person must connect their own account. JobAdder connects per company, so there the cause is more likely ATS permissions. ### Why can it read candidates but not attach the formatted CV? On JobAdder, the authorisation was granted without write permission — reauthorise and accept every requested permission. On Bullhorn, check the user's entitlements in Bullhorn itself. --- # Error code reference > Every error message RemakeCV can show, what causes it, and how to resolve it — covering the web app and the public API. Source: https://www.remakecv.com/help/troubleshooting/error-codes Last updated: 2026-08-21 --- This page lists every error RemakeCV can return, in the app and through the API, with its cause and resolution. API errors are identified by a machine-readable `code` and carry a `request_id`; log that identifier, because it is what support needs to trace the specific call. ## Application messages | Message | Cause | Resolution | |---|---|---| | Dialog: **No Credits Left** — "You have run out of credits. Please top up to continue using the service." | The company credit balance is exhausted | Top up, or wait for the billing cycle to refresh | | Dialog: **Credit Limit Reached** — "You have reached your individual or shared credit limit for this period." | An individual or shared-pool cap was hit while the company still has credits | Email support@remakecv.com — our team sets per-user and shared-pool limits. See [credits explained](https://www.remakecv.com/help/account-and-billing/credits-explained.md) | | `Please select a file to upload` | No file was attached | Select the file | | `Please select files to upload` | Bulk upload started with no files | Select the files | | `Failed to upload and process file` | Upload or processing failed | See [upload failed](https://www.remakecv.com/help/troubleshooting/upload-failed.md) | | `Upload functionality is restricted for this account.` | Account-level restriction | Contact your administrator or support | | `Company configuration not loaded. Please try again.` | Company settings did not load | Refresh; if it persists, contact support | | `No file available to regenerate summary` | Summary requested with no source CV loaded | Reopen the CV first | | `Error regenerating summary` | Summary generation failed | Retry; if it persists, contact support | | `Could not accept all changes. Please retry or accept changes in smaller batches.` | Too many edits applied at once | Accept changes in smaller groups | | `Could not process the selected file from JobAdder.` | The file could not be retrieved from JobAdder | See [integration sync errors](https://www.remakecv.com/help/troubleshooting/integration-sync-errors.md) | | `Too many Vincere requests. Please retry shortly.` | Vincere requests are rate limited per company | Wait and retry | | `Failed to search for candidates.` / `Failed to upload CV.` / `Failed to create contact from CV.` | Mercury operation failed | See [Mercury](https://www.remakecv.com/help/integrations/mercury.md) | | `Failed to convert DOCX to PDF` | PDF generation failed server-side | Retry; if it persists, contact support | | `Unsupported file type. Please upload a PDF, DOCX, or DOC file.` | The file is not a supported format | Convert the file | | A red status on a file in a bulk upload, with no message | A per-file failure in batch mode | Retry that file on its own to see the actual error | ## API error codes Every API error returns `code`, `message` and `request_id`. | Status | Code | Cause | Resolution | |---|---|---|---| | `400` | `validation_error` | Malformed request, or file over the size limit | The message names the specific problem | | `400` | `upload_required` | No file supplied where one is required | Send the file in the `file` multipart field | | `400` | `acting_user_required` | `acting_user_email` missing | Add it | | `400` | `storage_required` | Operation needs CV storage, which is disabled | Enable CV storage | | `401` | `unauthorized` | `Authorization` header missing or malformed | Send `Authorization: Bearer ` | | `401` | `invalid_api_key` | Key not found, inactive, revoked or expired | Check or replace the key | | `403` | `api_disabled` | Public API not enabled for this company | Email support@remakecv.com | | `403` | `cv_storage_disabled` | CV storage is off, so stored CVs cannot be listed | Enable storage, or use `download_url` at processing time | | `403` | `forbidden` | Key not permitted for this resource | Confirm the resource belongs to your company | | `404` | `not_found` | CV does not exist for this company | Check the `cvId` | | `404` | `company_not_found` | The key's company no longer exists | Contact support | | `404` | `acting_user_invalid` | Acting user is not a member of this company | Use a valid consultant email | | `429` | `rate_limit_exceeded` | Over 30 requests per minute | Back off — see [rate limits](https://www.remakecv.com/help/api-reference/rate-limits.md) | | `500` | `internal_error` | Failure on our side | Retry once, then send us the `request_id` | | `400` / `500` | `process_failed` | CV processing failed — **including credit rejections** | Read `message`; see below | | `400` / `500` | `storage_failed` | The CV processed but could not be stored | Retry; the `download_url` from the response may still work | > **Warning:** **Credit failures arrive as `process_failed`, not a dedicated code.** A company out of credits returns `400 process_failed` with `message` set to `No credits left`, and a per-user cap returns the same code with `credit limit reached`. If you need to handle these distinctly — and you should, since one needs a top-up and the other a limit change from our team — branch on `message` for these two cases specifically. > **Tip:** Log `request_id` for every API error, alongside the endpoint and the acting user. That combination lets support reconstruct almost any failure without a further round trip — and it is returned in the `X-Request-Id` header on successful responses too. ## Retry policy | Category | Retry? | |---|---| | `429` | Yes — exponential backoff with jitter | | `5xx` | Once, then escalate | | `4xx` | No — the request itself needs fixing | ## Reporting an error Email support@remakecv.com with: - The exact message or error code - The `request_id` if it was an API call - What you were doing and roughly when - The source CV, if it was a processing failure ## Frequently asked questions ### What is a request_id? A unique identifier for one API call, returned in every error body and in the X-Request-Id header on every response. Include it when contacting support. ### Do errors consume credits? Almost never — credits are deducted only after a CV parses successfully. The one exception is an API storage_failed, where processing succeeded and only the storage step failed, so the credit has already been spent. ### Which errors are worth retrying? 429 rate_limit_exceeded with backoff, and 500 internal_error once. Every 4xx error will fail identically on retry. --- # Glossary of CV formatting and recruitment terms > Definitions of the terms used across RemakeCV and recruitment CV formatting — ATS, anonymisation, credits, OCR, parsing, templates and more. Source: https://www.remakecv.com/help/reference/glossary Last updated: 2026-08-21 --- This glossary defines the terms used throughout RemakeCV and in recruitment CV formatting generally — from ATS and applicant tracking through to OCR, parsing, reading order, anonymisation, credits, acting users and template variants. Each entry is a standalone definition you can read without the surrounding page. ## The terms people look up most | Term | In one line | |---|---| | **ATS** | Software that tracks candidates through hiring — Bullhorn, Vincere, JobAdder | | **Anonymisation** | Removing identifying details from a CV while keeping the substance | | **Credit** | One CV processed; covers all later editing and downloading of that CV | | **OCR** | Reading text from an image, used when a PDF has no text layer | | **Parsing** | Deciding what extracted text *means* — which part is an employer, a date, a title | | **Reading order** | The order a human reads a page; PDFs do not store it | | **Template** | Your agency's CV design, applied to every CV you format | ## Recruitment terms **ATS (Applicant Tracking System)** Software that manages candidates through the hiring process — storing records, tracking applications and holding CVs. Bullhorn, Vincere, JobAdder and Mercury are examples. RemakeCV integrates with an ATS rather than replacing it. **Blind recruitment** A hiring process in which identifying details are removed from candidate CVs before a hiring manager sees them, to reduce bias. Also called anonymous or blind hiring. See [auto-anonymisation](https://www.remakecv.com/help/anonymisation-and-compliance/auto-anonymisation.md). **Candidate submission** The act of sending a formatted candidate CV to a client, usually with a covering message explaining the fit. **CRM (Candidate Relationship Management)** Software for managing ongoing relationships with candidates and clients. In recruitment the terms CRM and ATS are often used interchangeably. **Preferred supplier agreement (PSA)** An arrangement in which a client works with a defined list of agencies. PSAs frequently specify the CV template submissions must use, which is why [template variants](https://www.remakecv.com/help/templates-and-branding/template-variants.md) exist. **Shortlist** The set of candidates an agency puts forward for a role. Consistency across a shortlist is a common reason to use [bulk formatting](https://www.remakecv.com/help/formatting-cvs/bulk-formatting.md). ## CV formatting terms **Anonymisation** Removing or replacing identifying information in a CV — name, contact details, employers, institutions — while keeping the substance. Note that anonymised CVs may still be personal data under GDPR if the person remains identifiable. **Extraction** Pulling raw text out of a document. The first stage of formatting, before any structure is identified. **First-person neutralisation** Rewriting a CV written as "I managed a team" into neutral ("Managed a team") or third-person phrasing. See [first-person neutralisation](https://www.remakecv.com/help/anonymisation-and-compliance/first-person-neutralisation.md). **OCR (Optical Character Recognition)** Recognising text in an image. Used when a PDF has no text layer — a scan or a photograph. See [scanned PDFs and OCR](https://www.remakecv.com/help/troubleshooting/scanned-pdfs-and-ocr.md). **Parsing** Working out what extracted text *means* — which text is a job title, which is an employer, which is a date range. The stage that turns a wall of text into structured data. **Processing method** Whether a CV was read from a text layer (`text`) or via OCR (`image`). Recorded on every processed CV. **Reading order** The order a human reads a document. PDFs do not store it, which is why multi-column layouts can extract in a jumbled sequence. See [jumbled and multi-column CVs](https://www.remakecv.com/help/troubleshooting/jumbled-and-multi-column-cvs.md). **Structured data** The result of parsing: employers, titles, dates and bullets as discrete fields rather than free text. What gets rendered into a template. **Text layer** The machine-readable text inside a PDF. A scanned PDF has none, which is what triggers OCR. ## RemakeCV terms **Acting user** The consultant an API request is made on behalf of. Determines template visibility and which credit limits apply. See [authentication](https://www.remakecv.com/help/api-reference/authentication.md). **Bulk formatting** Processing several CVs in one batch. Five are processed concurrently and the rest queue. See [bulk formatting](https://www.remakecv.com/help/formatting-cvs/bulk-formatting.md). **Credit** The unit of usage. One credit formats one CV, and covers all subsequent editing, anonymising and downloading of that CV. See [how credits and usage work](https://www.remakecv.com/help/getting-started/credits-and-usage.md). **Custom extraction field** An agency-specific field extracted from every CV — security clearance, licence category, registration number. See [custom extraction fields](https://www.remakecv.com/help/ai-tools/custom-extraction-fields.md). **CV storage** A company-level setting controlling whether processed CVs are retained. When disabled, there is no CV history. See [GDPR and data retention](https://www.remakecv.com/help/anonymisation-and-compliance/gdpr-and-data-retention.md). **Reprocessing** Running extraction again on a CV already in the system. Does not consume a credit. **Shared pool** A credit allocation shared between a named group of users. See [credits explained](https://www.remakecv.com/help/account-and-billing/credits-explained.md). **Signed URL** A time-limited link granting access to a stored file without authentication. Expires — never store or share one. See [`GET /cvs/{cvId}/file`](https://www.remakecv.com/help/api-reference/endpoints/get-cv-file.md). **Template** Your agency's CV design: fonts, colours, logo, section order, headings and custom fields. Owned at company level. See [template basics](https://www.remakecv.com/help/templates-and-branding/template-basics.md). **Template variant** A version of a template for a specific situation — a client's branding, an anonymised layout, or one without a cover page. **User limit** A per-consultant cap on credit usage within a billing cycle. Takes precedence over any shared pool the user also belongs to. ## Frequently asked questions ### What does ATS stand for? Applicant Tracking System — software that manages candidates through the hiring process, storing records, tracking applications and holding CVs. Bullhorn, Vincere, JobAdder and Mercury are examples. ### What is the difference between extraction and parsing? Extraction pulls raw text out of a document. Parsing works out what that text means — which part is a job title, which is an employer, which is a date range. Extraction comes first. ### What is a credit in RemakeCV? One credit formats one CV, and covers all subsequent editing, anonymising, summarising and downloading of that CV. Reprocessing does not consume a second credit. ### What is blind recruitment? A hiring process in which identifying details are removed from candidate CVs before a hiring manager sees them, to reduce bias. Also called anonymous or blind hiring. --- # Frequently asked questions > Answers to the questions agencies ask most about RemakeCV — how it works, what it costs, data security, file formats, integrations and support. Source: https://www.remakecv.com/help/reference/faq Last updated: 2026-08-22 --- RemakeCV is an AI CV formatting platform for recruitment agencies. It reformats candidate CVs into your branded template, anonymises candidates for blind hiring, and integrates with major ATS platforms. Pricing is per user per month with pooled credits, at one credit per CV processed. ## At a glance | Question | Short answer | |---|---| | What is it? | AI CV formatting for recruitment agencies | | File types | `.pdf`, `.doc`, `.docx`, including scanned PDFs | | Pricing | From $25 per user/month billed annually | | Credits | One per CV processed; 30 per user per month on Business | | Integrations | Bullhorn, Vincere, JobAdder, Salesforce, Mercury, plus a REST API | | Data | CV storage is a setting you control; CVs are never used to train AI models | ## About the product **What is RemakeCV?** An AI-powered platform that formats candidate CVs into a clean, branded layout, making them easier for clients to read and compare. See [what is RemakeCV](https://www.remakecv.com/help/getting-started/what-is-remakecv.md). **How does it work?** It extracts the content of a CV, parses it into structured fields, then renders those fields into your agency template. See [how AI formatting works](https://www.remakecv.com/help/formatting-cvs/how-ai-formatting-works.md). **Does it rewrite the candidate's words?** No. The parser decides where content goes, not what it says. Summaries, cover messages and first-person neutralisation are separate opt-in features. **How much time does it save?** Agencies consistently report 10+ hours per person per month, by removing the retyping step from every submission. ## Files and formats **Which file types work?** `.pdf`, `.doc` and `.docx`. See [supported file types](https://www.remakecv.com/help/getting-started/supported-file-types.md). **Can it read a scanned CV?** Yes, via OCR, applied automatically when a PDF has no usable text layer. See [scanned PDFs and OCR](https://www.remakecv.com/help/troubleshooting/scanned-pdfs-and-ocr.md). **What about a two-column CV?** RemakeCV detects when extracted text is in a jumbled reading order and re-extracts via OCR to recover the intended order. See [jumbled and multi-column CVs](https://www.remakecv.com/help/troubleshooting/jumbled-and-multi-column-cvs.md). ## Pricing and credits **How much does it cost?** The Business plan is $35 per user/month, or $25 billed annually. Enterprise is priced to volume. See [plans and pricing](https://www.remakecv.com/help/account-and-billing/plans-and-pricing.md). **How many credits do I get?** 30 per user per month on Business, pooled across the company. **What uses a credit?** Processing a new CV, and nothing else. Editing, anonymising, summarising, regenerating and re-downloading are free. See [how credits and usage work](https://www.remakecv.com/help/getting-started/credits-and-usage.md). **Can I upgrade?** At any time, on any plan. Annual upgrades are pro-rated. See [upgrading and downgrading](https://www.remakecv.com/help/account-and-billing/upgrading-and-downgrading.md). ## Data and security **Is my data secure?** Data is encrypted in transit and stored in access-controlled infrastructure, with two-factor authentication on all accounts. AI processing runs on OpenAI under an enterprise agreement with zero data retention and no training on customer data, and EU data residency is available on request. See [security and sub-processors](https://www.remakecv.com/help/anonymisation-and-compliance/security-and-subprocessors.md). **Are candidate CVs used to train AI models?** No. **Do you store candidate CVs?** Only if CV storage is enabled for your company — it is a setting you control, and some agencies disable it entirely. See [GDPR and data retention](https://www.remakecv.com/help/anonymisation-and-compliance/gdpr-and-data-retention.md). **Can I get a DPA?** Yes. Email support@remakecv.com. ## Features **Can it anonymise CVs?** Yes — names, contact details, employers and institutions are removed or neutralised, while quantified achievements are preserved. See [auto-anonymisation](https://www.remakecv.com/help/anonymisation-and-compliance/auto-anonymisation.md). **Can I add information not in the CV?** Yes. See [adding information that wasn't on the original CV](https://www.remakecv.com/help/formatting-cvs/adding-missing-information.md). **Can I have my own template?** Yes — send us your existing Word template and we rebuild it. See [requesting a custom template](https://www.remakecv.com/help/templates-and-branding/requesting-a-custom-template.md). **Which ATS platforms integrate?** Bullhorn, Vincere, JobAdder, Salesforce and Mercury, plus a [public REST API](https://www.remakecv.com/help/api-reference/introduction.md) for anything else. ## Support **How do I get help?** Email support@remakecv.com, or [book a call](https://www.remakecv.com/contact). Business plans have same-day response; Enterprise has priority support. ## Frequently asked questions ### What is RemakeCV? An AI-powered platform that formats candidate CVs into a clean, branded layout for recruitment agencies, making them easier for clients to read and compare. ### How does RemakeCV work? Upload a CV and the AI extracts its content, then reformats it into your agency template, highlighting key skills and experience. ### Is my data secure with RemakeCV? Candidate data is encrypted in transit and stored in access-controlled infrastructure. AI processing runs on OpenAI under an enterprise agreement with zero data retention, so candidate data is not retained after processing and is never used to train models. EU data residency is available on request, and whether CVs are stored at all is a company-level setting you control. ### Can RemakeCV handle different CV formats? Yes. It works with .pdf, .doc and .docx, including scanned and image-only PDFs, which are processed via OCR. ### How much time can RemakeCV save? Recruitment agencies consistently report saving 10+ hours per person per month by automating CV formatting. ### What makes RemakeCV different from other tools? It handles messy real-world CVs — scanned documents, multi-column layouts, cut-off sentences — rather than only clean ones, and it renders into your own agency template rather than a generic layout. ### Can I add information that wasn't in the candidate's CV? Yes. Expected salary, notice period, client name, consultant details and your own notes can all be added in the editor, and can be built into your template so they appear on every CV. ### Can I upgrade my package? Yes, at any time on any plan. On annual plans the upgraded fee is pro-rated for the remaining year. Email support@remakecv.com. ### How many credits does one CV use? One. That credit covers all subsequent editing, anonymising, summarising and downloading of that CV. ### Which ATS platforms do you integrate with? Any ATS or CRM. Bullhorn, Vincere, JobAdder, Salesforce and Mercury are live native integrations, and our team builds integrations with other platforms on request using the API credentials your provider supplies. --- # Service status and reporting an outage > How to check whether RemakeCV is up, distinguish a service problem from a local one, and report an outage effectively. Source: https://www.remakecv.com/help/reference/service-status Last updated: 2026-08-21 --- To check whether RemakeCV is up, call the API health endpoint first — `GET /api/public/v1/health` returns `{"status":"ok"}` without authentication, so it separates a service outage from a credential or network problem. If it responds but the app does not work for you, the problem is likely local. Report outages to support@remakecv.com. ## Is it us or you? ### Check the health endpoint ```bash curl https://app.remakecv.com/api/public/v1/health ``` A response of `{"status":"ok"}` means the service is reachable. No authentication needed. See [`GET /health`](https://www.remakecv.com/help/api-reference/endpoints/health.md). ### Ask a colleague If it works for them, the problem is your browser, network or account rather than the service. ### Try a different browser or network Rules out an extension, a cached asset, or a corporate firewall. ### Read the error carefully Many apparent outages are account conditions — "No credits left" and "credit limit reached" both stop processing without anything being down. See [error codes](https://www.remakecv.com/help/troubleshooting/error-codes.md). ## Slow is not always down Some things are legitimately slower: | Situation | Expected | |---|---| | Text-based CV | 10–30 seconds | | Scanned CV requiring OCR | Noticeably longer | | Bulk batch | Five concurrent, the rest queued | | Large file | Longer upload before processing starts | Before reporting slowness, process a small text-based CV. If that is fast, the pipeline is healthy and the delay is input-specific. ## Reporting an outage Email support@remakecv.com with: - **What you were doing** — uploading, downloading, using an integration - **What happened** — the exact message, or a description - **When** — approximate time and timezone - **Scope** — just you, or everyone at your agency - **`request_id`** — if it was an API call. This is the single most useful thing you can include > **Tip:** Screenshot the error before dismissing it. A description of a message is much harder to trace than the message itself. ## What if I am mid-submission? If you have a formatted CV open, download it before troubleshooting. Even if it is imperfect, a downloaded file is a file you can send. If CV storage is disabled for your company, this matters more — there is no history to return to. See [CV history](https://www.remakecv.com/help/formatting-cvs/cv-history.md). ## Frequently asked questions ### How do I check if RemakeCV is down? Call GET /api/public/v1/health. It requires no authentication and returns {"status":"ok"} when the service is reachable. ### Processing is slow but not failing. Is that an outage? Not necessarily. Scanned CVs run through OCR and are legitimately slower. Compare against a text-based CV before reporting it. ### What should I include when reporting a problem? What you were doing, what happened, the time, and the request_id if it was an API call. --- # RemakeCV API introduction > The RemakeCV public API is a company-scoped REST interface for processing CVs, retrieving stored results and listing templates. Base URL https://app.remakecv.com/api/public/v1. Source: https://www.remakecv.com/help/api-reference/introduction Last updated: 2026-08-21 --- The RemakeCV public API is a REST interface scoped to your company. It has six endpoints covering CV processing, retrieval and templates. Authenticate with a bearer API key, send requests to `https://app.remakecv.com/api/public/v1`, and every response comes back in a consistent envelope with `data`, `pagination` and `error` fields. ## Base URL ``` https://app.remakecv.com/api/public/v1 ``` All endpoint paths below are relative to this base URL. > **Note:** A company administrator enables the API and creates keys in **Company Settings → Public API** — no support ticket needed. See [authentication](https://www.remakecv.com/help/api-reference/authentication.md). > **Warning:** **CV storage must be enabled for your company before `POST /cvs/process` will work.** Without it, every call runs the full pipeline, spends a credit, and returns `400 storage_required`. Email support@remakecv.com to check. ## What can it do? | Method | Path | Purpose | |---|---|---| | `GET` | `/health` | Check the API is reachable. No authentication | | `POST` | `/cvs/process` | Upload and format a CV | | `GET` | `/cvs` | List stored CVs | | `GET` | `/cvs/{cvId}` | Get one stored CV's detail | | `GET` | `/cvs/{cvId}/file` | Get a signed URL for the stored file | | `GET` | `/templates` | List templates visible to a user | ## The response envelope Every successful response uses the same shape, so a client can parse them uniformly: ```json { "data": { }, "pagination": null, "error": null } ``` - **`data`** — the result. An object or an array, depending on the endpoint. - **`pagination`** — populated on list endpoints, `null` elsewhere. - **`error`** — always `null` on success. Errors use a different envelope. See [errors](https://www.remakecv.com/help/api-reference/errors.md). ## Your first request ### Check connectivity `GET /health` needs no authentication and returns `{"status":"ok"}`. If this fails, the problem is network-level rather than a credential problem. ```bash curl https://app.remakecv.com/api/public/v1/health ``` ### Authenticate Every other endpoint needs `Authorization: Bearer `. See [authentication](https://www.remakecv.com/help/api-reference/authentication.md). ### List your templates A good first authenticated call — it confirms the key works and shows you the template IDs you will pass when processing. ```bash curl "https://app.remakecv.com/api/public/v1/templates?acting_user_email=consultant@agency.com" \ -H "Authorization: Bearer $REMAKECV_API_KEY" ``` ### Process a CV `POST /cvs/process` with the file and the acting consultant's email. See [process a CV](https://www.remakecv.com/help/api-reference/endpoints/process-a-cv.md). ## Things to know before you build - **The API extracts and stores; it does not render.** `download_url` gives you the source CV as a PDF, not a document rendered into your template. - **`acting_user_email` applies to two endpoints only** — `POST /cvs/process` and `GET /templates`. - **The default rate limit is 30 requests per minute** per company, configurable. See [rate limits](https://www.remakecv.com/help/api-reference/rate-limits.md). - **The default maximum file size is 10MB**, configurable per company. - **Every response carries an `X-Request-Id` header**, including `/health` and errors. Log it — it is what support needs to trace a specific call. - **One credit per CV processed**, drawn from the same pool as the web app. ## Machine-readable specification The OpenAPI 3.1 specification is published at [`/openapi/public-api.v1.yaml`](https://www.remakecv.com/openapi/public-api.v1.yaml). Point your client generator or coding agent at it directly. ## Frequently asked questions ### How do I get access to the API? A company administrator enables it and creates a key in Company Settings under Public API. CV storage must also be enabled for your company, which does need a word with support@remakecv.com. ### Can the API return a CV formatted into our template? The public API parses and stores CVs, and download_url returns the source file as a PDF. For branded, template-rendered output, use the web app or a native integration — our team builds those for any ATS. ### Is there a sandbox environment? There is no separate sandbox. Use GET /health to verify connectivity without authentication, and process a test CV against your live key when you are ready. ### Does the API cost extra? No separate fee. API usage draws on the same credit pool as the web app — one credit per CV processed. --- # Authentication > Authenticate to the RemakeCV API with a bearer API key. Keys are company-scoped, stored hashed, can be given an expiry, and are revocable at any time. Source: https://www.remakecv.com/help/api-reference/authentication Last updated: 2026-08-21 --- Send your API key as a bearer token in the `Authorization` header. Company administrators create and revoke keys themselves in Company Settings under **Public API**. Keys are scoped to one company and stored hashed, so the secret is shown only once at creation. ## How do I authenticate? ```bash curl "https://app.remakecv.com/api/public/v1/templates?acting_user_email=consultant@agency.com" \ -H "Authorization: Bearer $REMAKECV_API_KEY" ``` The header must be exactly `Authorization: Bearer `. A missing or malformed header returns `401 unauthorized`. ## How do I get a key? Self-serve, if you are a company administrator. ### Open Company Settings → Public API The tab appears only for administrators. ### Enable the public API Toggle it on for your company — you only need to do this once. ### Create a named key Give it a name identifying the integration. The secret is displayed **once** — copy it immediately, because it cannot be shown again. ### Revoke keys you no longer need Revocation takes effect immediately; requests with that key start failing at once. Keys look like `rcv_` followed by 48 hex characters. The table shows each key's name, prefix, status and when it was last used. > **Note:** A few account-level settings are configured by us rather than in the dashboard — the rate limit, the maximum file size, the API's default template and key expiry dates. Email support@remakecv.com and we will set them for your company. ## What is the acting user, and when is it required? `acting_user_email` identifies the consultant a request is on behalf of. It is required on **two endpoints only**: | Endpoint | Acting user | |---|---| | [`POST /cvs/process`](https://www.remakecv.com/help/api-reference/endpoints/process-a-cv.md) | Required | | [`GET /templates`](https://www.remakecv.com/help/api-reference/endpoints/list-templates.md) | Required | | `GET /cvs`, `GET /cvs/{cvId}`, `GET /cvs/{cvId}/file` | Not used — scoped by company | Where it applies, it is not metadata. It determines: - **Which templates are visible.** Template visibility can be scoped to specific users. - **Which credit limits apply.** Per-user limits and shared pools are checked against this address. - **What appears in usage logs.** Credit usage is attributed to this user. > **Warning:** Pass the real consultant's email, not a shared service account. Routing every API call through one address collapses your per-user credit limits into a single bucket and makes usage reporting meaningless. ## How are keys stored? Keys are never stored in plain text. RemakeCV holds a SHA-256 lookup hash for fast retrieval and a bcrypt hash for verification. This is why a key cannot be shown again after creation — if it is lost, create a new one and revoke the old. Each key records `last_used_at`, which is how you spot a key still in use after you thought it was retired. ## What can go wrong? | Status | Code | Meaning | |---|---|---| | `401` | `unauthorized` | `Authorization` header missing or malformed | | `401` | `invalid_api_key` | Key not found, revoked, inactive or expired | | `403` | `api_disabled` | The public API is not enabled for this company | | `404` | `company_not_found` | The key's company no longer exists | | `400` | `acting_user_required` | `acting_user_email` was not supplied | | `404` | `acting_user_invalid` | The acting user is not a member of this company | ## How should I handle keys securely? ### Server-side only Never put an API key in browser JavaScript, a mobile app, or any client you do not control. It grants access to candidate personal data. ### Use environment variables Not source code. A key committed to a repository is a key that has leaked, even in a private repo. ### One key per integration Separate keys per system mean you can revoke one without breaking the others, and `last_used_at` tells you which is which. ### Revoke on offboarding When someone who held a key leaves, revoke it yourself from Company Settings → Public API. It stops working immediately. ## Where do keys sit in the wider API? Authentication is the first of four things every integration must handle. The others are [rate limits](https://www.remakecv.com/help/api-reference/rate-limits.md), [errors](https://www.remakecv.com/help/api-reference/errors.md), and choosing a [template](https://www.remakecv.com/help/api-reference/endpoints/list-templates.md) — see the [API introduction](https://www.remakecv.com/help/api-reference/introduction.md) for the whole picture. ## How do I rotate a key? Create a new key, deploy it, confirm traffic has moved by checking that the old key's `last_used_at` has stopped advancing, then revoke the old one. A company can hold several active keys, so there is no downtime. ## Frequently asked questions ### How do I get an API key? A company administrator creates one in Company Settings under Public API. Enable the API, create a named key, and copy the secret — it is shown only once. ### What happens if a key leaks? Revoke it yourself from Company Settings → Public API. Revocation is immediate. Then create a replacement — keys carry access to candidate personal data. ### Do I need an acting user on every request? No. Only POST /cvs/process and GET /templates use acting_user_email. The CV listing and file endpoints are scoped by company alone. --- # Rate limits > The RemakeCV API allows 30 requests per minute per company by default. Limits are returned in standard RateLimit headers and exceeding them returns 429. Source: https://www.remakecv.com/help/api-reference/rate-limits Last updated: 2026-08-21 --- The default rate limit is 30 requests per minute, counted per company rather than per API key. Limits are reported in standard `RateLimit` response headers, and exceeding one returns `429` with the code `rate_limit_exceeded`. The limit is configurable per company if your volume needs it raised. ## What is the limit? | Property | Value | |---|---| | Default limit | 30 requests per minute | | Window | 60 seconds | | Scope | Per company | | Configurable | Yes, per company | | Headers | `RateLimit-Limit`, `RateLimit-Remaining`, `RateLimit-Reset`, `RateLimit-Policy`; `Retry-After` on a 429 | > **Warning:** The limit is per company, not per key. If you run several integrations against the same RemakeCV account, they compete for the same 30 requests per minute. Adding keys does not add capacity. ### Reading the headers `RateLimit-Reset` and `Retry-After` are both **seconds until the window resets**, not a timestamp. There are no `X-RateLimit-*` headers — only the unprefixed standard ones. ## What happens when I exceed it? ```json { "error": { "code": "rate_limit_exceeded", "message": "Rate limit exceeded for this company.", "request_id": "b7c1e4a2-..." } } ``` Returned with HTTP `429`. Nothing is processed, and no credit is consumed. ## How should I handle it? Exponential backoff with jitter. The jitter matters: without it, several workers that hit the limit together will retry together and hit it again. ```javascript async function callWithRetry(request, attempts = 5) { for (let attempt = 0; attempt < attempts; attempt += 1) { const response = await request(); if (response.status !== 429) return response; // Prefer the server's own reset hint; fall back to exponential backoff. const reset = Number(response.headers.get('RateLimit-Reset')); const backoff = Number.isFinite(reset) && reset > 0 ? reset * 1000 : 2 ** attempt * 1000; await new Promise((r) => setTimeout(r, backoff + Math.random() * 500)); } throw new Error('Rate limit retries exhausted'); } ``` ## How do I process a large batch? At 30 requests per minute, a 500-CV migration takes roughly 17 minutes of steady requests. Two things make that reliable: ### Pace deliberately, do not burst Sending two requests per second and staying under the limit is faster overall than bursting, hitting `429`, and backing off. ### Make the job resumable Track which CVs succeeded. A batch that fails at item 400 should restart at 400, not at 1 — reprocessing costs credits. ### Ask for a higher limit first If you have a one-off migration, email support@remakecv.com and we will raise the limit for its duration — far easier than engineering around it. ## Related - [Errors and status codes](https://www.remakecv.com/help/api-reference/errors.md) — the full error contract - [`POST /cvs/process`](https://www.remakecv.com/help/api-reference/endpoints/process-a-cv.md) — the endpoint you will call most - [Process a CV and save the result](https://www.remakecv.com/help/api-reference/recipes/process-and-download.md) — a paced batch example ## Does a rate-limited request cost a credit? No. A `429` is rejected before any processing happens. ## Frequently asked questions ### Is the limit per key or per company? Per company. Issuing extra API keys does not increase your throughput — all keys for a company share the same budget. ### Can the limit be raised? Yes, per company. Email support@remakecv.com with your expected volume and we will raise it — your current limit is shown in Company Settings. ### How should I handle a 429? Back off and retry using exponential backoff with jitter. Read the RateLimit-Reset header to know when the window rolls over. --- # Errors and status codes > Every RemakeCV API error returns a code, a human-readable message and a request_id. Full reference of every error code the API can return. Source: https://www.remakecv.com/help/api-reference/errors Last updated: 2026-08-21 --- API errors return an object containing a machine-readable `code`, a human-readable `message` and a `request_id`. Branch your logic on `code` rather than `message`, since messages may be reworded. Always log the `request_id` — it is what support needs to trace a specific failed call. ## Error shape ```json { "error": { "code": "validation_error", "message": "File exceeds maximum size of 10MB", "request_id": "3f9a1c72-8b04-4e51-9d2a-77c0e5b1a934" } } ``` The same identifier is returned in the `X-Request-Id` response header on **every** response, successful or not. ## Every error code | Status | Code | Meaning | What to do | |---|---|---|---| | `400` | `validation_error` | Request was malformed, or the file exceeded the size limit | Fix the request; the message names the specific problem | | `400` | `upload_required` | No file was included on a request that needs one | Send the file in the `file` multipart field | | `400` | `acting_user_required` | `acting_user_email` was not supplied | Add it | | `400` | `storage_required` | The operation needs CV storage, which is disabled | Enable CV storage for your company | | `401` | `unauthorized` | `Authorization` header missing or malformed | Send `Authorization: Bearer ` | | `401` | `invalid_api_key` | Key not found, inactive, revoked or expired | Check the key; request a replacement if needed | | `403` | `api_disabled` | Public API not enabled for this company | Email support@remakecv.com | | `403` | `cv_storage_disabled` | CV storage is off, so stored CVs cannot be listed or fetched | Enable storage, or use the `download_url` returned at processing time | | `403` | `forbidden` | The key is not permitted to access this resource | Check the resource belongs to your company | | `404` | `not_found` | The requested CV does not exist | Check the `cvId` | | `404` | `company_not_found` | The key's company no longer exists | Contact support | | `404` | `acting_user_invalid` | The acting user is not a member of this company | Use a valid consultant's email | | `429` | `rate_limit_exceeded` | Too many requests | Back off and retry — see [rate limits](https://www.remakecv.com/help/api-reference/rate-limits.md) | | `500` | `internal_error` | Something failed on our side | Retry once; if it persists, send us the `request_id` | | `400` / `500` | `process_failed` | Processing failed — **also how credit rejections surface** | Read `message` | | `400` / `500` | `storage_failed` | Processed, but could not be stored | The `download_url` may still work | ## Which errors are worth retrying? | Code | Retry? | |---|---| | `rate_limit_exceeded` | Yes, with exponential backoff — costs nothing | | `internal_error` | Once, then escalate | | `process_failed` / `storage_failed` | **Cautiously** — these can occur after a credit was spent, so each retry may cost another | | Everything else | No — retrying will produce the same result | > **Warning:** Do not retry `4xx` errors in a loop. They indicate a problem with the request, so a retry fails identically while consuming your rate-limit budget. ## Do errors consume credits? Usually not. Validation failures, authentication failures and rate limits are rejected before any processing, so they cost nothing. **Two exceptions both spend a credit**, because they occur after the CV has already been processed: | Error | Why the credit is gone | |---|---| | `400 storage_required` | CV storage is disabled for your company. The pipeline runs, the credit is deducted, and *then* the storage check fails | | `400`/`500 storage_failed` | The CV parsed, but storing it failed | Neither response includes a `download_url` — there is no way to recover the file from them. > **Warning:** If CV storage is disabled for your company, **every** `POST /cvs/process` call spends a credit and returns an error. Confirm storage is enabled before you begin integrating. ## Credit rejections come back as `process_failed` There is no dedicated credit error code. RemakeCV returns `400 process_failed` with `message` set to either `No credits left` (company balance exhausted) or `credit limit reached` (a per-user or shared-pool cap). Branch on `message` for these two, since the remedies differ — see [credits explained](https://www.remakecv.com/help/account-and-billing/credits-explained.md). ## What should I log? At minimum: `request_id`, `code`, HTTP status, the endpoint, and the `acting_user_email`. That set is enough for support to reconstruct almost any failure without a further round trip. ## Frequently asked questions ### Should I branch on the code or the message? Always the code. Messages are written for humans and may be reworded; codes are the stable contract. ### What is request_id for? It uniquely identifies the call in our logs. Include it when contacting support and we can trace exactly what happened. It is also returned in the X-Request-Id response header. ### Do failed requests consume credits? Usually not — validation, auth and rate-limit rejections are free. But storage_required and storage_failed occur after processing, so those do spend a credit. --- # GET /health > Check that the RemakeCV API is reachable. The only endpoint requiring no authentication, which makes it the right first step when debugging an integration. Source: https://www.remakecv.com/help/api-reference/endpoints/health Last updated: 2026-08-21 --- `GET /health` returns `{"status":"ok"}` and requires no authentication, because it sits ahead of the RemakeCV API's auth layer. Use it to verify network connectivity and that the service is reachable, separately from any question about whether your API key is valid or your company has the API enabled. ## Request ```bash curl https://app.remakecv.com/api/public/v1/health ``` No headers required. ## Response ```json { "status": "ok" } ``` > **Note:** This endpoint returns a bare object rather than the standard `data`/`pagination`/`error` envelope, because it sits ahead of the authenticated API layer. ## Why it is useful Because it separates two failure modes that otherwise look identical from the client side: | `/health` | An authenticated call | Diagnosis | |---|---|---| | Succeeds | Fails `401` | Your key is wrong, expired or revoked | | Succeeds | Fails `403 api_disabled` | The API is not enabled for your company | | Fails | Fails | Network, DNS or the service is down | Start every integration debug here. ## Where to go next Once `/health` responds, move on to [authentication](https://www.remakecv.com/help/api-reference/authentication.md) and then [`GET /templates`](https://www.remakecv.com/help/api-reference/endpoints/list-templates.md), which is the simplest authenticated call to confirm a key works. ## Should I poll it? For an uptime check, a low-frequency poll is reasonable. Do not use it as a keepalive before every request — it adds a round trip without telling you anything about whether the *next* call will succeed. ## Frequently asked questions ### Does /health need an API key? No. It sits ahead of the authentication middleware, which is what makes it useful for isolating connectivity problems from credential problems. ### Does it count against my rate limit? No. Rate limiting is applied after authentication, and /health runs before it. --- # POST /cvs/process > Upload a CV for parsing. Returns the extracted candidate name, latest employer and role, plus a signed URL to the stored source file. Does not render a formatted document. Source: https://www.remakecv.com/help/api-reference/endpoints/process-a-cv Last updated: 2026-08-22 --- `POST /cvs/process` uploads a CV to RemakeCV as multipart form data, parses it, and returns the extracted candidate name, latest employer and latest role plus a signed URL to the stored file. It requires the file and `acting_user_email`, needs CV storage enabled, and consumes one credit per call. > **Danger:** **This endpoint parses and stores a CV; it does not return a rendered document.** The `download_url` it returns points at the **source file you uploaded**, converted to PDF. For branded, template-rendered output on a candidate record, use the web app or a native integration — our team builds those for any ATS. See [integrations overview](https://www.remakecv.com/help/integrations/integrations-overview.md). > **Warning:** **CV storage must be enabled for your company.** If it is not, every call still runs the full pipeline and **spends a credit**, then returns `400 storage_required`. Confirm storage is on before you start integrating. ## Request `POST /cvs/process` · `multipart/form-data` · **Authentication required** - `file` _binary_ (required) — The CV to process. Accepts `.pdf`, `.doc` and `.docx`. Maximum 10MB by default. - `acting_user_email` _string_ (required) — Email address of the consultant this request is on behalf of. Determines template visibility and which credit limits apply. - `template_id` _string | null_ — Influences the **extraction schema** for company-specific configurations. It does not render anything. Pass a value we have configured for your company, or omit it. When omitted, a separate public-API setting is used, falling back to the literal `default`. That setting is **not** the same as the `is_default` template returned by [`GET /templates`](https://www.remakecv.com/help/api-reference/endpoints/list-templates.md); contact support@remakecv.com to set it. - `gender` _string_ — Free text passed into the extraction prompt as context about the candidate. It biases how the model reads the CV. Omit it unless you have a specific reason. - `blurb` _string_ — A **style exemplar**, not content. It is shown to the model as an example summary to imitate when generating a candidate summary, and never appears verbatim in the output. It is only consulted when the CV has no existing summary. ```bash curl -X POST "https://app.remakecv.com/api/public/v1/cvs/process" \ -H "Authorization: Bearer $REMAKECV_API_KEY" \ -F "file=@candidate-cv.pdf" \ -F "acting_user_email=consultant@agency.com" \ -F "template_id=42" ``` ## Response ```json { "data": { "id": 1234, "stored": true, "storage_enabled": true, "candidate_name": "Alex Morgan", "latest_company": "Northwind Logistics", "latest_role": "Operations Manager", "processing_method": "text", "download_url": "https://storage.googleapis.com/..." }, "pagination": null, "error": null } ``` - `id` _integer | null_ — The stored CV's identifier, or `null` when CV storage is disabled for your company. - `stored` _boolean_ — Always `true` on a 200 response. A CV that could not be stored returns an error instead. - `storage_enabled` _boolean_ — Always `true` on a 200 response — storage is a prerequisite, so a company without it never reaches this response. - `candidate_name` _string | null_ — Extracted candidate name. `null` if it could not be determined. - `latest_company` _string | null_ — The candidate's most recent employer. - `latest_role` _string | null_ — The candidate's most recent job title. - `processing_method` _string_ — `text` when the document had an extractable text layer, `image` when OCR was required. - `download_url` _string_ — Signed URL for **the source CV you uploaded, as a PDF** (Word files are converted). Valid for **1 hour**. > **Warning:** `download_url` expires after **1 hour**. Do not store it in a database or send it to a client. Store `id` instead and fetch a fresh URL from [`GET /cvs/{cvId}/file`](https://www.remakecv.com/help/api-reference/endpoints/get-cv-file.md) when you need one. ## Scope of this endpoint `POST /cvs/process` is the parse-and-store endpoint. Worth knowing as you design around it: | Behaviour | Detail | |---|---| | Branded document output | Handled by the web app and the native integrations rather than this endpoint — ask us about your platform | | Processing mode | Automatic; RemakeCV selects the right extraction path per document | | Each call | Treated as a new CV, so use your stored `cvId` rather than re-posting the same file | | Filtering by consultant | Filter client-side from [`GET /cvs`](https://www.remakecv.com/help/api-reference/endpoints/list-cvs.md) | Need something here that the API does not currently expose? Email support@remakecv.com — the API is actively developed and customer requirements drive what lands next. ## Errors | Status | Code | Cause | |---|---|---| | `400` | `upload_required` | No file in the `file` field | | `400` | `acting_user_required` | `acting_user_email` missing | | `400` | `validation_error` | File too large, or malformed multipart body | | `401` | `invalid_api_key` | Key invalid, revoked or expired | | `400` | `storage_required` | CV storage is disabled — **a credit is still spent** | | `403` | `api_disabled` | Public API not enabled for this company | | `400`/`500` | `process_failed` | Processing failed. Credit rejections arrive here, with the reason in `message` | | `400`/`500` | `storage_failed` | Parsed, but storing failed — **credit already spent, and no `download_url` is returned** | | `404` | `acting_user_invalid` | Acting user is not a member of this company | | `429` | `rate_limit_exceeded` | Over 30 requests per minute | See [errors](https://www.remakecv.com/help/api-reference/errors.md). ## Notes - **One credit per call that reaches processing.** Validation, auth and rate-limit rejections cost nothing, but `storage_required` and `storage_failed` occur *after* the credit is deducted. - **`processing_method: "image"` means OCR ran.** Those results warrant closer review — see [scanned PDFs and OCR](https://www.remakecv.com/help/troubleshooting/scanned-pdfs-and-ocr.md). - **`template_id` is not validated.** An unknown ID is accepted and quietly ignored. ## Frequently asked questions ### What is the maximum file size? 10MB by default, configurable per company. Exceeding it returns 400 validation_error. ### Does download_url give me the formatted CV? It points at the source file you uploaded, converted to PDF. For branded, template-rendered output on a candidate record, use the web app or a native integration — our team builds those for any ATS. ### How long does download_url stay valid? One hour. For longer-lived access, store the returned CV id and fetch a fresh URL from GET /cvs/{cvId}/file when needed. ### Does a failed call consume a credit? Usually not — validation, auth and rate-limit rejections are free. But storage_required and storage_failed happen after the credit is deducted, so those do cost one. --- # GET /cvs > List CVs stored for your company, with pagination and creation-date filters. Requires CV storage to be enabled. Source: https://www.remakecv.com/help/api-reference/endpoints/list-cvs Last updated: 2026-08-22 --- `GET /cvs` returns a paginated list of the CVs RemakeCV has stored for your company, each with the candidate name, latest employer, latest role and processing method. Supports `page`, `page_size` and `created_from` / `created_to` date filters. Requires CV storage to be enabled. ## Request `GET /cvs` · **Authentication required** - `page` _integer_ — Page number, starting at 1. Defaults to the first page. - `page_size` _integer_ — Results per page. Maximum 1000. Values outside the range are clamped to the nearest valid value rather than rejected, so a request never fails on this alone. - `created_from` _string (date-time)_ — Only return CVs created at or after this timestamp. ISO 8601. - `created_to` _string (date-time)_ — Only return CVs created at or before this timestamp. ISO 8601. ```bash curl "https://app.remakecv.com/api/public/v1/cvs?page=1&page_size=100" \ -H "Authorization: Bearer $REMAKECV_API_KEY" ``` ## Response ```json { "data": [ { "id": 1234, "created_at": "2026-08-14T09:12:33.000Z", "updated_at": "2026-08-14T09:15:02.000Z", "candidate_name": "Alex Morgan", "latest_company": "Northwind Logistics", "latest_role": "Operations Manager", "processing_method": "text", "file_available": true } ], "pagination": { "page": 1, "page_size": 100, "total": 842, "total_pages": 9 }, "error": null } ``` - `file_available` _boolean_ — Always `true` on this endpoint — it does not currently reflect real file availability. Do not branch on it here. On [`GET /cvs/{cvId}`](https://www.remakecv.com/help/api-reference/endpoints/get-cv.md) it is genuine. > **Warning:** **This endpoint and `GET /cvs/{cvId}` differ in how they report missing data.** `GET /cvs` substitutes the strings `"Unknown"` for a missing candidate name and `"N/A"` for a missing employer or role. `GET /cvs/{cvId}` returns `null` for the same fields. Handle both, or you will treat `"Unknown"` as a real candidate. Results are ordered by `created_at` **descending**. ## Paging through everything ```javascript async function* allCvs(fetchPage) { let page = 1; let totalPages = 1; do { const { data, pagination } = await fetchPage(page, 1000); totalPages = pagination.total_pages; yield* data; page += 1; } while (page <= totalPages); } ``` > **Warning:** Each page is one request against your rate limit of 30 per minute. A 9-page export is fine; a nightly full sync of a large archive should use `created_from` to fetch only what changed. Because ordering is newest-first, a CV processed mid-export shifts every subsequent row by one and you can miss records. For a consistent snapshot, bound the export with `created_to`. ## Related - [`GET /cvs/{cvId}`](https://www.remakecv.com/help/api-reference/endpoints/get-cv.md) — one record in detail - [CV history](https://www.remakecv.com/help/formatting-cvs/cv-history.md) — the same data in the web app ## Errors | Status | Code | Cause | |---|---|---| | `401` | `invalid_api_key` | Key invalid, revoked or expired | | `403` | `api_disabled` | Public API not enabled | | `403` | `cv_storage_disabled` | CV storage is off for this company | | `429` | `rate_limit_exceeded` | Over the rate limit | ## Frequently asked questions ### What is the maximum page size? 1000. For a full export, page through rather than requesting everything at once. ### Why do I get 403 cv_storage_disabled? Your company has CV storage turned off, so there is nothing stored to list. Enable storage or capture download_url at processing time instead. ### Can I filter by candidate name? Not directly. Filter by date range and match on candidate_name client-side. ### Can I see which consultant processed each CV? Not through the public API. The listing is company-scoped and does not return or filter by user. --- # GET /cvs/{cvId} > Retrieve the detail of a single stored CV by its identifier, including candidate name, latest employer, role and processing method. Source: https://www.remakecv.com/help/api-reference/endpoints/get-cv Last updated: 2026-08-21 --- `GET /cvs/{cvId}` returns one RemakeCV stored CV record: candidate name, latest employer, latest role, processing method, timestamps and whether the file is still retrievable. It returns `404 not_found` if the CV does not exist or belongs to another company. ## Request `GET /cvs/{cvId}` · **Authentication required** - `cvId` _integer_ (required) — The stored CV's identifier, as returned by [`POST /cvs/process`](https://www.remakecv.com/help/api-reference/endpoints/process-a-cv.md) or [`GET /cvs`](https://www.remakecv.com/help/api-reference/endpoints/list-cvs.md). ```bash curl "https://app.remakecv.com/api/public/v1/cvs/1234" \ -H "Authorization: Bearer $REMAKECV_API_KEY" ``` ## Response ```json { "data": { "id": 1234, "created_at": "2026-08-14T09:12:33.000Z", "updated_at": "2026-08-14T09:15:02.000Z", "candidate_name": "Alex Morgan", "latest_company": "Northwind Logistics", "latest_role": "Operations Manager", "processing_method": "text", "file_available": true }, "pagination": null, "error": null } ``` > **Note:** Company scoping is enforced on every request. A `cvId` belonging to a different company returns `404 not_found` rather than `403`, so the endpoint does not reveal whether that identifier exists elsewhere. ## Errors | Status | Code | Cause | |---|---|---| | `401` | `invalid_api_key` | Key invalid, revoked or expired | | `403` | `api_disabled` | Public API not enabled | | `403` | `cv_storage_disabled` | CV storage is off for this company | | `404` | `not_found` | No such CV for this company | | `429` | `rate_limit_exceeded` | Over the rate limit | ## Frequently asked questions ### Does this return the CV content? It returns the record's summary fields, not the full parsed CV body. To get the document itself, use GET /cvs/{cvId}/file. ### Can I fetch a CV from another company? No. Every request is scoped to the company that owns the API key. A CV belonging to another company returns 404. --- # GET /cvs/{cvId}/file > Get a short-lived signed URL for a stored CV file. Fetch a fresh URL each time rather than storing the one you were given. Source: https://www.remakecv.com/help/api-reference/endpoints/get-cv-file Last updated: 2026-08-21 --- `GET /cvs/{cvId}/file` returns a signed URL for the stored CV, valid for **one hour**. The file is always served as a **PDF** — Word uploads are converted. It is the source CV you uploaded, not a document rendered into your template. Request a fresh URL each time rather than persisting one. ## Request `GET /cvs/{cvId}/file` · **Authentication required** - `cvId` _integer_ (required) — The stored CV's identifier. ```bash curl "https://app.remakecv.com/api/public/v1/cvs/1234/file" \ -H "Authorization: Bearer $REMAKECV_API_KEY" ``` ## Response ```json { "data": { "url": "https://storage.googleapis.com/...", "expires_in": 3600 }, "pagination": null, "error": null } ``` - `url` _string_ — Signed download URL for the stored CV, always a PDF. In practice this is never `null` on a 200 response — a genuinely missing file surfaces as `500 internal_error` instead. - `expires_in` _integer_ — Seconds until the URL stops working. Currently `3600`. > **Note:** The file is the **source CV**, converted to PDF where it was uploaded as Word. RemakeCV's public API does not render CVs into your template — see [`POST /cvs/process`](https://www.remakecv.com/help/api-reference/endpoints/process-a-cv.md). ## How should I use it? ### Store the id, not the URL Persist `cvId` in your own system. Signed URLs are ephemeral by design. ### Fetch on demand Call this endpoint at the moment a user asks for the file, then redirect or stream. ### Download server-side where you can Fetching the file on your server and serving it through your own authenticated route keeps the signed URL out of browsers, logs and referrer headers. > **Warning:** A signed URL grants access to a candidate's CV to anyone holding it, with no authentication. Do not put one in an email, a shared document, a client-side log or a support ticket. ## Related - [`GET /cvs`](https://www.remakecv.com/help/api-reference/endpoints/list-cvs.md) — find the `cvId` to pass here - [Sync formatted CVs back to your ATS](https://www.remakecv.com/help/api-reference/recipes/sync-to-your-ats.md) — where this endpoint is normally used ## Errors | Status | Code | Cause | |---|---|---| | `401` | `invalid_api_key` | Key invalid, revoked or expired | | `403` | `api_disabled` | Public API not enabled | | `403` | `cv_storage_disabled` | CV storage is off for this company | | `404` | `not_found` | No such CV for this company | | `429` | `rate_limit_exceeded` | Over the rate limit | ## Frequently asked questions ### How long is the URL valid? One hour, reported as expires_in: 3600. Fetch a fresh URL rather than storing one. ### What format is the file? Always PDF. Word uploads are converted. It is the source CV you uploaded, not a template-rendered document. ### Can I share the signed URL with a client? Technically it works until expiry, but it is a bad idea — it grants unauthenticated access to candidate personal data. Download the file and send it through your normal channel. --- # GET /templates > List the RemakeCV templates visible to a given consultant, with their IDs and which one is the company default. Visibility is per user, so the list differs between consultants. Source: https://www.remakecv.com/help/api-reference/endpoints/list-templates Last updated: 2026-08-21 --- `GET /templates` lists the RemakeCV templates a specific consultant can use, returning each template's `id`, `name` and whether it is the company default. It requires `acting_user_email` because template visibility can be scoped to particular users, so the list differs between consultants. ## Request `GET /templates` · **Authentication required** - `acting_user_email` _string_ (required) — Email of the consultant whose visible templates you want. Required — visibility is per user. ```bash curl "https://app.remakecv.com/api/public/v1/templates?acting_user_email=consultant@agency.com" \ -H "Authorization: Bearer $REMAKECV_API_KEY" ``` ## Response ```json { "data": [ { "id": "42", "name": "Agency Standard", "is_default": true }, { "id": "43", "name": "Acme Corp — client branded", "is_default": false }, { "id": "44", "name": "Agency Standard — anonymised", "is_default": false } ], "pagination": null, "error": null } ``` - `id` _string | integer_ — Pass this as `template_id` to [`POST /cvs/process`](https://www.remakecv.com/help/api-reference/endpoints/process-a-cv.md). - `is_default` _boolean_ — The default template **in the web app**. > **Warning:** `is_default` is the web app default, and the API keeps its own separate default so the two can differ deliberately. Pass `template_id` explicitly to remove all ambiguity, or email support@remakecv.com to set the API default for your company. > **Tip:** Fetch templates once at startup and cache them rather than calling this before every CV. Templates change rarely, and each call spends one of your 30 requests per minute. ## Why is the list different for different users? Because template visibility can be scoped. A client-branded variant is normally restricted to the team working that account, so a consultant outside it will not see it. In practice most companies see identical lists: filtering applies only to non-admin users who have an explicit visibility entry. Administrators always see everything. If a template you expect is missing, check the acting user's visibility rather than assuming the template is gone. See [template variants](https://www.remakecv.com/help/templates-and-branding/template-variants.md). ## Errors | Status | Code | Cause | |---|---|---| | `400` | `acting_user_required` | `acting_user_email` not supplied | | `401` | `invalid_api_key` | Key invalid, revoked or expired | | `403` | `api_disabled` | Public API not enabled | | `404` | `acting_user_invalid` | Acting user is not a member of this company | | `429` | `rate_limit_exceeded` | Over the rate limit | ## Frequently asked questions ### Why does acting_user_email change the results? Template visibility can be restricted to specific users — client-branded variants in particular. The list reflects what that consultant can actually select. ### What if I omit template_id when processing? A separate public-API default is used, which is not the is_default template shown here and is unset for most companies. Pass template_id explicitly to be sure. --- # Recipe: process a CV and store the result > A complete worked example — authenticate, upload a CV for parsing, read the extracted candidate details, and retrieve the stored source file, with retry and error handling. Source: https://www.remakecv.com/help/api-reference/recipes/process-and-download Last updated: 2026-08-21 --- This recipe walks through a full RemakeCV integration: fetch the template list, `POST` a CV to `/cvs/process`, read the extracted candidate name, employer and role, and retrieve the stored source file. It includes rate-limit backoff and the error handling a production integration needs. ## What you need - An API key — a company administrator creates one in Company Settings → Public API. See [authentication](https://www.remakecv.com/help/api-reference/authentication.md) - **CV storage enabled for your company.** Without it every call spends a credit and returns `400 storage_required` - The email address of the consultant the work is on behalf of - A CV file in `.pdf`, `.doc` or `.docx` > **Warning:** This endpoint **parses and stores** a CV. It does not render one into your template — `download_url` returns the file you uploaded, converted to PDF. Plan your integration around the extracted fields, not around a formatted document. ## The complete flow ```javascript title="process-cv.mjs" import fs from 'node:fs/promises'; const BASE = 'https://app.remakecv.com/api/public/v1'; const KEY = process.env.REMAKECV_API_KEY; const ACTING_USER = 'consultant@agency.com'; const auth = { Authorization: `Bearer ${KEY}` }; /** Retries only on 429 and 5xx; 4xx errors are the caller's problem to fix. */ async function request(path, init = {}, attempts = 4) { for (let attempt = 0; attempt < attempts; attempt += 1) { const response = await fetch(`${BASE}${path}`, { ...init, headers: { ...auth, ...init.headers }, }); if (response.ok) return response.json(); if (response.status !== 429 && response.status < 500) { const { error } = await response.json(); throw new Error(`${error.code}: ${error.message} (request_id ${error.request_id})`); } const wait = 2 ** attempt * 1000 + Math.random() * 500; await new Promise((r) => setTimeout(r, wait)); } throw new Error(`Gave up after ${attempts} attempts: ${path}`); } async function findTemplate(name) { const { data } = await request( `/templates?acting_user_email=${encodeURIComponent(ACTING_USER)}` ); return data.find((t) => t.name === name) ?? data.find((t) => t.is_default); } async function processCv(filePath, templateId) { const form = new FormData(); form.append('file', new Blob([await fs.readFile(filePath)]), filePath); form.append('acting_user_email', ACTING_USER); if (templateId) form.append('template_id', String(templateId)); const { data } = await request('/cvs/process', { method: 'POST', body: form }); return data; } const template = await findTemplate('Agency Standard'); const cv = await processCv('./candidate-cv.pdf', template?.id); console.log(`${cv.candidate_name} — ${cv.latest_role} at ${cv.latest_company}`); // OCR was needed, so this result is worth a closer human review. if (cv.processing_method === 'image') { console.warn('Scanned CV — verify extracted fields before sending.'); } // download_url points at the SOURCE CV as a PDF, and expires after an hour. const file = await fetch(cv.download_url); await fs.writeFile(`./source-${cv.id}.pdf`, Buffer.from(await file.arrayBuffer())); ``` ## What the response tells you | Field | Why you should act on it | |---|---| | `processing_method` | `image` means OCR ran — flag for human review | | `id` | Persist this. It is how you get a fresh download URL later | | `candidate_name` | `null` means extraction could not find a name — worth flagging | | `latest_company` / `latest_role` | The fields most worth writing into your own system | > **Warning:** `download_url` expires after **one hour**, so a job that processes now and downloads on a nightly schedule will fail. Store `id` and fetch a fresh URL from [`GET /cvs/{cvId}/file`](https://www.remakecv.com/help/api-reference/endpoints/get-cv-file.md) when you actually need the file. > **Tip:** The retry helper above retries on `5xx`. Be careful: `process_failed` and `storage_failed` can occur *after* a credit has been deducted, so a blind retry loop can spend several credits on one CV. Cap the attempts, as this example does. ## Processing a batch At 30 requests per minute, pace deliberately rather than firing everything at once: ```javascript async function processBatch(paths, templateId) { const results = []; for (const path of paths) { results.push({ path, cv: await processCv(path, templateId) }); // Roughly 30/min, leaving headroom for the template lookup and retries. await new Promise((r) => setTimeout(r, 2100)); } return results; } ``` Track which files succeeded so a failed run resumes rather than restarting — reprocessing costs credits. See [rate limits](https://www.remakecv.com/help/api-reference/rate-limits.md). ## Frequently asked questions ### Can I skip the template lookup? Yes, but pass template_id explicitly if it matters — the fallback when you omit it is a separate public-API setting, not the is_default template. ### Does this give me a CV formatted into our template? The public API parses and stores CVs, and download_url returns the source file as a PDF. For branded, template-rendered output, use the web app or a native integration. ### Should I download immediately? Only if you need the file now. download_url lasts an hour; store the CV id and fetch a fresh URL from /cvs/{cvId}/file when required. --- # Recipe: sync CV data back to your ATS > Build a two-way flow — pull a CV from your ATS, parse it with RemakeCV, and write the extracted candidate details back onto the record. Source: https://www.remakecv.com/help/api-reference/recipes/sync-to-your-ats Last updated: 2026-08-21 --- To sync RemakeCV with your ATS, pull the candidate's CV from your system and `POST` it to `/cvs/process`, then write the extracted candidate name, employer and role back onto the record. This recipe covers the parsing and write-back half; for branded document output on the candidate record, use a native integration or ask our team to build one for your platform. ## The shape of the integration ### Trigger A consultant clicks a button on the candidate record, or a webhook fires when a CV is attached. Prefer an explicit trigger over formatting everything automatically — it wastes credits on candidates nobody submits. ### Fetch the source CV Pull the raw file from your ATS. ### Resolve the acting user Map the ATS user to their RemakeCV email. This determines template visibility and credit attribution — see [authentication](https://www.remakecv.com/help/api-reference/authentication.md). ### Process `POST /cvs/process` with the file, `acting_user_email` and optionally `template_id`. ### Store the identifier Persist the returned `id` against your candidate record. ### Write the extracted fields back `candidate_name`, `latest_company` and `latest_role` are the useful output. Write them onto the candidate record, or use them to reconcile against what your ATS already holds. ## Worked example ```javascript title="sync.mjs" async function formatAndAttach(candidateId) { const candidate = await ats.getCandidate(candidateId); const source = await ats.downloadAttachment(candidate.cvAttachmentId); const form = new FormData(); form.append('file', new Blob([source.buffer]), source.filename); form.append('acting_user_email', resolveActingUser(candidate.ownerId)); form.append('template_id', String(templateFor(candidate.clientId))); const response = await fetch(`${BASE}/cvs/process`, { method: 'POST', headers: { Authorization: `Bearer ${KEY}` }, body: form, }); if (!response.ok) { const { error } = await response.json(); // request_id is what support needs to trace this exact call. throw new Error(`${error.code} (${error.request_id}): ${error.message}`); } const { data: cv } = await response.json(); // The parsed fields are the value here — not the file. await ats.updateCandidate(candidateId, { latestEmployer: cv.latest_company, latestRole: cv.latest_role, }); // Lets you re-fetch the stored source file later without spending another credit. await ats.setCustomField(candidateId, 'remakecv_id', cv.id); // OCR ran, so the extraction is worth a human check. if (cv.processing_method === 'image') { await ats.addNote(candidateId, 'CV was OCR-processed — verify extracted details.'); } return cv; } ``` ## Design decisions worth getting right | Decision | Recommendation | |---|---| | Trigger | Explicit consultant action, not automatic on every upload — credits | | Acting user | Real consultant, never a shared service account | | Template selection | Derive from the client on the record, so the right variant is used | | Idempotency | Check for an existing `remakecv_id` before posting — each call creates a new CV and spends a credit, so store the id and reuse it | | Failure handling | Surface the `request_id` to the consultant, do not swallow it | | Rate limiting | Queue with backoff — see [rate limits](https://www.remakecv.com/help/api-reference/rate-limits.md) | > **Danger:** **This recipe syncs parsed data, not the branded document.** `download_url` gives you back the source file you uploaded, converted to PDF. If your goal is a branded, template-rendered CV landing on the candidate record, that is what the native integrations do — and our team builds them for any platform. See [integrations overview](https://www.remakecv.com/help/integrations/integrations-overview.md), or use the web app. > **Warning:** Guard against double-processing. A consultant clicking twice, or a webhook firing on retry, will process the same CV twice and spend two credits. Check for an existing `remakecv_id` before you call the API. ## Re-downloading later Do not store `download_url` — it expires after an hour. Store `id`, and when a consultant asks for the file again: ```javascript const { data } = await request(`/cvs/${remakecvId}/file`); // data.url is a signed URL to the source CV as a PDF, valid for data.expires_in seconds (3600). ``` Note the file is the **source CV as a PDF**, not a formatted document, and the URL lasts an hour. See [`GET /cvs/{cvId}/file`](https://www.remakecv.com/help/api-reference/endpoints/get-cv-file.md). ## Frequently asked questions ### Should I store the file or the CV id? Store the id. It lets you fetch a fresh signed URL for the stored source file at any time without spending another credit, so store it rather than re-posting the same file. ### How do I map ATS users to acting_user_email? Match on email address. If your ATS emails differ from RemakeCV logins, keep an explicit mapping table rather than falling back to a service account.