# MarketSharp API and MCP server

> MarketSharp has a read-only OData API that account admins enable under API Maintenance (checked 11 Oct 2026). Its REST API, the only way to write data, is reserved for approved partners who serve at least 20 MarketSharp customers, after an NDA and legal review.

CRM for home improvement contractors and remodelers: leads, inquiries, sales appointments, jobs, contracts and follow-up activities.

## What is the MarketSharp API?

Cotlet's MarketSharp API exposes 14 endpoints for your own MarketSharp account: search contacts, get contact, list appointments, list jobs, get job, list activities, create lead, schedule appointment, result appointment, add note, add activity, complete activity, update job status and issue appointments. The search_contacts endpoint returns find prospects, leads and customers by name, phone, email or address, like Quick Find. Each endpoint takes simple JSON inputs like contact_id, limit or salesperson and works both as an MCP tool for agents and as a REST call for scripts.

- **Category:** [Local services & SaaS](https://cotlet.dev/integrations/category/local-services-saas)
- **Endpoints:** 14 (6 read, 8 write)
- **Updated:** 2026-10-11

MarketSharp has a read-only OData API that account admins enable under API Maintenance (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for MarketSharp with 14 endpoints (6 read, 8 write): your AI agent signs in as you and does the work.

## Does MarketSharp have an official API?

MarketSharp has a read-only OData API that account admins enable under API Maintenance (checked 11 Oct 2026). Its REST API, the only way to write data, is reserved for approved partners who serve at least 20 MarketSharp customers, after an NDA and legal review.

| Task | MarketSharp official | Cotlet |
|---|---|---|
| Search leads and customers | Yes: Read-only OData, keys from your admin | Yes |
| Read appointments and results | Yes: Read-only OData | Yes |
| Read job and contract status | Yes: Read-only OData | Yes |
| Add a new lead | Partly: Custom Lead Capture form post or Zapier, one way | Yes |
| Result an appointment | No | Yes |
| Add notes to a contact | No | Yes |
| Schedule and complete activities | No | Yes |
| Update job or contract status | No | Yes |

Sources: [MarketSharp API documentation (help center)](https://support.marketsharp.com/hc/en-us/articles/1500011603421-MarketSharp-API-Documentation), [How to connect to the MarketSharp API (OData)](https://support.marketsharp.com/hc/en-us/articles/31177021868183-How-to-Connect-to-the-MarketSharp-API-OData), [Zapier and MarketSharp (help center)](https://support.marketsharp.com/hc/en-us/articles/1500006512682-Zapier-and-MarketSharp), [MarketSharp on Zapier](https://zapier.com/apps/marketsharp/integrations)

## For AI agents

```text
MarketSharp has a read-only OData API that account admins enable under API Maintenance (checked 11 Oct 2026). Its REST API, the only way to write data, is reserved for approved partners who serve at least 20 MarketSharp customers, after an NDA and legal review.
Cotlet provides a hosted MCP server and REST API for MarketSharp: 14 tools (6 read, 8 write).
Access       Request access at https://cotlet.dev/app/signup?app=marketsharp; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/marketsharp
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        search_contacts, get_contact, list_appointments, list_jobs, get_job, list_activities, create_lead, schedule_appointment, result_appointment, add_note, add_activity, complete_activity, update_job_status, issue_appointments
Confirm      create_lead, schedule_appointment, result_appointment, add_note, add_activity, complete_activity, update_job_status, issue_appointments (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/marketsharp-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=marketsharp (MarketSharp is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to MarketSharp once in a browser. 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 MarketSharp 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.
Session: the user signs in to MarketSharp in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following MarketSharp's terms; Cotlet is not affiliated with MarketSharp.
```

## What can an AI agent do in MarketSharp?

Cotlet is best for home improvement contractors and their office managers who want an AI agent to add leads, book appointments and result them in MarketSharp without running or fixing a server.

- **[Add leads from email and book the sales appointment](https://cotlet.dev/integrations/marketsharp-api-mcp-server/add-leads-and-book-appointments)** (runs: daily): "Go through the lead emails that came in since yesterday. For each homeowner, check MarketSharp for an existing contact, add new ones as leads with the right lead source and product interest, and book a sales appointment with the salesperson I name, at a time that does not clash with their calendar." → `search_contacts`, `get_contact`, `list_appointments`, `create_lead`, `schedule_appointment`
- **[Result sales appointments and log the outcome](https://cotlet.dev/integrations/marketsharp-api-mcp-server/result-sales-appointments)** (runs: daily): "Find last week's sales appointments that still have no Appt Result. For each one, ask me or the rep what happened, set the result, add the rep's note to the contact, and tell me if the follow-up activities from our Appointment Rules did not show up." → `list_appointments`, `get_contact`, `result_appointment`, `add_note`
- **Find appointments with no result** (runs: daily): "Which of last week's sales appointments still have no result?" → `list_appointments`
- **Report sold jobs and contract status** (runs: weekly): "List jobs sold this month with their contract status and start date." → `list_jobs`, `get_job`
- **Create follow-up calls for lost appointments** (runs: daily): "Create a follow-up call activity for every lead whose appointment ended without a sale." → `list_appointments`, `add_activity`
- **Email tomorrow's appointments to salespeople** (runs: daily): "Email tomorrow's appointments to the salespeople." → `list_appointments`, `issue_appointments`

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

Yes. Cotlet does not replace your automation platform: it gives it a MarketSharp 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 add leads from email and book the sales appointment, 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 to https://cotlet.dev/api/v1/marketsharp/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/marketsharp/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/marketsharp/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/marketsharp/{tool} 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 403 until the account has an API key with access to MarketSharp.

### search_contacts

Find prospects, leads and customers by name, phone, email or address, like Quick Find. Access: read. REST: `POST /api/v1/marketsharp/search_contacts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | Name, phone, email or address. |
| `contact_type` | enum | no | prospect, lead, customer or all. Default: all. |
| `limit` | integer | no | 1 to 100. Default: 25. |

Searches your MarketSharp contacts the way Quick Find does and returns the best matches first. Use contact_id from each item in get_contact and the write tools. Pages hold up to 100 contacts.

Example response:

```json
{
  "contacts": [
    {
      "contact_id": "3e9b1d44-0c27-4f5a-8e13-6a2b9c0d7f58",
      "name": "Dana Miller",
      "contact_type": "lead",
      "phone": "555-0142",
      "address": "12 Oak Lane, Springfield, IL 62704"
    }
  ]
}
```

### get_contact

Full contact record: phones, addresses, inquiries, appointments, jobs, notes and open activities. Access: read. REST: `POST /api/v1/marketsharp/get_contact`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Contact ID from search_contacts. |

Returns one contact with its phones, addresses, inquiries, appointments, jobs, notes and open activities. Use it before writing, so your agent sees what is already there. IDs in the result feed the other tools.

Example response:

```json
{
  "contact_id": "3e9b1d44-0c27-4f5a-8e13-6a2b9c0d7f58",
  "name": "Dana Miller",
  "contact_type": "lead",
  "inquiries": [
    {
      "inquiry_id": "i_204",
      "product": "Kitchen"
    }
  ],
  "appointments": [
    {
      "appointment_id": "a7f3c2e1-5b8d-4e0a-9c61-2d4f8b7e1a90",
      "starts_at": "2026-10-15T10:00:00-05:00",
      "result": null
    }
  ],
  "jobs": [],
  "notes": [],
  "open_activities": []
}
```

### list_appointments

Sales appointments in a date range with contact, salesperson, set by and Appt Result. Access: read. REST: `POST /api/v1/marketsharp/list_appointments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from` | date | yes | First appointment date. |
| `to` | date | yes | Last appointment date. |
| `salesperson` | string | no | MarketSharp username of the salesperson. |
| `unresulted_only` | boolean | no | Only appointments with no Appt Result yet. |

Lists sales appointments between two dates, earliest first. Set unresulted_only to see the visits that still need an Appt Result. Result is empty until someone sets it.

Example response:

```json
{
  "appointments": [
    {
      "appointment_id": "a7f3c2e1-5b8d-4e0a-9c61-2d4f8b7e1a90",
      "contact": "Dana Miller",
      "salesperson": "jsmith",
      "set_by": "frontdesk",
      "starts_at": "2026-10-08T10:00:00-05:00",
      "result": null
    }
  ]
}
```

### list_jobs

Jobs with job number, customer, job status, contract status, sale date and start date. Access: read. REST: `POST /api/v1/marketsharp/list_jobs`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `sold_from` | date | no | Only jobs sold on or after this date. |
| `sold_to` | date | no | Only jobs sold on or before this date. |
| `job_status` | string | no | One of your company's Job Status values. |
| `limit` | integer | no | 1 to 200. Default: 50. |

Lists jobs, newest sale first, with job number, customer, Job Status, Contract Status, sale date and start date. Filter by sale date or by one of your own Job Status values. Pages hold up to 200 jobs.

Example response:

```json
{
  "jobs": [
    {
      "job_id": "j_5531",
      "job_number": "1042",
      "customer": "Dana Miller",
      "job_status": "Sold",
      "contract_status": "Signed",
      "sold_on": "2026-10-08",
      "start_date": "2026-11-02"
    }
  ]
}
```

### get_job

One job: products, contract amount and status, payments, production tasks and dates. Access: read. REST: `POST /api/v1/marketsharp/get_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job ID from list_jobs or get_contact. |

Returns one job with its products, contract amount and status, payments, production tasks and dates. Use it when the list is not enough.

Example response:

```json
{
  "job_id": "j_5531",
  "job_number": "1042",
  "customer": "Dana Miller",
  "products": [
    "Kitchen"
  ],
  "contract": {
    "amount": 18500,
    "currency": "USD",
    "status": "Signed"
  },
  "payments": [
    {
      "amount": 5000,
      "received_on": "2026-10-08"
    }
  ],
  "start_date": "2026-11-02"
}
```

### list_activities

The Activity List: to-dos for a user and date, with type, contact and due date. Access: read. REST: `POST /api/v1/marketsharp/list_activities`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `assigned_to` | string | no | MarketSharp username. Default: you. |
| `date` | date | no | Day to list. Default: today. |
| `activity_type` | string | no | One of your Activity Types, e.g. a call. |
| `include_completed` | boolean | no | Also return completed activities. Default: false. |

Returns the Activity List for one user and day: type, contact, reference and due date. Open activities only, unless include_completed is set. Use activity_id with complete_activity.

Example response:

```json
{
  "activities": [
    {
      "activity_id": "act_881",
      "activity_type": "Call",
      "contact": "Dana Miller",
      "reference": "Follow up on kitchen quote",
      "due_at": "2026-10-14T09:00:00-05:00",
      "completed": false
    }
  ]
}
```

### create_lead

New lead with contact details and an inquiry, optionally with a sales appointment. Access: write, asks the user first. REST: `POST /api/v1/marketsharp/create_lead`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `first_name` | string | yes | Up to 50 characters. |
| `last_name` | string | yes | Up to 50 characters. |
| `email` | string | no | Email or a phone number is required. |
| `phone` | string | no | Home or cell phone. |
| `address` | object | no | address1, city, state, zip. |
| `primary_source` | string | no | One of your existing primary lead sources. |
| `product_interests` | string[] | no | Product types from your MarketSharp list. |
| `inquiry_notes` | string | no | Added to the inquiry notes. |
| `appointment_at` | datetime | no | Book a sales appointment at this time. |

Creates a lead with an inquiry in your MarketSharp account. A first name, a last name, and an email or a phone number are required. With appointment_at set, a sales appointment is added to the Sales Calendar. Source and product values must exist in your lists. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "contact_id": "3e9b1d44-0c27-4f5a-8e13-6a2b9c0d7f58",
  "inquiry_id": "i_204",
  "appointment_id": "a7f3c2e1-5b8d-4e0a-9c61-2d4f8b7e1a90",
  "contact_type": "lead",
  "status": "created"
}
```

### schedule_appointment

Add a sales appointment to a contact's inquiry; it appears on the Sales Calendar. Access: write, asks the user first. REST: `POST /api/v1/marketsharp/schedule_appointment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Contact ID from search_contacts. |
| `inquiry_id` | string | no | Inquiry to attach it to. Default: the latest one. |
| `starts_at` | datetime | yes | ISO 8601 with time zone. |
| `salesperson` | string | no | MarketSharp username of the salesperson. |

Adds a sales appointment to an inquiry, the latest one unless inquiry_id is set. It appears on the Sales Calendar for the chosen salesperson. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "appointment_id": "a7f3c2e1-5b8d-4e0a-9c61-2d4f8b7e1a90",
  "contact_id": "3e9b1d44-0c27-4f5a-8e13-6a2b9c0d7f58",
  "starts_at": "2026-10-15T10:00:00-05:00",
  "salesperson": "jsmith",
  "status": "scheduled"
}
```

### result_appointment

Set the Appt Result after the visit. A result marked Sold converts the lead to a customer. Access: write, asks the user first. REST: `POST /api/v1/marketsharp/result_appointment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `appointment_id` | string | yes | Appointment ID from get_contact or list_appointments. |
| `result` | string | yes | One of your company's Appt Result options. |

Sets the Appt Result of one appointment to one of your company's own options. A result marked Sold converts the lead to a customer, and the response says what to do next. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "appointment_id": "a7f3c2e1-5b8d-4e0a-9c61-2d4f8b7e1a90",
  "contact_id": "3e9b1d44-0c27-4f5a-8e13-6a2b9c0d7f58",
  "result": "Sold",
  "sold": true,
  "contact_type": "customer",
  "next_step": "Create a job for this customer"
}
```

### add_note

Add a note to the Notes tab of a contact. Access: write, asks the user first. REST: `POST /api/v1/marketsharp/add_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Contact ID from search_contacts. |
| `text` | string | yes | Note text. |

Adds a note to the Notes tab of one contact, under your name. There is no tool to delete a note, so each call asks first. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "note_id": "n_3302",
  "contact_id": "3e9b1d44-0c27-4f5a-8e13-6a2b9c0d7f58",
  "status": "added"
}
```

### add_activity

Add a follow-up activity to a contact and assign it to a user. Access: write, asks the user first. REST: `POST /api/v1/marketsharp/add_activity`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Contact ID from search_contacts. |
| `activity_type` | string | yes | One of your Activity Types. |
| `assigned_to` | string | no | MarketSharp username. Default: you. |
| `due_at` | datetime | no | When the activity is due. |
| `reference` | string | no | Short description shown in the Activity List. |

Adds an activity of one of your Activity Types to a contact and assigns it to a user, who sees it in the Activity List. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "activity_id": "act_881",
  "contact_id": "3e9b1d44-0c27-4f5a-8e13-6a2b9c0d7f58",
  "activity_type": "Call",
  "assigned_to": "jsmith",
  "due_at": "2026-10-14T09:00:00-05:00",
  "status": "added"
}
```

### complete_activity

Mark an activity as completed, with an activity result. Access: write, asks the user first. REST: `POST /api/v1/marketsharp/complete_activity`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `activity_id` | string | yes | Activity ID from list_activities or get_contact. |
| `result` | string | no | One of your activity results. |

Marks one activity as completed and records one of your activity results. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "activity_id": "act_881",
  "completed": true,
  "result": "Left voicemail"
}
```

### update_job_status

Change a job's Job Status or Contract Status, for example to Canceled. Access: write, asks the user first. REST: `POST /api/v1/marketsharp/update_job_status`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job ID from list_jobs or get_contact. |
| `job_status` | string | no | One of your Job Status values. |
| `contract_status` | string | no | One of your Contract Status values. |

Changes the Job Status, the Contract Status or both to values from your own lists. A change like Canceled affects a customer's contract, so the call asks first. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "job_id": "j_5531",
  "job_status": "Canceled",
  "contract_status": "Canceled",
  "status": "updated"
}
```

### issue_appointments

Email and issue appointments to the assigned salespeople, using one of your Issue Appointment templates. Access: write, asks the user first. REST: `POST /api/v1/marketsharp/issue_appointments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `appointment_ids` | string[] | yes | Appointments from list_appointments. |
| `template` | string | no | Issue Appointment email template name. Default: your default template. |

Issues the appointments you pass and emails each assigned salesperson with one of your Issue Appointment templates, or your default one. The emails reach your team. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "issued": 1,
  "emailed_to": [
    "jsmith"
  ],
  "template": "Default",
  "status": "issued"
}
```

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

Connecting MarketSharp takes three steps: request access, sign in to MarketSharp once, then add one MCP server or call the REST API with the same key.

### Connect MarketSharp to your agent.

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

2. **Sign in to MarketSharp once** Open the connect page from the console and sign in to MarketSharp the way you always do. We keep the session, never your password, and you can revoke it anytime.

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 MarketSharp 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.

```
Go through the lead emails that came in since yesterday. For each homeowner, check MarketSharp for an existing contact, add new ones as leads with the right lead source and product interest, and book a sales appointment with the salesperson I name, at a time that does not clash with their calendar.
```

### Call MarketSharp 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 a POST endpoint at /api/v1/marketsharp/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

```
curl https://cotlet.dev/api/v1/marketsharp/result_appointment \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"appointment_id":"a7f3c2e1-5b8d-4e0a-9c61-2d4f8b7e1a90","result":"Sold"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "appointment_id": "a7f3c2e1-5b8d-4e0a-9c61-2d4f8b7e1a90",
  "contact_id": "3e9b1d44-0c27-4f5a-8e13-6a2b9c0d7f58",
  "result": "Sold",
  "sold": true,
  "contact_type": "customer",
  "next_step": "Create a job for this customer"
}
```

## Why use Cotlet for MarketSharp?

**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 MarketSharp yourself. We keep only the session, encrypted with AES-256.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Pick read only, or read and write.
- Anything that reaches other people waits for your OK, unless you switch it off per tool.
- Revoke access in one click.

**Kept working for you**

- We test every integration daily.
- When MarketSharp changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is there a MarketSharp MCP server on GitHub?

The MarketSharp app on Zapier has one action, Submit Lead, which feeds new leads in through a Custom Lead Capture; it cannot read or update anything.

|  | Zapier | Cotlet |
|---|---|---|
| Setup | Create a Custom Lead Capture in MarketSharp Admin, then build a Zap | Request access, sign in to MarketSharp once, add one MCP server or API key |
| What it can do | Submit Lead only, no triggers | Search, read and update contacts, appointments, jobs, notes and activities |
| Reading your data | Not available | Contacts, appointments, jobs and contract status |
| When the session expires | Not needed, the form post uses your company ID | We keep it alive; if MarketSharp logs you out, your agent gets a link to sign in again |
| Where it runs | Zapier cloud, started by another app | Hosted: Claude Code, Codex, Cursor and scripts |
| Price | Your Zapier plan; tasks are counted by Zapier | Free 7-day trial with 5,000 credits, then credits per call |

### 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 MarketSharp 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 the session to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the MarketSharp API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the MarketSharp API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

| Size | Price | Credits / month | Per credit |
|---|---|---|---|
| Solo | $29/mo | 3,000 | about $0.0097 |
| Pro | $99/mo | 12,000 | about $0.0083 |
| Agency | $299/mo | 40,000 | $0.0075 |

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own MarketSharp account.

- **Company details:** The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. [Terms](https://cotlet.dev/terms)
- **Your session:** You sign in to MarketSharp yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a MarketSharp tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect MarketSharp in your dashboard: the session is deleted and access ends at once. 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.
- **MarketSharp's terms:** You use your own MarketSharp account and stay responsible for following MarketSharp's terms. Cotlet is independent and not affiliated with MarketSharp. [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?**

Request access and pick MarketSharp. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

No. You sign in to MarketSharp once in your browser 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 a hosted server safe? My MarketSharp session would leave my computer.**

Cotlet keeps your MarketSharp session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

**Do I need an admin to enable the MarketSharp API?**

Not for Cotlet. It works in your own MarketSharp user account and does not use the OData API, which an account admin enables under API Maintenance (checked 11 Oct 2026).

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

No. Every call to create_lead, schedule_appointment, result_appointment, add_note, add_activity, complete_activity, update_job_status or issue_appointments waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the MarketSharp API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/marketsharp/{tool} from the HTTP Request node.