canonical: https://jentic.com/apis/salesloft.com/salesloft

# SalesLoft Platform

The SalesLoft API reads and writes the people, accounts, and cadences that drive a sales team's outreach in SalesLoft. It creates, upserts, and updates people and accounts, enrolls a person in a cadence through a cadence membership, and logs calls, notes, tasks, and external emails against those records. Read access covers cadence steps and actions, email templates, meetings, call data records, CRM activities, and users, while bulk jobs, imports, and webhook subscriptions handle large syncs and event delivery.

## For AI agents

Create or upsert SalesLoft people and accounts, add a person to a cadence, log calls and notes, create tasks, and subscribe to SalesLoft webhook events.

## Scope

Does not manage deals or opportunities, send marketing newsletters, or find new contact data. Use for SalesLoft people, accounts, cadences, and sales activity only.

## Capabilities

- Create, upsert, or update a person with email_address, title, account_id, and custom_fields
- Enroll a person in a cadence by creating a cadence membership with person_id and cadence_id
- Log a note against a person or account and create tasks with a subject, task_type, and due_date
- List cadences, steps, and pending actions to see what outreach is due next
- Read calls, emails, meetings, and call data records for activity reporting
- Run bulk jobs and imports to sync large batches of people into SalesLoft
- Subscribe a callback_url to SalesLoft event types through webhook subscriptions

## Use cases

### AI agent lead enrollment

An AI agent that qualifies inbound leads needs to push the good ones into outreach. Through Jentic the agent searches for 'add a person to a cadence', loads the SalesLoft operation with its input schema, upserts the person, then creates a cadence membership with the required person_id and cadence_id while the OAuth credential is injected at call time. The lead starts receiving the cadence's steps without a rep touching the record.

Example prompt: POST `/v2/person_upserts.json` with email_address and first_name, then POST `/v2/cadence_memberships.json` with the returned person_id and a cadence_id

### Post-call notes and tasks

After a sales call, reps lose context if notes and next steps are not captured. SalesLoft notes require content, associated_with_type, and associated_with_id, and tasks require subject, person_id, user_id, task_type, due_date, and current_state. A meeting assistant can write both straight onto the person's record.

Example prompt: Create a note on a person with POST `/v2/notes.json`, then create a call task due in three days with POST `/v2/tasks.json`

### Sales activity reporting

Sales managers track how much outreach their team is doing and what it produces. SalesLoft lists calls, emails, call data records, meetings, and successes, along with call dispositions and sentiments, so an analytics job can pull a week of activity per user for a dashboard.

Example prompt: List GET `/v2/activities/calls.json` and GET `/v2/activities/emails.json` for the past week and count activities per user

### CRM and event sync

Teams running SalesLoft next to a CRM keep both in step. Bulk jobs and imports load batches of people, crm_id fields link records across systems, and webhook subscriptions push events to a callback_url with a callback_token so downstream systems react without polling.

Example prompt: Create a webhook subscription with POST `/v2/webhook_subscriptions` for one event_type and a callback_url, then confirm it with GET `/v2/webhook_subscriptions`

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v2/person_upserts.json` | Upsert a person |
| GET | `/v2/people.json` | List people |
| POST | `/v2/cadence_memberships.json` | Create a cadence membership |
| GET | `/v2/cadences.json` | List cadences |
| POST | `/v2/notes.json` | Create a note |
| POST | `/v2/tasks.json` | Create a task |
| GET | `/v2/activities/calls.json` | List calls |
| POST | `/v2/webhook_subscriptions` | Create a webhook subscription |

## Key resources

- **People** — Create, upsert, list, fetch, update, and delete people, plus person stages
- **Accounts** — Create, upsert, list, fetch, update, and delete accounts, plus account stages and tiers
- **Cadences** — List cadences, steps, and actions; import and export cadences; manage cadence memberships
- **Activities** — Calls, emails, notes, tasks, meetings, call data records, and CRM activities
- **Bulk jobs and imports** — Batch data loads and import records
- **Webhook subscriptions** — Create, list, update, and delete event subscriptions

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 56 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 73 / 100
  - Developer Experience & Jentic Compatibility: 60 / 100
  - AI-Readiness & Agent Experience: 31 / 100
  - Agent Usability: 79 / 100
  - Security: 85 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/salesloft.com/salesloft/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring SalesLoft by hand means running an OAuth 2.0 client-credentials exchange against accounts.salesloft.com, refreshing the token, and paging through .json list endpoints. Through Jentic you install once, import SalesLoft from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** SalesLoft puts record ids in the URL path, such as `/v2/people/{id}.json` and `/v2/accounts/{id}.json`, so a rule can pin your agent to one person or account and the operations you pick. You choose the operations it may call, so destructive ones like deleting a person or account are not included unless you add them.
- **Credential handling:** Your SalesLoft OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'add a person to a cadence' or 'log a call note', and Jentic returns the matching SalesLoft operation with its input schema so the agent sends the right fields.

## Related APIs

- **Outreach** — Sales engagement platform with sequences and prospect records
- **Apollo.io** — Prospect database with built-in email sequencing
- **HubSpot CRM Contacts** — CRM contact records that SalesLoft people can sync with
- **Gong** — Conversation intelligence for recorded sales calls

## FAQ

### What authentication does the SalesLoft API use?

The OpenAPI spec declares an OAuth 2.0 client-credentials scheme with the token URL https://accounts.salesloft.com/oauth/token, though it does not attach that scheme to individual operations. Check the SalesLoft developer docs for the credential your account uses. Through Jentic the token is stored by your own instance and injected at call time.

### Can I add a person to a cadence with the SalesLoft API?

Yes. POST `/v2/cadence_memberships.json` enrolls a person, taking person_id and cadence_id as required query parameters, with optional user_id and step_id. Use GET `/v2/cadences.json` to find the cadence id first.

### What are the rate limits for the SalesLoft API?

The OpenAPI spec does not specify rate limits. Check the SalesLoft developer documentation at https://developers.salesloft.com for current limits before running large syncs, and prefer bulk jobs for batch loads.

### Is there a SalesLoft MCP server?

You don't need an MCP server to give your agent SalesLoft. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent finds the people, cadence, and activity operations it needs by intent rather than preloading them all.

### How do I upsert a person in SalesLoft through Jentic?

Search Jentic for 'upsert a person in SalesLoft', load POST `/v2/person_upserts.json`, and execute it with an upsert_key and fields such as email_address, first_name, and title. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit what my agent is allowed to do with the SalesLoft API?

Yes. For a lead-routing agent, write a rule that allows only the person upsert and cadence membership create operations, so it can enroll leads while deleting people, editing custom fields, and changing webhook subscriptions stay off its list. Every call it makes is logged.
