[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)

# JobAdder API and MCP server

> JobAdder has a REST API, but not for every account (checked 22 Oct 2026). Access goes through JobAdder's API Partner terms, its pricing page lists API access on Essential and Pro and not on Lite, and there is no official MCP server.

Recruitment software for agencies and in-house teams: an applicant tracking system, a recruitment CRM and placement management in one account.

## What is the JobAdder API?

Cotlet's JobAdder API exposes 12 endpoints for your own JobAdder account: search candidates, get candidate, search jobs, get job, list job applications, list placements, list tasks, add candidate note, rate application, update application status, create candidate and create task. The search_candidates endpoint returns candidates matching a name, email, phone or resume keyword. Each endpoint takes simple JSON inputs like limit, cursor or candidate_id and works both as an operation of the jobadder_read or jobadder_write MCP tool for agents and as a REST call for scripts.

- **Category:** [HR & recruiting](https://cotlet.dev/integrations/category/hr-recruiting.md)
- **Endpoints:** 12 (7 read, 5 write)
- **Updated:** 2026-10-19

JobAdder has a REST API, but not for every account (checked 22 Oct 2026). Cotlet is a hosted MCP server and REST API for JobAdder with 12 endpoints (7 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does JobAdder have an official API?

JobAdder has a REST API, but not for every account (checked 22 Oct 2026). Access goes through JobAdder's API Partner terms, its pricing page lists API access on Essential and Pro and not on Lite, and there is no official MCP server.

| Task | JobAdder official | Cotlet |
|---|---|---|
| Search and read candidates | Partly: Needs API access: approval and a plan that includes it | Yes |
| List applications for a job | Partly: Needs API access | Yes |
| Update an application status | Partly: Needs API access | Yes |
| Add notes to a candidate | Partly: Needs API access | Yes |
| Create a candidate | Partly: Needs API access | Yes |
| Create tasks | Partly: Needs API access | Yes |
| Work without API approval or on the Lite plan | No | Yes |

Sources: [JobAdder: API terms](https://jobadder.com/api-terms/), [JobAdder: plans and pricing](https://jobadder.com/pricing/), [JobAdder API (partner help center)](https://jobadder-partners.zendesk.com/hc/en-us/articles/8359239946127-JobAdder-API), [JobAdder on Zapier](https://zapier.com/apps/jobadder/integrations)

## For AI agents

```text
JobAdder has a REST API, but not for every account (checked 22 Oct 2026). Access goes through JobAdder's API Partner terms, its pricing page lists API access on Essential and Pro and not on Lite, and there is no official MCP server.
Cotlet provides a hosted MCP server and REST API for JobAdder: 12 tools (7 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=jobadder, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    jobadder_read, jobadder_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/jobadder, each operation at its own route, e.g. PATCH /api/v1/jobadder/applications/{application_id}/status
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   search_candidates, get_candidate, search_jobs, get_job, list_job_applications, list_placements, list_tasks, add_candidate_note, rate_application, update_application_status, create_candidate, create_task
Confirm      add_candidate_note, update_application_status, create_candidate, create_task (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/jobadder-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=jobadder, requests JobAdder in the Cotlet console and creates an API key there.
2. The user signs in to JobAdder once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables JobAdder 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 JobAdder 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 JobAdder 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 JobAdder 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 JobAdder 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 JobAdder's terms; Cotlet is not affiliated with JobAdder.
```

## What can an AI agent do in JobAdder?

Cotlet is best for recruiters and agency teams who want an AI agent to screen applicants, log notes and create follow-ups in JobAdder without running or fixing a server.

- **[Screen new job applicants](https://cotlet.dev/integrations/jobadder-api-mcp-server/screen-job-applicants.md)** (runs: daily): "List the new applications on the Senior Accountant job in JobAdder. Rate each out of 5 against my brief, reject the clear mismatches and leave the rest for me with a one-line reason." → `list_job_applications`, `get_candidate`, `rate_application`, `update_application_status`
- **[Log call notes on candidate records](https://cotlet.dev/integrations/jobadder-api-mcp-server/log-call-notes.md)** (runs: daily): "Here are my notes from today's candidate calls. Find each person in JobAdder, add a note to their record and tell me who I could not match." → `search_candidates`, `get_candidate`, `add_candidate_note`
- **Weekly open jobs and applicants digest** (runs: weekly): "Every Monday, list my open jobs in JobAdder with the number of applications and how many are still unrated." → `search_jobs`, `list_job_applications`
- **Create follow-up tasks for new placements** (runs: daily): "Check JobAdder for placements from the last week. For each one without a follow-up task, create a check-in task for me." → `list_placements`, `list_tasks`, `create_task`
- **Add candidates from CVs and emails**: "Here are three candidates from today's inbox. Check whether each exists in JobAdder and create the ones that do not." → `search_candidates`, `create_candidate`

## Can JobAdder automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a JobAdder 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 screen new job applicants, 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/jobadder/job-applications. | 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/jobadder/job-applications with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 12 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 JobAdder.

### search_candidates

Candidates matching a name, email, phone or resume keyword. Access: read. REST: `GET /api/v1/jobadder/candidates/search`. MCP: `jobadder_read → search_candidates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | Name, email, phone or resume keyword. |
| `limit` | integer | no | Maximum candidates to return. |
| `cursor` | string | no | Next page cursor from the previous call. |

Searches the candidates your JobAdder user can see and returns a page of matches with the candidate_id, name, email, phone and current location of each. Pass next_cursor back as cursor for the next page. The agent uses the candidate_id in get_candidate, add_candidate_note and create_task. A query with no match returns an empty list.

Example response:

```json
{
  "candidates": [
    {
      "candidate_id": "cand_20931",
      "name": "Priya Nair",
      "email": "priya.nair@example.com",
      "phone": "+61 400 000 111",
      "location": "Sydney"
    }
  ],
  "next_cursor": null
}
```

### get_candidate

One candidate record with skills, employment history, applications and recent notes. Access: read. REST: `GET /api/v1/jobadder/candidates/{candidate_id}`. MCP: `jobadder_read → get_candidate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `candidate_id` | string | yes | Candidate id from search_candidates or list_job_applications. |

Returns the profile of one candidate: contact details, skills, employment history and education, their applications with job and status, and the most recent notes. A candidate your JobAdder user cannot open returns APP_PERMISSION_DENIED. Attachments such as the original resume file are not returned.

Example response:

```json
{
  "candidate_id": "cand_20931",
  "name": "Priya Nair",
  "email": "priya.nair@example.com",
  "skills": [
    "Financial reporting",
    "Xero",
    "Month-end close"
  ],
  "employment": [
    {
      "title": "Senior Accountant",
      "company": "Harbour Partners",
      "years": "2020-2026"
    }
  ],
  "applications": [
    {
      "application_id": "app_48213",
      "job": "Senior Accountant",
      "status": "Phone screen"
    }
  ],
  "notes": [
    {
      "note_id": "note_77310",
      "text": "Referred by a client.",
      "created_at": "2026-10-14T09:12:00+11:00"
    }
  ]
}
```

### search_jobs

Jobs matching a title or keyword, with company and status. Access: read. REST: `GET /api/v1/jobadder/jobs/search`. MCP: `jobadder_read → search_jobs`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Title or keyword. Empty lists your jobs. |
| `limit` | integer | no | Maximum jobs to return. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns a page of jobs your JobAdder user can see, each with job_id, title, company, status and the number of applications. Pass next_cursor back as cursor for the next page. The job_id goes into get_job, list_job_applications and list_placements.

Example response:

```json
{
  "jobs": [
    {
      "job_id": "job_5521",
      "title": "Senior Accountant",
      "company": "Harbour Partners",
      "status": "Open",
      "applications": 17
    }
  ],
  "next_cursor": null
}
```

### get_job

One job with its description, company, contact and status. Access: read. REST: `GET /api/v1/jobadder/jobs/{job_id}`. MCP: `jobadder_read → get_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job id from search_jobs. |

Returns the job record: title, description, company, the contact on the client side, location, status and the recruiter who owns it. The description is the text of the job as stored in JobAdder, so the agent can use it as the brief for screening.

Example response:

```json
{
  "job_id": "job_5521",
  "title": "Senior Accountant",
  "company": "Harbour Partners",
  "contact": "Elena Park",
  "location": "Sydney",
  "status": "Open",
  "owner": "Maya Brooks",
  "description": "CPA-qualified accountant to lead month-end close and reporting for a mid-size firm."
}
```

### list_job_applications

Applications on one job with candidate, status, rating and date. Access: read. REST: `GET /api/v1/jobadder/job-applications`. MCP: `jobadder_read → list_job_applications`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job id from search_jobs. |
| `status` | string | no | Only applications in this status, named as in your JobAdder workflow. |
| `limit` | integer | no | Maximum applications to return. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns a page of the applications on one job, each with application_id, candidate_id, candidate name, status, rating out of 5 (null when unrated) and applied_at. Pass next_cursor back as cursor until it comes back empty. Use status to see only applications in one workflow status.

Example response:

```json
{
  "applications": [
    {
      "application_id": "app_48213",
      "candidate_id": "cand_20931",
      "candidate": "Priya Nair",
      "status": "New",
      "rating": null,
      "applied_at": "2026-10-21T22:40:00+11:00"
    }
  ],
  "next_cursor": null
}
```

### list_placements

Placements, optionally of one job, with candidate, start date and status. Access: read. REST: `GET /api/v1/jobadder/placements`. MCP: `jobadder_read → list_placements`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | no | Only placements of this job. |
| `limit` | integer | no | Maximum placements to return. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns a page of placement records your JobAdder user can see, each with placement_id, job, candidate, start date and status. Pass job_id to see the placements of one job. Pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "placements": [
    {
      "placement_id": "plc_3107",
      "job": "Senior Accountant",
      "candidate": "Priya Nair",
      "start_date": "2026-12-01",
      "status": "Confirmed"
    }
  ],
  "next_cursor": null
}
```

### list_tasks

Your JobAdder tasks by view: active, priority, unscheduled, overdue or complete. Access: read. REST: `GET /api/v1/jobadder/tasks`. MCP: `jobadder_read → list_tasks`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `view` | enum | no | active, priority, unscheduled, overdue or complete. Default: active. |
| `limit` | integer | no | Maximum tasks to return. |

Returns the tasks of the signed-in JobAdder user for the view you pick, the same views JobAdder shows for tasks and reminders. Each task has task_id, title, due date and the record it is linked to. The agent uses it to avoid creating a task that already exists.

Example response:

```json
{
  "tasks": [
    {
      "task_id": "task_9084",
      "title": "Check in with Priya Nair",
      "due": "2026-12-08",
      "linked_to": "Priya Nair"
    }
  ],
  "next_cursor": null
}
```

### add_candidate_note

Add a text note to a candidate record. Access: write, asks the user first. REST: `POST /api/v1/jobadder/candidates/{candidate_id}/note`. MCP: `jobadder_write → add_candidate_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `candidate_id` | string | yes | Candidate id from search_candidates. |
| `text` | string | yes | Note text. |

Adds a note to the candidate and returns its note_id and creation time. The note is plain text, visible to your team in JobAdder, and Cotlet has no tool to delete it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "note_id": "note_77412",
  "candidate_id": "cand_20931",
  "created_at": "2026-10-22T17:05:00+11:00"
}
```

### rate_application

Set the rating out of 5 on a job application. Access: write. REST: `POST /api/v1/jobadder/applications/{application_id}/rate`. MCP: `jobadder_write → rate_application`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `application_id` | string | yes | Application id from list_job_applications. |
| `rating` | integer | yes | Rating out of 5. |

Sets the rating of one application and returns it. A rating reaches no candidate and is changed by calling the tool again with another number, so this tool does not wait for your confirmation.

Example response:

```json
{
  "application_id": "app_48213",
  "rating": 4
}
```

### update_application_status

Move a job application to another status of its workflow. Access: write, asks the user first. REST: `PATCH /api/v1/jobadder/applications/{application_id}/status`. MCP: `jobadder_write → update_application_status`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `application_id` | string | yes | Application id from list_job_applications. |
| `status` | string | yes | Status name as shown in your JobAdder workflow, including a custom rejection status. |

Sets the status of one application and returns the old and the new status. In JobAdder a status update can trigger actions, such as an automatic reply to the applicant, depending on how your account is set up. A status the job's workflow does not have fails with an error. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "application_id": "app_48213",
  "previous_status": "New",
  "status": "Phone screen"
}
```

### create_candidate

Create a candidate record with name and contact details. Access: write, asks the user first. REST: `POST /api/v1/jobadder/candidates`. MCP: `jobadder_write → create_candidate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `first_name` | string | yes | First name. |
| `last_name` | string | yes | Last name. |
| `email` | string | no | Email address. |
| `phone` | string | no | Phone number. |

Creates a candidate and returns its candidate_id. Search first: the tool does not merge duplicates. Resume files are not uploaded. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "candidate_id": "cand_20987",
  "name": "Marta Kowal",
  "email": "marta.kowal@example.com"
}
```

### create_task

Create a task for you, optionally linked to a candidate. Access: write, asks the user first. REST: `POST /api/v1/jobadder/tasks`. MCP: `jobadder_write → create_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `title` | string | yes | Task title. |
| `due` | date | no | Due date. Empty makes an unscheduled task. |
| `candidate_id` | string | no | Candidate to link the task to. |

Creates a task for the signed-in JobAdder user with a title and an optional due date and candidate link, and returns its task_id. Tasks for other users are not created. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "task_id": "task_9112",
  "title": "Check in with Priya Nair",
  "due": "2026-12-08",
  "linked_to": "Priya Nair"
}
```

## How do I connect JobAdder to Claude Code, Codex or Cursor?

Connecting JobAdder takes three steps: sign up, sign in to JobAdder 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 JobAdder to your agent.

1. **Create an account** Sign up and add JobAdder in the console. Your API key is there too.

2. **Sign in to JobAdder in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to JobAdder 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 JobAdder 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.

```
List the new applications on the Senior Accountant job in JobAdder. Rate each out of 5 against my brief, reject the clear mismatches and leave the rest for me with a one-line reason.
```

### Call JobAdder 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/jobadder 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/jobadder/applications/app_48213/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.

```
{
  "application_id": "app_48213",
  "previous_status": "New",
  "status": "Phone screen"
}
```

## Why use Cotlet for JobAdder?

**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 JobAdder 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 JobAdder changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect JobAdder to Cotlet?

Yes. You sign in to JobAdder yourself, in your own Cloud Browser, and we never save your password. Your agents only get JobAdder 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 JobAdder integration?**

No, Cotlet is independent of JobAdder. JobAdder's own API is open only to approved partners. Cotlet works through your own JobAdder account, the way you use JobAdder 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 JobAdder in your console: your agents lose access at once and you stay signed in. Signing out of JobAdder in the browser works too, and Reset browser deletes the whole profile.

## Is there a JobAdder MCP server on GitHub?

Zapier has an app for JobAdder with fixed triggers and actions such as adding a note or updating an application status. It suits rules of the type "this happened, do that". Cotlet adds an agent that reads candidates and applications, decides and acts, and it works in your own JobAdder account without API approval. Use both where both fit.

|  | Zapier | Cotlet |
|---|---|---|
| Setup | Connect JobAdder in Zapier, build one Zap per job | Sign up, sign in to JobAdder once, add one MCP server or API key |
| Best for | Fixed rules: a record changes, one action follows | Jobs where an agent reads records and decides what to do |
| When JobAdder changes | The Zapier app is kept up to date by its maintainers | Our team tests it daily and fixes it for you; failed calls are free |
| Your JobAdder access | A connection to the JobAdder API | Your own login in your Cloud Browser in the EU, profile encrypted, never your password |
| When the session expires | The connection is renewed by the app | Your Cloud Browser keeps you signed in; if JobAdder logs you out, your agent gets a link to sign in again |
| Where it runs | Hosted, inside Zapier | Hosted: Claude Code, Codex, Cursor, n8n, Make, Zapier and scripts, also on a schedule |
| Price | Your Zapier plan | 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 JobAdder 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 JobAdder API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the JobAdder 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 JobAdder 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 JobAdder 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 JobAdder only after you enable it. When JobAdder 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 JobAdder, sign out of JobAdder 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.
- **JobAdder's terms:** You use your own JobAdder account and stay responsible for following JobAdder's terms. Cotlet is independent and not affiliated with JobAdder. [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 JobAdder in the console and press Request access. Then you create your API key and connect JobAdder there.

**Do I need to be technical?**

No. You sign in to JobAdder 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 JobAdder to Cotlet?**

Yes. You sign in to JobAdder yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get JobAdder 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 JobAdder 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 JobAdder 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 JobAdder's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. JobAdder 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 JobAdder 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?**

JobAdder 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).

**Do I need JobAdder API access or the Pro plan?**

No. Cotlet works in your own JobAdder login and does not use the API. JobAdder's pricing page lists API access on Essential and Pro and calls the API + Sandbox add-on not available on Lite. What you can see and change still follows your user's permissions in JobAdder.

**Can the agent email or message candidates?**

No tool sends an email or an SMS. A status change can still trigger an action in JobAdder, such as an automatic reply, because JobAdder lets a status update trigger actions. That is why update_application_status waits for your OK by default.

**Can my agent post or send messages in JobAdder without asking me?**

No. Every call to add_candidate_note, update_application_status, create_candidate or create_task waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. rate_application runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the JobAdder 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/jobadder 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.