[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # JazzHR API and MCP server > JazzHR has a REST API with an API key from Settings > Integrations, but no official MCP server (checked 20 Oct 2026). The API reads jobs, applicants, activities, tasks and hires and can add applicants, notes, files and jobs. It has no call to move a candidate to another workflow stage, change a job status, email a candidate or create a task. Applicant tracking system for small and mid-size companies: job postings sent to job boards, a candidate pipeline built from workflow stages, email templates, tasks and bulk actions. ## What is the JazzHR API? Cotlet's JazzHR API exposes 13 endpoints for your own JazzHR account: list jobs, get job, list workflow stages, list candidates, get candidate, list tasks, change candidate status, bulk change status, send candidate email, add candidate note, create task, create job and set job status. The list_jobs endpoint returns jobs of your account with status, department and location, filtered by status or title. Each endpoint takes simple JSON inputs like job_id, status or candidate_id and works both as an operation of the jazzhr_read or jazzhr_write MCP tool for agents and as a REST call for scripts. - **Category:** [HR & recruiting](https://cotlet.dev/integrations/category/hr-recruiting.md) - **Endpoints:** 13 (6 read, 7 write) - **Updated:** 2026-10-19 JazzHR has a REST API with an API key from Settings > Integrations, but no official MCP server (checked 20 Oct 2026). Cotlet is a hosted MCP server and REST API for JazzHR with 13 endpoints (6 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work. ## Does JazzHR have an official API? JazzHR has a REST API with an API key from Settings > Integrations, but no official MCP server (checked 20 Oct 2026). The API reads jobs, applicants, activities, tasks and hires and can add applicants, notes, files and jobs. It has no call to move a candidate to another workflow stage, change a job status, email a candidate or create a task. | Task | JazzHR official | Cotlet | |---|---|---| | List jobs and read job details | Yes | Yes | | List candidates and read their answers | Yes: Filter by job, status, rating and apply date | Yes | | Add a note to a candidate | Yes: Notes can be added but not read back or edited | Yes | | Create a job | Partly: Needs hiring lead, workflow and employment type; no call to change the status afterwards | Yes | | Move a candidate to another workflow stage | No: Only a new job link can set a stage; nothing updates an existing one | Yes | | Bulk change candidate status | No | Yes | | Email a candidate | No | Yes | | Create a task | No: Tasks can only be read | Yes | | Open, hold, fill or close a job | No | Yes | Sources: [JazzHR API reference](https://www.resumatorapi.com/v1/), [JazzHR Help: API Overview](https://success.jazzhr.com/hc/en-us/articles/222540508-API-Overview), [JazzHR Help: Job Status Overview](https://help.jazzhr.com/s/article/Job-Status-Overview), [JazzHR Help: Performing Bulk Actions](https://help.jazzhr.com/s/article/Performing-Bulk-Actions) ## For AI agents ```text JazzHR has a REST API with an API key from Settings > Integrations, but no official MCP server (checked 20 Oct 2026). The API reads jobs, applicants, activities, tasks and hires and can add applicants, notes, files and jobs. It has no call to move a candidate to another workflow stage, change a job status, email a candidate or create a task. Cotlet provides a hosted MCP server and REST API for JazzHR: 13 tools (6 read, 7 write). Access Sign up at https://cotlet.dev/app/signup?app=jazzhr, then request the app and create API keys in the Cotlet console. MCP server https://cotlet.dev/mcp/v1 MCP tools jazzhr_read, jazzhr_write, reads and writes apart; call one with {"operation": "", "arguments": {...}} REST base https://cotlet.dev/api/v1/jazzhr, each operation at its own route, e.g. PATCH /api/v1/jazzhr/jobs/{job_id}/candidates/{candidate_id}/status Auth Authorization: Bearer . Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in. Operations list_jobs, get_job, list_workflow_stages, list_candidates, get_candidate, list_tasks, change_candidate_status, bulk_change_status, send_candidate_email, add_candidate_note, create_task, create_job, set_job_status Confirm change_candidate_status, bulk_change_status, send_candidate_email, add_candidate_note, create_task, set_job_status (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations) Markdown https://cotlet.dev/integrations/jazzhr-api-mcp-server.md How access works: 1. The user signs up at https://cotlet.dev/app/signup?app=jazzhr, requests JazzHR in the Cotlet console and creates an API key there. 2. The user signs in to JazzHR once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables JazzHR for agents. An agent cannot do this step. 3. The API key goes into the MCP client or the REST call as a bearer token. Fits: people who want a hosted JazzHR server that someone else maintains, including non-developers. Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA. Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev. Sign-in: the user signs in to JazzHR in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get JazzHR only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273). API key: holds no JazzHR login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once. Terms: the user stays responsible for following JazzHR's terms; Cotlet is not affiliated with JazzHR. ``` ## What can an AI agent do in JazzHR? Cotlet is best for recruiters and hiring teams who need an agent to move candidates, send emails and create tasks in JazzHR without running or fixing a server. - **[Reject remaining candidates when a job is filled](https://cotlet.dev/integrations/jazzhr-api-mcp-server/reject-candidates-when-job-filled.md)** (runs: weekly): "For every job that is now Filled, take the candidates still in the pipeline, move them to Not Hired and email each one the decline template. Show me the list before you send." → `list_jobs`, `list_candidates`, `bulk_change_status`, `send_candidate_email` - **[Advance applicants by your screening rules](https://cotlet.dev/integrations/jazzhr-api-mcp-server/advance-applicants-by-screening-rules.md)** (runs: daily): "Go through new applicants for Senior Support Agent. Move anyone with 3+ years of support experience and a US work authorization answer to Phone Screen, and leave a note with the reason. Leave the rest for me." → `list_candidates`, `get_candidate`, `change_candidate_status`, `add_candidate_note` - **[Create follow-up tasks for new candidates](https://cotlet.dev/integrations/jazzhr-api-mcp-server/create-follow-up-tasks-for-candidates.md)** (runs: daily): "For every candidate who reached Interview this week with no task on their profile, create a task for the hiring lead due in two days: "Send interview feedback", and notify by email." → `list_candidates`, `list_tasks`, `create_task` - **Weekly hiring pipeline report** (runs: weekly): "Every Monday, list my Open jobs and how many candidates sit in each workflow stage. Flag any stage where the newest candidate is older than 7 days." → `list_jobs`, `list_workflow_stages`, `list_candidates` - **Draft a job from a description and open it**: "Create a job called Customer Success Manager in the Support department from job.md, save it as Drafting, and show me the posting. Open it only when I say so." → `create_job`, `get_job`, `set_job_status` ## Can JazzHR automations run on a schedule in n8n, Make or Zapier? Yes. Cotlet does not replace your automation platform: it gives it a JazzHR connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to reject remaining candidates when a job is filled, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off. | Where | How to connect | How to schedule | |---|---|---| | Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. | | n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/jazzhr/jobs. | Schedule Trigger node. | | Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. | | Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. | | Your own script | GET https://cotlet.dev/api/v1/jazzhr/jobs with your API key. | cron or GitHub Actions. | ## Tools **For AI agents:** Every endpoint and its schema is public. The 13 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to JazzHR. ### list_jobs Jobs of your account with status, department and location, filtered by status or title. Access: read. REST: `GET /api/v1/jazzhr/jobs`. MCP: `jazzhr_read → list_jobs`. | Parameter | Type | Required | Description | |---|---|---|---| | `status` | enum | no | Open, On Hold, Drafting, Filled, Cancelled or Closed. Default: all. | | `title` | string | no | Part of the job title. | | `department` | string | no | Department name as shown on the job. | | `cursor` | string | no | Next page cursor from the previous call. | Lists jobs of your JazzHR account, 100 to a page; pass next_cursor back as cursor for the next page. status is the job status JazzHR shows, and only Open jobs appear on the careers page and free job boards. Use job_id as the job parameter of the other tools. Example response: ```json { "jobs": [ { "job_id": "job_20261012_8f3a", "title": "Senior Support Agent", "status": "Open", "department": "Support", "location": "Austin, TX", "open_date": "2026-10-12" }, { "job_id": "job_20260922_41cb", "title": "Account Executive", "status": "Filled", "department": "Sales", "location": "Remote", "open_date": "2026-09-22" } ], "next_cursor": null } ``` ### get_job One job with its description, hiring lead, workflow and status. Access: read. REST: `GET /api/v1/jazzhr/jobs/{job_id}`. MCP: `jazzhr_read → get_job`. | Parameter | Type | Required | Description | |---|---|---|---| | `job_id` | string | yes | Job ID from list_jobs. | Returns the full job: title, description, employment type, department, location, status and the hiring lead. workflow is the name of the workflow the job uses, whose stages list_workflow_stages returns. Works for jobs in any status, including Drafting. Example response: ```json { "job_id": "job_20261012_8f3a", "title": "Senior Support Agent", "status": "Open", "employment_type": "Full-time", "department": "Support", "location": "Austin, TX", "hiring_lead": "Maria Costa", "workflow": "Standard hiring", "description": "You will own the hardest tickets for our B2B customers and coach two junior agents." } ``` ### list_workflow_stages The stages of the workflow a job uses, in order, with the closing statuses such as Not Hired. Access: read. REST: `GET /api/v1/jazzhr/jobs/{job_id}/workflow-stages`. MCP: `jazzhr_read → list_workflow_stages`. | Parameter | Type | Required | Description | |---|---|---|---| | `job_id` | string | yes | Job ID from list_jobs. | Returns the workflow stages of one job in the order JazzHR shows them, then the closing statuses a candidate can end in, such as Not Hired. Pass a stage name as status to change_candidate_status and bulk_change_status. Stage names differ between workflows, so read them per job. Example response: ```json { "job_id": "job_20261012_8f3a", "stages": [ "New", "Review", "Phone Screen", "Interview", "Offer" ], "closing": [ "Hired", "Not Hired" ] } ``` ### list_candidates Candidates of a job with stage, rating and apply date, filtered by stage, status or name. Access: read. REST: `GET /api/v1/jazzhr/candidates`. MCP: `jazzhr_read → list_candidates`. | Parameter | Type | Required | Description | |---|---|---|---| | `job_id` | string | no | Only candidates of this job. Default: all jobs. | | `stage` | string | no | Workflow stage name from list_workflow_stages. | | `name` | string | no | Part of the candidate name. | | `applied_since` | date | no | Only candidates who applied on or after this date. | | `rating` | integer | no | Only candidates with this rating. | | `cursor` | string | no | Next page cursor from the previous call. | Lists candidates 100 to a page, newest application first; pass next_cursor back as cursor for the next page. stage is the workflow stage as JazzHR shows it for that job, or a closing status. Each row is one candidate on one job, so a person who applied to two jobs appears twice. Use candidate_id for the other candidate tools. Example response: ```json { "candidates": [ { "candidate_id": "prospect_20261019_5e2c", "name": "Dana Whitfield", "email": "dana.whitfield@example.com", "job_id": "job_20261012_8f3a", "stage": "New", "rating": 0, "applied_at": "2026-10-19" }, { "candidate_id": "prospect_20261016_77ad", "name": "Luis Ortega", "email": "luis.ortega@example.com", "job_id": "job_20261012_8f3a", "stage": "Interview", "rating": 4, "applied_at": "2026-10-16" } ], "next_cursor": null } ``` ### get_candidate One candidate with contact details, questionnaire answers, source and notes on the job. Access: read. REST: `GET /api/v1/jazzhr/candidates/{candidate_id}`. MCP: `jazzhr_read → get_candidate`. | Parameter | Type | Required | Description | |---|---|---|---| | `candidate_id` | string | yes | Candidate ID from list_candidates. | | `job_id` | string | no | Job whose notes and stage to return, when the candidate applied to several. | Returns the profile fields JazzHR holds for one candidate: contact details, source, rating, questionnaire answers and the notes on the chosen job. Notes are job-specific in JazzHR, so a note from another job is not returned. Files and resumes are listed by name only. Example response: ```json { "candidate_id": "prospect_20261019_5e2c", "name": "Dana Whitfield", "email": "dana.whitfield@example.com", "job_id": "job_20261012_8f3a", "stage": "New", "source": "Careers page", "answers": [ { "question": "Years of customer support experience", "answer": "5" }, { "question": "Are you authorized to work in the US?", "answer": "Yes" } ], "notes": [], "files": [ "resume.pdf" ] } ``` ### list_tasks Open and done tasks with the candidate, assignee and due date. Access: read. REST: `GET /api/v1/jazzhr/tasks`. MCP: `jazzhr_read → list_tasks`. | Parameter | Type | Required | Description | |---|---|---|---| | `status` | enum | no | open or done. Default: all. | | `from_date` | date | no | Only tasks due on or after this date. | | `to_date` | date | no | Only tasks due on or before this date. | | `cursor` | string | no | Next page cursor from the previous call. | Lists tasks visible to your account, soonest due date first, 100 to a page. Each row names the candidate it is attached to and the person it is assigned to. Use it before create_task to avoid a duplicate. Example response: ```json { "tasks": [ { "task_id": "task_20261014_0b1", "title": "Send interview feedback", "candidate_id": "prospect_20261016_77ad", "assigned_to": "Maria Costa", "due_date": "2026-10-22", "status": "open" } ], "next_cursor": null } ``` ### change_candidate_status Move one candidate to a workflow stage of their job, or to a closing status such as Not Hired. Access: write, asks the user first. REST: `PATCH /api/v1/jazzhr/jobs/{job_id}/candidates/{candidate_id}/status`. MCP: `jazzhr_write → change_candidate_status`. | Parameter | Type | Required | Description | |---|---|---|---| | `candidate_id` | string | yes | Candidate ID from list_candidates. | | `job_id` | string | yes | Job ID from list_jobs. | | `status` | string | yes | Stage or closing status name from list_workflow_stages. | Moves one candidate on one job to the stage you name. The name must match a stage or closing status of that job's workflow; an unknown name fails and the error lists the valid ones. Workflow helpers on the new stage can email the candidate or add a task, as when you move someone by hand. The call returns the previous and new stage. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "candidate_id": "prospect_20261019_5e2c", "job_id": "job_20261012_8f3a", "previous_stage": "New", "stage": "Phone Screen" } ``` ### bulk_change_status Move a group of candidates of one job to a stage or closing status in one pass. Access: write, asks the user first. REST: `POST /api/v1/jazzhr/jobs/{job_id}/change-status/bulk`. MCP: `jazzhr_write → bulk_change_status`. | Parameter | Type | Required | Description | |---|---|---|---| | `job_id` | string | yes | Job ID from list_jobs. | | `status` | string | yes | Stage or closing status name from list_workflow_stages. | | `candidate_ids` | array | yes | Candidate IDs from list_candidates, all on this job. | Does what the Bulk Actions button does with Change Status on: the same new status for every candidate listed. A candidate who is not on the job is reported and left out. Workflow helpers on the target stage can email the group, so check the stage first. The call returns how many were moved and which were not. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "job_id": "job_20261012_8f3a", "status": "Not Hired", "moved": 3, "skipped": [] } ``` ### send_candidate_email Email one candidate from their profile, from a template or with your own text. Access: write, asks the user first. REST: `POST /api/v1/jazzhr/candidates/{candidate_id}/email`. MCP: `jazzhr_write → send_candidate_email`. | Parameter | Type | Required | Description | |---|---|---|---| | `candidate_id` | string | yes | Candidate ID from list_candidates. | | `job_id` | string | no | Job the email is about. Default: the candidate's most recent job. | | `template` | string | no | Name of an email template from Settings > Templates > Email. | | `subject` | string | no | Subject when you write the email yourself instead of using a template. | | `body` | string | no | Message text when you write the email yourself. | | `send_at` | datetime | no | Send later at this time. Default: now. | Sends from the Emails tab of the candidate's profile, so it is stored there with the rest of the thread. Give either a template or a subject and body. A candidate with no email on file fails and nothing is sent. With send_at the email is scheduled, as JazzHR allows. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "candidate_id": "prospect_20261016_77ad", "template": "Decline after interview", "sent_to": "luis.ortega@example.com", "status": "sent" } ``` ### add_candidate_note Add a note to a candidate on one job, visible to your hiring team. Access: write, asks the user first. REST: `POST /api/v1/jazzhr/jobs/{job_id}/candidates/{candidate_id}/note`. MCP: `jazzhr_write → add_candidate_note`. | Parameter | Type | Required | Description | |---|---|---|---| | `candidate_id` | string | yes | Candidate ID from list_candidates. | | `job_id` | string | yes | Job ID from list_jobs. | | `text` | string | yes | The note text. | Adds one note to the candidate on the job you name. Notes are job-specific in JazzHR and do not move with the candidate to another job. Your teammates see the note, and the candidate does not. The call returns the note ID. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "note_id": "note_20261020_a31", "candidate_id": "prospect_20261019_5e2c", "job_id": "job_20261012_8f3a", "text": "5 years in support, US authorized. Moved to Phone Screen." } ``` ### create_task Create a task on a candidate for a teammate, with a due date and optional email notice. Access: write, asks the user first. REST: `POST /api/v1/jazzhr/candidates/{candidate_id}/tasks`. MCP: `jazzhr_write → create_task`. | Parameter | Type | Required | Description | |---|---|---|---| | `candidate_id` | string | yes | Candidate ID from list_candidates. | | `title` | string | yes | Task title. | | `assign_to` | string | yes | Name of a JazzHR user on your account. | | `due_date` | date | no | Due date. Default: none. | | `notes` | string | no | Task notes. | | `notify_by_email` | boolean | no | Email the assignee, as the Notify by email option does. Default: false. | Creates the task the way the profile's All Tasks section does. assign_to must match one user, and no match fails with the list of names. With notify_by_email the assignee gets an email with a Go to Candidate button. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "task_id": "task_20261020_c17", "candidate_id": "prospect_20261016_77ad", "title": "Send interview feedback", "assigned_to": "Maria Costa", "due_date": "2026-10-22", "notified": true } ``` ### create_job Create a job as Drafting or Open from a title, description and basic fields. Access: write. REST: `POST /api/v1/jazzhr/jobs`. MCP: `jazzhr_write → create_job`. | Parameter | Type | Required | Description | |---|---|---|---| | `title` | string | yes | Job title. | | `description` | string | yes | Job description text. | | `employment_type` | string | no | Employment type as the job form lists it. | | `department` | string | no | Department name. | | `city` | string | no | City of the job. | | `state` | string | no | State or region of the job. | | `status` | enum | no | Drafting or Open. Default: Drafting. | Fills the Create Job form and saves it. With Drafting, the default, the job is saved like Save As Draft and shows nowhere public, reaches no one and is edited or closed in one call, so it does not wait for your OK. With Open the job goes onto your careers page and the free job boards JazzHR syndicates to, so use set_job_status for that step. The call returns job_id. Example response: ```json { "job_id": "job_20261020_d90e", "title": "Customer Success Manager", "status": "Drafting", "department": "Support" } ``` ### set_job_status Change a job to Open, On Hold, Drafting, Filled, Cancelled or Closed. Access: write, asks the user first. REST: `PUT /api/v1/jazzhr/jobs/{job_id}/status`. MCP: `jazzhr_write → set_job_status`. | Parameter | Type | Required | Description | |---|---|---|---| | `job_id` | string | yes | Job ID from list_jobs. | | `status` | enum | yes | Open, On Hold, Drafting, Filled, Cancelled or Closed. | Does what the Job Status drop-down on the job does. Open makes the job visible on your careers page and lets JazzHR send it to the free job boards you selected; any other status takes it off partner job boards and stops new applications. Cancelled applies to jobs that went through job approval. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "job_id": "job_20261020_d90e", "previous_status": "Drafting", "status": "Open" } ``` ## How do I connect JazzHR to Claude Code, Codex or Cursor? Connecting JazzHR takes three steps: sign up, sign in to JazzHR once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key. ### Connect JazzHR to your agent. 1. **Create an account** Sign up and add JazzHR in the console. Your API key is there too. 2. **Sign in to JazzHR in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to JazzHR there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off. 3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once. Claude Code: ``` claude mcp add --transport http cotlet \ https://cotlet.dev/mcp/v1 \ --header "Authorization: Bearer $COTLET_API_KEY" ``` Cursor: ``` { "mcpServers": { "cotlet": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet] url = "https://cotlet.dev/mcp/v1" bearer_token_env_var = "COTLET_API_KEY" ``` 4. **Ask your agent** Ask in plain words. Your agent finds the JazzHR tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool. ``` For every job that is now Filled, take the candidates still in the pipeline, move them to Not Hired and email each one the decline template. Show me the list before you send. ``` ### Call JazzHR from your scripts. 1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code. ``` export COTLET_API_KEY="cotlet_..." ``` 2. **Call a tool** Every tool is an endpoint under /api/v1/jazzhr with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise. ``` curl -X PATCH https://cotlet.dev/api/v1/jazzhr/jobs/job_20261012_8f3a/candidates/prospect_20261019_5e2c/status \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"status":"Phone Screen"}' ``` 3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing. ``` { "candidate_id": "prospect_20261019_5e2c", "job_id": "job_20261012_8f3a", "previous_stage": "New", "stage": "Phone Screen" } ``` ## Why use Cotlet for JazzHR? **Built for agents** - One MCP server for every app you connect. - The same tools as a REST API for scripts and cron jobs. - Works with Claude Code, Codex and Cursor. **Your login stays yours** - You sign in to JazzHR yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses. - A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory. - The model never sees a login. - No stored passwords, no CAPTCHA solving, no MFA bypass. **You stay in control** - Scope each API key: its apps, its tools, read only or read and write. - Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you. - Every background request listed in your Background activity. Disable for agents in one click. **Kept working for you** - We test every integration every 6 hours. - When JazzHR changes, the tool pauses until we fix it. - Failed calls cost nothing. ## Is it safe to connect JazzHR to Cotlet? Yes. You sign in to JazzHR yourself, in your own Cloud Browser, and we never save your password. Your agents only get JazzHR once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself. - **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev) - **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on) - **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev) - **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev) [How Cotlet protects your access](https://cotlet.dev/security.md) ### Common concerns **Who runs Cotlet?** Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet. **Is this an official JazzHR integration?** No, Cotlet is independent of JazzHR. JazzHR's own API is too limited for this work. Cotlet works through your own JazzHR account, the way you use JazzHR in the browser, so you need no partner approval and no developer setup. **What about client data and GDPR?** Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it. **Can I start with read only?** Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool. **Is it reliable?** Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev. **How do I stop?** Press Disable for agents next to JazzHR in your console: your agents lose access at once and you stay signed in. Signing out of JazzHR in the browser works too, and Reset browser deletes the whole profile. ## Is there a JazzHR MCP server on GitHub? Zapier lists no JazzHR app (checked 20 Oct 2026), so a no-code flow means calling the JazzHR REST API yourself from a webhook step with your API key. Hosted API wrappers exist and use the same key. Both stay inside what the API allows: they read and add records, and cannot move a candidate or send an email. Cotlet works in your signed-in JazzHR, so those steps are available too. | | Zapier with the API | Cotlet | |---|---|---| | Setup | Generate an API key, build every call as a custom request, handle paging by hand | Sign up, sign in to JazzHR once, add one MCP server or API key | | When JazzHR changes | Your requests keep working until the API changes; you fix them | Our team tests it daily and fixes it for you; failed calls are free | | Your JazzHR access | An API key in each tool that holds it; generating a new key deactivates the old ones | Your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click | | Moving candidates and email | Not possible: the API has no call for it | Change stage, bulk change status and send email, as you do in the app | | Upkeep | You maintain the flows and the key | Nothing to host or update | | Where it runs | Inside Zapier or your own script | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule | | Price | Your Zapier plan, paid for with your time too | Free 7-day trial, then pay-as-you-go credit packs, no subscription | ### Which one fits you **Pick Cotlet if** - you are not a developer, or you do not want to maintain a server - you need it to keep working when JazzHR changes, without checking it yourself - your agent or a script should run it on a schedule, also while your computer is off **Pick an open-source server if** - you are comfortable installing, updating and fixing it yourself - you want your sign-in to stay on your own computer - you only need it now and then, from one MCP client ## How much does the JazzHR API cost? Free 7-day trial with 2,000 credits, no card needed. After that, the JazzHR API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over. | Credits | Price, one time | Calls at 25 credits | Per 1,000 credits | |---|---|---|---| | 5,000 | $29 | 200 | $5.80 | | 15,000 | $79 | 600 | $5.27 | | 32,000 | $149 | 1,280 | $4.66 | | 60,000 | $249 | 2,400 | $4.15 | Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md) ## How Cotlet holds your access Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own JazzHR account. - **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms) - **Your sign-in:** You sign in to JazzHR yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get JazzHR only after you enable it. When JazzHR signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md) - **Revoking access:** Press Disable for agents next to JazzHR, sign out of JazzHR in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool. - **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA. - **JazzHR's terms:** You use your own JazzHR account and stay responsible for following JazzHR's terms. Cotlet is independent and not affiliated with JazzHR. [Terms](https://cotlet.dev/terms) - **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev) ## Frequently asked questions **How do I get access?** Sign up free, open JazzHR in the console and press Request access. Then you create your API key and connect JazzHR there. **Do I need to be technical?** No. You sign in to JazzHR once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix. **Is it safe to connect JazzHR to Cotlet?** Yes. You sign in to JazzHR yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get JazzHR once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security. **Is a hosted server safer than a local one? My JazzHR sign-in would leave my computer.** On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your JazzHR cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off. **Why does Cotlet send requests instead of clicking in my browser?** To be fast, Cotlet doesn't click through JazzHR's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. JazzHR sees the same browser and IP you signed in with, and every request is listed in your Background activity. **What if someone gets my Cotlet API key?** The key holds no JazzHR login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once. **Why a signed-in browser and not OAuth, like other integration platforms?** JazzHR offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273). **Which JazzHR plan and role do I need for the API key?** JazzHR's API Overview says the API is included with all subscription levels, and the key sits under Settings > Integrations. It names Super Administrators, Recruiting Administrators and Developers as the roles that see it, so check your plan and role in your own account. Cotlet needs neither a key nor a plan feature: it works in your signed-in JazzHR with your role. **Does generating a new JazzHR API key affect Cotlet?** No. Cotlet uses your signed-in session, not the API key. JazzHR's own help warns that generating a new key deactivates the existing ones, which breaks any other tool that holds the old key. **Can my agent post or send messages in JazzHR without asking me?** No. Every call to change_candidate_status, bulk_change_status, send_candidate_email, add_candidate_note, create_task or set_job_status waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_job runs without asking, because it sends nothing to anyone and one call undoes it. **Can I use the JazzHR API in n8n?** Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/jazzhr from the HTTP Request node. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners. ## For AI agents: sign your user up Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed. 1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests 2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them. 3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests. One call creates the account and sends the access request; we email the user when access is granted.