[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) # JobDiva API and MCP server > JobDiva has a REST API with public Swagger docs, 759 paths across two versions, but it only works with a client ID that JobDiva provides, and JobDiva has no official MCP server (checked 23 Oct 2026). The API has no webhooks, so changes have to be polled, and updates and deletes are POST calls. Recruiting and staffing platform with an applicant tracking system, CRM, onboarding and reports in one place, used by staffing agencies and corporate recruiters. ## What is the JobDiva API? Cotlet's JobDiva API exposes 14 endpoints for your own JobDiva account: search candidates, find candidate, get candidate, list candidate notes, search jobs, get job, list submittals, list hotlists, create candidate, add candidate note, create hotlist, add candidates to hotlist, remove candidates from hotlist and create submittal. The search_candidates endpoint returns candidates from a Talent Search by skills, titles and distance from a location. Each endpoint takes simple JSON inputs like candidate_id, job_id or limit and works both as an operation of the jobdiva_read or jobdiva_write MCP tool for agents and as a REST call for scripts. - **Category:** [HR & recruiting](https://cotlet.dev/integrations/category/hr-recruiting.md) - **Endpoints:** 14 (8 read, 6 write) - **Updated:** 2026-10-24 JobDiva has a REST API with public Swagger docs, 759 paths across two versions, but it only works with a client ID that JobDiva provides, and JobDiva has no official MCP server (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for JobDiva with 14 endpoints (8 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work. ## Does JobDiva have an official API? JobDiva has a REST API with public Swagger docs, 759 paths across two versions, but it only works with a client ID that JobDiva provides, and JobDiva has no official MCP server (checked 23 Oct 2026). The API has no webhooks, so changes have to be polled, and updates and deletes are POST calls. | Task | JobDiva official | Cotlet | |---|---|---| | Search candidates by skills, titles and distance | Yes: Talent Search endpoint, needs a client ID from JobDiva | Yes | | Find a candidate by name, email or phone | Yes: Quick Candidate Profile Search, needs a client ID | Yes | | Read a candidate and the notes on the record | Yes: Needs a client ID | Yes | | Search and read jobs | Yes: Needs a client ID | Yes | | Add a note to a candidate | Yes: Needs a client ID | Yes | | Create hotlists and add or remove candidates | Yes: Needs a client ID | Yes | | Create a submittal for a candidate on a job | Yes: Needs a client ID | Yes | | Work from your own JobDiva login, with no client ID or API user | No | Yes | Sources: [JobDiva API (Swagger UI, Version 1 and Version 2)](https://api.jobdiva.com/jobdiva-api.html), [JobDiva: Integrate with JobDiva](https://www.jobdiva.com/integrate), [JobDiva + AI](https://www.jobdiva.com/jobdiva-ai), [JobDiva: FAQ](https://www.jobdiva.com/faq) ## Quick reference ```text JobDiva has a REST API with public Swagger docs, 759 paths across two versions, but it only works with a client ID that JobDiva provides, and JobDiva has no official MCP server (checked 23 Oct 2026). The API has no webhooks, so changes have to be polled, and updates and deletes are POST calls. Cotlet provides a hosted MCP server and REST API for JobDiva: 14 tools (8 read, 6 write). Access Sign up at https://cotlet.dev/app/signup?app=jobdiva, then request the app and create API keys in the Cotlet console. MCP server https://cotlet.dev/mcp/v1 MCP tools jobdiva_read, jobdiva_write, reads and writes apart; call one with {"operation": "", "arguments": {...}} REST base https://cotlet.dev/api/v1/jobdiva, each operation at its own route, e.g. POST /api/v1/jobdiva/candidates 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 search_candidates, find_candidate, get_candidate, list_candidate_notes, search_jobs, get_job, list_submittals, list_hotlists, create_candidate, add_candidate_note, create_hotlist, add_candidates_to_hotlist, remove_candidates_from_hotlist, create_submittal Confirm create_submittal (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/jobdiva-api-mcp-server.md How access works: 1. The user signs up at https://cotlet.dev/app/signup?app=jobdiva, requests JobDiva in the Cotlet console and creates an API key there. 2. The user signs in to JobDiva once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables JobDiva 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 JobDiva 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 JobDiva 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 JobDiva 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 JobDiva 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 JobDiva's terms; Cotlet is not affiliated with JobDiva. ``` ## What can an AI agent do in JobDiva? Cotlet is best for JobDiva recruiters and agency owners who want an AI agent to search talent, log notes, fill hotlists and submit candidates without running or fixing a server. - **[Build a hotlist of matching candidates for a job](https://cotlet.dev/integrations/jobdiva-api-mcp-server/build-candidate-hotlist.md)**: "For job 24071835, run a Talent Search for SQL and dbt within 25 miles of Chicago, read the best matches, and put the ones that fit into a new hotlist linked to the job." → `get_job`, `search_candidates`, `get_candidate`, `list_hotlists`, `create_hotlist`, `add_candidates_to_hotlist` - **[Log call notes on candidate records](https://cotlet.dev/integrations/jobdiva-api-mcp-server/log-call-notes.md)** (runs: daily): "Here are my call notes from today. For each candidate, find the record in JobDiva and add a note with the summary. Skip anyone who already has a note from today." → `find_candidate`, `list_candidate_notes`, `add_candidate_note` - **[Submit shortlisted candidates to a job](https://cotlet.dev/integrations/jobdiva-api-mcp-server/submit-candidates-to-a-job.md)**: "For job 24071835, read Priya Raman and Marcus Lee, skip anyone already submitted, and after my OK create submittals with a quoted bill rate of 105 USD an hour and a pay rate of 90." → `get_job`, `list_submittals`, `get_candidate`, `create_submittal` - **Weekly submittals per open job** (runs: weekly): "Every Monday, list my open jobs and how many candidates are submitted to each, with the status of each submittal." → `search_jobs`, `list_submittals` - **Add new candidates without duplicates**: "Add these five people to JobDiva with name, email, phone and skills. Search for each one first and skip anyone who already has a record." → `find_candidate`, `create_candidate` ## Can JobDiva automations run on a schedule in n8n, Make or Zapier? Yes. Cotlet does not replace your automation platform: it gives it a JobDiva 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 log call notes on candidate records, 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/jobdiva/candidates/find. | 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/jobdiva/candidates/find with your API key. | cron or GitHub Actions. | ## Tools **For AI agents:** Every endpoint and its schema is public. The 14 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 JobDiva. ### search_candidates Candidates from a Talent Search by skills, titles and distance from a location. Access: read. REST: `GET /api/v1/jobdiva/candidates/search`. MCP: `jobdiva_read → search_candidates`. | Parameter | Type | Required | Description | |---|---|---|---| | `skills` | string[] | no | Skills the resume must show, for example SQL and dbt. | | `titles` | string[] | no | Job titles to look for. | | `location` | string | no | City or address to measure distance from. | | `within_miles` | integer | no | Distance from the location in miles. | | `limit` | integer | no | Candidates per page. | | `page` | integer | no | Page number, starting at 1. | Runs the search the way Talent Search does: skills and titles combined with a location and a distance in miles. Returns one page of candidates with location and a short summary, best matches first. Pass page for the next one. Use candidate_id in get_candidate and add_candidates_to_hotlist. Candidates you cannot open in JobDiva are not returned. Example response: ```json { "total": 31, "candidates": [ { "candidate_id": 5821904, "name": "Priya Raman", "title": "Data Analyst", "location": "Chicago, IL", "skills": [ "SQL", "dbt", "Looker" ] }, { "candidate_id": 5830117, "name": "Marcus Lee", "title": "BI Lead", "location": "Naperville, IL", "skills": [ "SQL", "Power BI" ] }, { "candidate_id": 5834402, "name": "Elena Petrova", "title": "Analytics Engineer", "location": "Evanston, IL", "skills": [ "SQL", "dbt", "Snowflake" ] } ], "page": 1 } ``` ### find_candidate Quick search for a candidate by name, email, phone or address. Access: read. REST: `GET /api/v1/jobdiva/candidates/find`. MCP: `jobdiva_read → find_candidate`. | Parameter | Type | Required | Description | |---|---|---|---| | `value` | string | yes | Name, email, phone or address to look for. | | `limit` | integer | no | Maximum number of records returned. | Matches first name, last name, email, alternate email, work, home and cell phone, fax and address. Returns every record that matches, so a common name gives several rows; compare location and title before you use one. Use it to check whether a person already exists before create_candidate. Example response: ```json { "candidates": [ { "candidate_id": 5821904, "name": "Priya Raman", "title": "Data Analyst", "location": "Chicago, IL", "email": "priya.raman@example.com" } ] } ``` ### get_candidate One candidate record with contact fields, location, skills and work history. Access: read. REST: `GET /api/v1/jobdiva/candidates/{candidate_id}`. MCP: `jobdiva_read → get_candidate`. | Parameter | Type | Required | Description | |---|---|---|---| | `candidate_id` | integer | yes | Candidate ID from search_candidates or find_candidate. | Returns the name, contact fields, location, skills and work history shown on the record. Notes are not included; list_candidate_notes reads them. A record you cannot open in JobDiva answers APP_PERMISSION_DENIED. Example response: ```json { "candidate_id": 5821904, "name": "Priya Raman", "email": "priya.raman@example.com", "phone": "+1 312 555 0147", "location": "Chicago, IL", "skills": [ "SQL", "dbt", "Looker" ], "experience": [ { "title": "Data Analyst", "company": "Brightpath Retail", "from": "2020-03", "to": null } ] } ``` ### list_candidate_notes The notes on a candidate record, newest first. Access: read. REST: `GET /api/v1/jobdiva/candidate-notes`. MCP: `jobdiva_read → list_candidate_notes`. | Parameter | Type | Required | Description | |---|---|---|---| | `candidate_id` | integer | yes | Candidate ID from search_candidates or find_candidate. | Returns each note with its text, action type, action date and author, and the job it is linked to when it has one. Pinned notes are marked. Read it before add_candidate_note to avoid a double note. Example response: ```json { "notes": [ { "note_id": 90214477, "action": "Phone Call", "date": "2026-10-19", "author": "Jonas Weber", "note": "Left a voicemail about the Northwind role.", "pinned": false, "job_id": 24071835 } ] } ``` ### search_jobs Jobs by title, company, city and state, open jobs only if you ask. Access: read. REST: `GET /api/v1/jobdiva/jobs/search`. MCP: `jobdiva_read → search_jobs`. | Parameter | Type | Required | Description | |---|---|---|---| | `title` | string | no | Words from the job title. | | `company_name` | string | no | Company the job is for. | | `city` | string | no | City of the job. | | `state` | string | no | State of the job. | | `open_only` | boolean | no | true returns open jobs only. | | `limit` | integer | no | Maximum number of jobs returned. | Returns one row per job with its id, JobDiva reference, title, company, location and status. Use job_id in get_job, list_submittals and create_submittal. Jobs you cannot open in JobDiva are not returned. Example response: ```json { "jobs": [ { "job_id": 24071835, "reference": "26-04817", "title": "Senior Data Analyst", "company": "Northwind Logistics", "location": "Chicago, IL", "status": "Open" }, { "job_id": 24072210, "reference": "26-04902", "title": "Data Engineer", "company": "Harbor Freight Tech", "location": "Austin, TX", "status": "Open" } ] } ``` ### get_job One job with its description, company, location and dates. Access: read. REST: `GET /api/v1/jobdiva/job`. MCP: `jobdiva_read → get_job`. | Parameter | Type | Required | Description | |---|---|---|---| | `job_id` | integer | no | Job ID from search_jobs. | | `reference` | string | no | JobDiva reference number, used when you have no job_id. | Look a job up by job_id or by the JobDiva reference. Returns the title, company, location, description, issue date and status. The submittals on the job are not included; list_submittals reads them. Example response: ```json { "job_id": 24071835, "reference": "26-04817", "title": "Senior Data Analyst", "company": "Northwind Logistics", "location": "Chicago, IL", "status": "Open", "issued": "2026-10-12", "description": "Own reporting for the warehouse network. SQL and dbt required, 5+ years." } ``` ### list_submittals Submittals filtered by job, candidate or company. Access: read. REST: `GET /api/v1/jobdiva/submittals`. MCP: `jobdiva_read → list_submittals`. | Parameter | Type | Required | Description | |---|---|---|---| | `job_id` | integer | no | Only submittals on this job. | | `candidate_id` | integer | no | Only submittals of this candidate. | | `company_name` | string | no | Only submittals on jobs of this company. | Returns one row per submittal with the candidate, the job, the status and the submittal date. Filter by job_id to see who is already on a job, or by candidate_id to see where a person was sent. Pass at least one filter. Example response: ```json { "submittals": [ { "submittal_id": 7719150, "candidate_id": 5821904, "candidate": "Priya Raman", "job_id": 24071835, "status": "Submitted", "submittal_date": "2026-10-14" }, { "submittal_id": 7719161, "candidate_id": 5812266, "candidate": "Tomas Novak", "job_id": 24071835, "status": "Submitted", "submittal_date": "2026-10-15" } ] } ``` ### list_hotlists The candidate hotlists you can see. Access: read. REST: `GET /api/v1/jobdiva/hotlists`. MCP: `jobdiva_read → list_hotlists`. No parameters. Returns each hotlist with its id, name, description and the job it is linked to. Check it before create_hotlist, so the agent reuses a hotlist that exists. Example response: ```json { "hotlists": [ { "hotlist_id": 88102, "name": "Austin pipeline", "description": "Data engineers near Austin", "job_id": null }, { "hotlist_id": 88314, "name": "Senior Data Analyst - Northwind", "description": "Matches for job 26-04817", "job_id": 24071835 } ] } ``` ### create_candidate A new candidate record with name, contact fields and skills. Access: write. REST: `POST /api/v1/jobdiva/candidates`. MCP: `jobdiva_write → create_candidate`. | Parameter | Type | Required | Description | |---|---|---|---| | `first_name` | string | yes | First name. | | `last_name` | string | yes | Last name. | | `email` | string | no | Email address. | | `cell_phone` | string | no | Cell phone number. | | `city` | string | no | City. | | `state` | string | no | State. | | `skills` | string[] | no | Skills to put on the record. | Only first_name and last_name are required. Returns the new candidate_id. It does not check for duplicates, so run find_candidate first. It sends nothing and reaches no one, so it does not wait for your OK. Example response: ```json { "candidate_id": 5841230, "name": "Dana Whitfield", "status": "created" } ``` ### add_candidate_note A note on a candidate record, with an action type and an optional job link. Access: write. REST: `POST /api/v1/jobdiva/candidates/{candidate_id}/note`. MCP: `jobdiva_write → add_candidate_note`. | Parameter | Type | Required | Description | |---|---|---|---| | `candidate_id` | integer | yes | Candidate ID from search_candidates or find_candidate. | | `note` | string | yes | Text of the note. | | `action` | string | no | Action type name as set up in your JobDiva account, for example Phone Call. | | `job_id` | integer | no | Open job the note is about. | Saves the note on the record and returns its note_id. The action is the type name as set up in your JobDiva account; copy one from list_candidate_notes. job_id links the note to an open job. It sends nothing and reaches no one, so it does not wait for your OK. Example response: ```json { "note_id": 90214531, "candidate_id": 5821904, "action": "Phone Call", "job_id": 24071835, "status": "saved" } ``` ### create_hotlist A new candidate hotlist, optionally linked to a job. Access: write. REST: `POST /api/v1/jobdiva/hotlists`. MCP: `jobdiva_write → create_hotlist`. | Parameter | Type | Required | Description | |---|---|---|---| | `name` | string | yes | Hotlist name. | | `description` | string | yes | What the hotlist is for. | | `job_id` | integer | no | Job to link the hotlist to. | Returns the hotlist_id for add_candidates_to_hotlist. Linking a job puts the hotlist on that job. It shares the hotlist with nobody, so it does not wait for your OK. Example response: ```json { "hotlist_id": 88314, "name": "Senior Data Analyst - Northwind", "job_id": 24071835, "status": "created" } ``` ### add_candidates_to_hotlist Put candidates into a hotlist. Access: write. REST: `POST /api/v1/jobdiva/hotlists/{hotlist_id}/candidates-to-hotlists`. MCP: `jobdiva_write → add_candidates_to_hotlist`. | Parameter | Type | Required | Description | |---|---|---|---| | `hotlist_id` | integer | yes | Hotlist ID from list_hotlists or create_hotlist. | | `candidate_ids` | integer[] | yes | Candidate IDs to add. | Adds the candidates in one call and returns how many are in the hotlist now. Reaches no one and is undone with remove_candidates_from_hotlist, so it does not wait for your OK. Example response: ```json { "hotlist_id": 88314, "added": 3, "hotlist_size": 3 } ``` ### remove_candidates_from_hotlist Take candidates out of a hotlist. Access: write. REST: `DELETE /api/v1/jobdiva/hotlists/{hotlist_id}/candidates-from-hotlists`. MCP: `jobdiva_write → remove_candidates_from_hotlist`. | Parameter | Type | Required | Description | |---|---|---|---| | `hotlist_id` | integer | yes | Hotlist ID from list_hotlists. | | `candidate_ids` | integer[] | yes | Candidate IDs to remove. | Removes the candidates from the hotlist and leaves their records alone. Undone with add_candidates_to_hotlist, so it does not wait for your OK. Example response: ```json { "hotlist_id": 88314, "removed": 1, "hotlist_size": 2 } ``` ### create_submittal Submit a candidate to a job with status, rates and notes. Access: write, asks the user first. REST: `POST /api/v1/jobdiva/jobs/{job_id}/submittals`. MCP: `jobdiva_write → create_submittal`. | Parameter | Type | Required | Description | |---|---|---|---| | `job_id` | integer | yes | Job ID from search_jobs or get_job. | | `candidate_id` | integer | yes | Candidate ID from search_candidates or find_candidate. | | `status` | string | no | Submittal status as used in your JobDiva account, for example Submitted. | | `quoted_bill_rate` | number | no | Bill rate quoted to the client. | | `pay_rate` | number | no | Pay rate for the candidate. | | `rate_unit` | string | no | Unit of both rates, for example hour. | | `currency` | string | no | Currency code of both rates, for example USD. | | `internal_notes` | string | no | Notes for your own team. | Creates the submittal and returns its submittal_id. It records the quoted bill rate and the pay rate, and can reach the client, so check list_submittals first to avoid a second submittal for the same person. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "submittal_id": 7719203, "job_id": 24071835, "candidate_id": 5830117, "status": "Submitted", "quoted_bill_rate": 105, "pay_rate": 90, "rate_unit": "hour", "currency": "USD", "submittal_date": "2026-10-23" } ``` ## How do I connect JobDiva to Claude Code, Codex or Cursor? Connecting JobDiva takes three steps: sign up, sign in to JobDiva 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 JobDiva to your agent. 1. **Create an account** Sign up and add JobDiva in the console. Your API key is there too. 2. **Sign in to JobDiva in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to JobDiva 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 JobDiva 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 job 24071835, run a Talent Search for SQL and dbt within 25 miles of Chicago, read the best matches, and put the ones that fit into a new hotlist linked to the job. ``` ### Call JobDiva 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/jobdiva 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 POST https://cotlet.dev/api/v1/jobdiva/candidates \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"first_name":"Dana","last_name":"Whitfield","email":"dana.whitfield@example.com","cell_phone":"+1 312 555 0182","city":"Chicago","state":"IL","skills":["SQL","Python"]}' ``` 3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing. ``` { "candidate_id": 5841230, "name": "Dana Whitfield", "status": "created" } ``` ## Why use Cotlet for JobDiva? **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 JobDiva 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 JobDiva changes, the tool pauses until we fix it. - Failed calls cost nothing. ## Is it safe to connect JobDiva to Cotlet? Yes. You sign in to JobDiva yourself, in your own Cloud Browser, and we never save your password. Your agents only get JobDiva 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 JobDiva integration?** No, Cotlet is independent of JobDiva. JobDiva's own API is open only to approved partners. Cotlet works through your own JobDiva account, the way you use JobDiva 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 JobDiva in your console: your agents lose access at once and you stay signed in. Signing out of JobDiva in the browser works too, and Reset browser deletes the whole profile. ## Is there a JobDiva MCP server on GitHub? You can build on the JobDiva API yourself. It needs a client ID from JobDiva, a login for the API and a wrapper that you write, host and keep in step with the spec. Cotlet works in your own JobDiva login instead and keeps the integration running for you. | | JobDiva API | Cotlet | |---|---|---| | Setup | Get a client ID from JobDiva, sign in with a username and password, then write and host a wrapper | Sign up, sign in to JobDiva once, add one MCP server or API key | | When JobDiva changes | The API is versioned and documented, but you update your own code | Our team runs automatic checks and fixes the integration for you | | Your JobDiva session | Not used; the API signs in with a client ID, username and password you store | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click | | When the session expires | Your code signs in again with the stored password | Your Cloud Browser keeps you signed in; if JobDiva logs you out, your agent gets a link to sign in again | | Upkeep | You host, monitor and debug it | Nothing to host or update | | Where it runs | Your servers, polling for changes because the spec has no webhooks | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule | | Price | JobDiva publishes no API price; ask JobDiva support | 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 JobDiva 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 JobDiva API cost? Free 7-day trial with 2,000 credits, no card needed. After that, the JobDiva 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 10 credits (about $0.04 to $0.06), 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 10 credits | Per 1,000 credits | |---|---|---|---| | 5,000 | $29 | 500 | $5.80 | | 15,000 | $79 | 1,500 | $5.27 | | 32,000 | $149 | 3,200 | $4.66 | | 60,000 | $249 | 6,000 | $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 JobDiva 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 JobDiva 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 JobDiva only after you enable it. When JobDiva 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 JobDiva, sign out of JobDiva 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. - **JobDiva's terms:** You use your own JobDiva account and stay responsible for following JobDiva's terms. Cotlet is independent and not affiliated with JobDiva. [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 JobDiva in the console and press Request access. Then you create your API key and connect JobDiva there. **Do I need to be technical?** No. You sign in to JobDiva 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 JobDiva to Cotlet?** Yes. You sign in to JobDiva yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get JobDiva 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 JobDiva 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 JobDiva 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 JobDiva's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. JobDiva 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 JobDiva 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?** JobDiva 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). **Does it work with Azure Sign In?** Yes. JobDiva's sign-in page offers Azure Sign In next to email and password, and a Choose Your Team step. You complete both yourself in your Cloud Browser. Cotlet keeps only the session, never your password. **Can the agent change timesheets, billing or pay records?** No. The tools cover candidates, notes, jobs, hotlists and submittals. JobDiva's API also has financial endpoints for timesheets, billing and payroll, but Cotlet has no tool for them. **Can my agent post or send messages in JobDiva without asking me?** No. Every call to create_submittal 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_candidate, add_candidate_note, create_hotlist, add_candidates_to_hotlist and remove_candidates_from_hotlist run without asking, because they send nothing to anyone and one call undoes it. **Can I use the JobDiva 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/jobdiva 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.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md) 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.