API review
Salesloft API review
Enterprise sales engagement platform (cadences, dialer, conversations, deals) with a REST API v2 (~215 endpoints), customer API keys or OAuth apps, a team-wide cost-based rate limit, async bulk upsert jobs, signed webhooks and an official read-only MCP server for Agent-package customers; sales-quoted pricing. Best for integrating with a customer's Salesloft team: people, accounts, cadences, cadence memberships, steps/actions, calls, notes, meetings, conversations.
Rate limits
Cost-based, per TEAM (shared by all integrations on that team): 600 cost points per minute, default cost 1 per request.
More on limitsLess
Page parameter beyond 100 costs extra: 101-150 = 3, 151-250 = 8, 251-500 = 10, 501+ = 30 points. Headers x-ratelimit-endpoint-cost and x-ratelimit-remaining-minute. Salesloft can adjust per customer/team. MCP server calls route through the API and count against the same limits.
How to get an API key
Salesloft uses OAuth. The steps below follow Salesloft's own docs.
- Create a Salesloft account.
- Customers: Your Applications -> API Keys -> Create New, pick scopes (keys look like ak_ + 64 hex, act as the issuing user). Partners: create an OAuth app (Authorization Code) or, for private admin use, Client Credentials.
- Send it with every request: header: Authorization: Bearer <token>.
- Make a first call: List all owned cadences, Cadences are user defined engines to run their outbound process. Keep the key in an environment variable, never in the command.
curl -X GET "https://api.salesloft.com/public_api/v1/cadences" \ -H "Authorization: Bearer $SALESLOFT_ACCESS_TOKEN"
Where the docs live
| What | Where |
|---|---|
| Documentation | developers.salesloft.com/docs/platform/intro |
| API reference | developers.salesloft.com/docs/api |
| Base URL | https://api.salesloft.com |
| MCP server | https://mcp.salesloft.com/mcp |
Strengths and limits
Where it fits
- Integrating with a customer's Salesloft team: people, accounts, cadences, cadence memberships, steps/actions, calls, notes, meetings, conversations
- Signed (HMAC-SHA1) webhooks on 37 event types incl. cadence membership, meeting booked, conversation transcript
- Async bulk upserts of people/accounts/calendar events via bulk jobs
- Third-party dialer integrations (Voice Links, call data records)
Where it falls short
- Self-serve cold email at volume: no public pricing, demo only
- Partner apps on API keys: partner apps must use OAuth or will not be approved
- Deep page-number pagination: pages past 100 cost 3-30 rate-limit points each; use an updated_at cursor
- AI agents that need to write: the official MCP server is read-only (no updates, writes or deletes, no cadence data) and only included with Salesloft Agent packages
Worth knowing
- Rate limit is per TEAM, not per integration: every connected app shares the same 600 points/min.
- High page numbers are surcharged (page 501+ costs 30 points); poll with an updated_at cursor instead.
- Out-of-range per_page/page values are silently reset to defaults instead of erroring.
- API keys are customer-only; partner apps submitted on API keys are rejected.
- Client Credentials apps cannot be allowlisted and run with the creating admin's permissions.
9 moreShow fewer
- Only one bulk job runs at a time per tenant and the queue is shared with teammates; results deleted after 30 days.
- Webhook retries are short: 3 retries 15 s apart, then failed; a brief outage loses events.
- Action/step details are only supported for phone-type actions.
- Turning on Voice Links releases all existing Salesloft phone numbers.
- Request parameters are rendered client-side on the reference pages, so static downloads carry only method, path and description.
- The official MCP server is read-only, beta, excludes cadences, needs an admin toggle, and is only included with Salesloft Agent packages.
- MCP queries are ordinary API calls and spend the same team-wide 600 points/min as every other integration.
- email_contents is a privileged scope (needed for the email_with_body_and_subject_updated webhook), not an event type.
- Voice Links and dialer webhooks are switched on per customer by their customer success manager, not self-serve.
Who should use it
- Use Salesloft for
- Integrating with a customer's Salesloft team: people, accounts, cadences, cadence memberships, steps/actions, calls, notes, meetings, conversations
- Look elsewhere for
- Self-serve cold email at volume: no public pricing, demo only
If Salesloft is not the answer
Other Email sending tools in this directory, each with its own review.
Aimfox
LinkedIn outreach
From $40.83/moOfficial MCP
Best for multi-account LinkedIn outreach where you want to rent extra sender profiles natively.
Aimfox API review
Dripify
LinkedIn outreach
From $59/moOfficial MCP
Best for solo sellers or small teams running LinkedIn + email sequences from their own accounts.
Dripify API review
EmailBison
Email sending
From $599/mo
Best for agencies and teams sending hundreds of thousands of emails a month that want dedicated IPs and no per-seat or per-lead….
EmailBison API reviewBefore you build
Three things to settle first, each read off Salesloft's own pages.
- Keep the key out of your codeOAuth. It is sent as: header: Authorization: Bearer <token>.
- Design around the rate limitCost-based, per TEAM (shared by all integrations on that team): 600 cost points per minute, default cost 1 per request.
- Know the catch before you scaleRate limit is per TEAM, not per integration: every connected app shares the same 600 points/min.
Want us to build it for you?
Tell us what you want Salesloft to do in your stack. We will show you how we would wire it into your data, outbound or CRM, and what we would check first.
Read from salesloft.com/pricing, developers.salesloft.com/docs/api and developers.salesloft.com/docs/platform/api-basics/rate-limits. Verified 25 Oct 2026.
All 215 endpointsFor developers: method, path, what it does and what it costs.
| Method | Path | What it does | Cost |
|---|---|---|---|
| GET | /public_api/v1/cadences | List all owned cadences, Cadences are user defined engines to run their outbound process. | Not stated |
| GET | /public_api/v1/calls | List all account calls, A call is the data recording the results of a phone interaction with a person. | Not stated |
| POST | /public_api/v1/companies | Create a single company, Companies are unique across a team, so any companies you add will be visible to the entire team. | Not stated |
| GET | /public_api/v1/companies/:id | Fetches a single company, A Company can be looked up by id or domain. Companies are unique by domain across a team, so any edits you make to a Company will be visible to every user on the team. IDs will never change. | Not stated |
| PUT | /public_api/v1/companies/:id | Updates a single company, A company can be looked up by id or domain. Companies are unique across teams, so any edits you make to a company will be visible to every user on the team. IDs will never change. | Not stated |
| GET | /public_api/v1/me | Fetches information about a User, User information which can be used to create an account in an integrating system. | Not stated |
| GET | /public_api/v1/custom_fields | List all team custom fields, Custom Fields are used to add additional information to people. They are simple key/value pairs stored on a Person. | Not stated |
| POST | /public_api/v1/people | Create a single person, People are unique by email address across a team, so any people you add will be visible to the entire team. | Not stated |
| GET | /public_api/v1/people/:id | Fetches a single person, A person can be looked up by id or email. People are unique by email address across a team, so any edits you make to a person will be visible to every user on the team. IDs will never change. | Not stated |
| PUT | /public_api/v1/people/:id | Updates a single person, A person can be looked up by id or email. People are unique by email address across a team, so any edits you make to a person will be visible to every user on the team. IDs will never change. | Not stated |
| POST | /public_api/v1/people/:person_id/cadence_memberships | Add a person to a cadence | Not stated |
| GET | /public_api/v1/people/:person_id/cadence_memberships | List all cadences for a person, Results are ordered by cadence_id ASC. | Not stated |
| GET | /public_api/v1/successes | List all account successes, A success is recorded manually by a user when they take an action that they classify as successful. This could be reaching a prospect, getting a demo, etc. It is important to understand how success is | Not stated |
| GET | /public_api/v1/tags | List all tags, Tags are used to organize different entities in the system. Tags are added to a specific entity through the endpoints for that entity. | Not stated |
| GET | /v2/account_stages | List account stages, Fetches multiple account stage records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/account_stages/:id | Fetch an account stage, Fetches an account stage, by ID only. | Not stated |
| GET | /v2/account_team_member_roles | List CRM Account Team Member Roles, Fetches multiple CRM Account Team Member Role records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/account_tiers | List Account Tiers, Fetches multiple account tier records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/account_tiers/:id | Fetch an account tier, Fetches an account tier, by ID only. | Not stated |
| GET | /v2/account_types | List distinct account types, Fetches distinct account types for the team to be used in filter selections. Returns an array of unique account type values that exist in the team's companies. This endpoint respects user permissions | Not stated |
| POST | /v2/account_upserts | Upsert an account, Upserts an account record. The upsert_key dictates how the upsert will be performed. The create and update behavior is exactly the same as the individual create and update endpoints. | Not stated |
| POST | /v2/accounts | Create an account, Creates an account. | Not stated |
| DELETE | /v2/accounts/:id | Delete an account, Deletes an account. This operation is not reversible without contacting support. This operation can be called multiple times successfully. | Not stated |
| GET | /v2/accounts | List accounts, Fetches multiple account records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/accounts/:id | Fetch an account, Fetches an account, by ID only. | Not stated |
| PUT | /v2/accounts/:id | Update an existing Account, Updates an account. | Not stated |
| GET | /v2/action_details/call_instructions | List call instructions, Fetches multiple call instruction records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/action_details/call_instructions/:id | Fetch a call instructions, Fetches a call instruction, by ID only. | Not stated |
| GET | /v2/actions | List actions, Fetches multiple action records. The records can be filtered, paged, and sorted according to the respective parameters. Only actions that are currently "in_progess" will be returned by this endpoint. | Not stated |
| GET | /v2/actions/:id | Fetch an action, Fetches an action, by ID only. This endpoint will only return actions that are in_progress or pending_activity. Once an action is complete, the request for that action will return a 404 status code. | Not stated |
| POST | /v2/activities/calls | Create a call, Creates a call. The parameters of this endpoint can be used to create an action and ensure that the CRM Task is mapped correctly. | Not stated |
| GET | /v2/activities/calls | List calls, Fetches multiple call records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/activities/calls/:id | Fetch a call, Fetches a call, by ID only. | Not stated |
| POST | /v2/activities | Create an activity, Creates an activity. An activity will mark the associated action as completed. Currently, only certain action types can have an activity explicitly created for them. | Not stated |
| GET | /v2/activities/emails | List emails, Fetches multiple email records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/activities/emails/:id | Fetch an email, Fetches an email, by ID only. | Not stated |
| GET | /v2/activity_histories | List Past Activities, Fetches all of the customer's past activities for your application. Returns all the Activities that are found on the Salesloft Activity Feed. | Not stated |
| POST | /v2/audit_reports | Create a new audit report, Creates a request for a new audit report. | Not stated |
| GET | /v2/audit_reports | List generated audit reports, Returns all reports that have been requested by user's tenant_id, paged by 25 records | Not stated |
| GET | /v2/audit_reports/:id | Fetch an audit report, Fetch an audit report by ID. | Not stated |
| POSTasync | /v2/bulk_jobs | Create a bulk job, Creates a bulk job. The type of the bulk job must be included when created. | Not stated |
| DELETE | /v2/bulk_jobs/:id | Cancel a bulk job, Cancels a bulk job and marks all pending records as cancelled. Cannot cancel jobs that are already completed. | Not stated |
| GET | /v2/bulk_jobs | List bulk jobs, Fetches multiple bulk job records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| POST | /v2/bulk_jobs/:bulk_jobs_id/job_data | Create job data for a bulk job, Upload job data for the specified bulk job. Upload an array of objects, where element contains the parameters necessary to execute the individual calls. Each call to this endpoint can handle up to 5,0 | Not stated |
| GET | /v2/bulk_jobs/:bulk_jobs_id/job_data | List job data for a bulk job, Fetches multiple job data records for a given bulk job. Pagination is not supported, but cursor based polling is via use of the id[gt] filter. Pass the last id seen (i.e. id[gt]=1234 ) in order to get | Not stated |
| GET | /v2/bulk_jobs/:bulk_jobs_id/results | List job data for a completed bulk job., Fetches multiple job data records for a completed bulk job. Note that until a bulk job's state is set to done the returned data will be an empty array. Pagination is not supported, but cursor based po | Not stated |
| GET | /v2/bulk_jobs/:id | Fetch a bulk job, Fetches a bulk job, by ID only. | Not stated |
| PUT | /v2/bulk_jobs/:id | Update a bulk job, Updates a bulk job's name and / or marks a bulk job as 'ready_to_execute'. May only be updated if the bulk job is still in an "open" state. | Not stated |
| POST | /v2/bulk_reschedule_tasks | Reschedule many tasks at once, Reschedule many tasks in batch. | Not stated |
| POST | /v2/cadence_bulk_archives | Archive cadences in bulk, Archives up to 100 cadences in the background. Cadences that are not visible to the current user are ignored. When all is true, cadences owned by inactive users are also ignored. The response lists th | Not stated |
| POST | /v2/cadence_bulk_memberships | Create cadence memberships in bulk, Adds multiple people to a cadence. The people are specified in the form of a listing filter. Any person record that matches the specified filter must be allowed to be added to the cadence, otherwise | Not stated |
| POST | /v2/cadence_collection_export_downloads | Create a cadence collection export download, Puts in a request to generate a cadence collection export download. The request will be processed asynchronously and the download will be sent to the user via email. | Not stated |
| GET | /v2/cadence_collection_exports/:id | Export a cadence collection, Exports a cadence collection as JSON. | Not stated |
| POST | /v2/cadence_collection_imports | Import cadence collections from JSON, New cadence collections can be created from JSON settings. The import format mirrors the cadence collection export format. Requires team admin access. | Not stated |
| GET | /v2/cadence_collections | List cadence collections, Fetches multiple cadence collection records. The records can be filtered, sorted, and paged according to the respective parameters. | Not stated |
| GET | /v2/cadence_collections/:id | Fetch a cadence collection, Fetches a single cadence collection by ID. This endpoint is useful for preselecting a collection in cadence create and edit pages. | Not stated |
| POST | /v2/cadence_export_downloads | Create a cadence export download, Puts in a request to generate a cadence export download. The request will be processed asynchronously and the download will be sent to the user via email. | Not stated |
| GET | /v2/cadence_exports/:id | Export a cadence, Exports a cadence as JSON. | Not stated |
| POST | /v2/cadence_imports | Import cadences from JSON, New cadences can be created or steps can be imported onto existing cadences which do not have steps. Visit here for more details. | Not stated |
| POST | /v2/cadence_memberships | Create a cadence membership, Adds a person to a cadence. person_id and cadence_id are required, and must be visible to the authenticated user. user_id will default to the authenticated user, but can be set to any visible user on | Not stated |
| DELETE | /v2/cadence_memberships/:id | Delete a cadence membership, Cadence Membership | Not stated |
| GET | /v2/cadence_memberships | List cadence memberships, Fetches multiple cadence membership records. The records can be filtered, paged, and sorted according to the respective parameters. A cadence membership is the association between a person and their c | Not stated |
| GET | /v2/cadence_memberships/:id | Fetch a cadence membership, Fetches a cadence membership, by ID only. | Not stated |
| GET | /v2/cadence_stats/:id | Fetch stats for a cadence, Fetches stats for a cadence, by ID only. | Not stated |
| POST | /v2/cadences/:cadence_id/activate | Activate a draft cadence, Transitions a draft cadence to active. Returns an error if the team has the cadence approval flow setting enabled, use the request review endpoint instead. | Not stated |
| GET | /v2/cadences | List cadences, Fetches multiple cadence records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/cadences/:id | Fetch a cadence, Fetches a cadence, by ID only. | Not stated |
| GET | /v2/cadences/:cadence_id/step_groups | List step groups, Fetches the step groups of a cadence, ordered by day and then by their position within the day. | Not stated |
| GET | /v2/cadences/:cadence_id/step_groups/:id | Fetch a step group, Fetches a single step group of a cadence. | Not stated |
| GET | /v2/calendar_availabilities | Get calendar availabilities, Fetches available time slots for a user's calendar within the specified date range. This endpoint returns periods of free time that can be used for scheduling meetings. | Not stated |
| POST | /v2/calendar_events | Create a Meeting, Creates a new Meeting in the user's calendar. This endpoint supports both external calendar synchronization and internal-only event creation for CRM tracking. You can create meetings with attendees, t | Not stated |
| GET | /v2/calendar/events | List calendar events, Returns all calendar events, paginated and filtered by the date. | Not stated |
| PUT | /v2/calendar_events/:id | Update a meeting, Updates a meeting, by ID only. | Not stated |
| POST | /v2/calendar/events/upsert | Upsert a calendar event, Upserts a calendar event object. Upsert key is a combination of id and i_cal_uid scoped to the given calendar_id. Bulk operations: This endpoint is used for bulk operations, see bulk jobs for integra | Not stated |
| GET | /v2/calendar/events_with_recurring | List calendar events with recurring occurrences, Returns all calendar events including expanded recurring event occurrences, paginated and filtered by date. This endpoint includes performance optimizations for handling recurring events efficiently. | Not stated |
| POST | /v2/call_data_records | Create a call data record | Not stated |
| GET | /v2/call_data_records | List call data records, Fetches multiple call data records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/call_data_records/:id | Fetch a call data record, Fetches a call data record, by ID only. | Not stated |
| PUT | /v2/call_data_records/:id | Update a call data record | Not stated |
| GET | /v2/call_dispositions | List call dispositions, Fetches multiple call disposition records. The records can be sorted according to the respective parameters. Call dispositions must be configured in application. This will change in the future, but pl | Not stated |
| GET | /v2/call_dispositions/:id | Fetch a call disposition, Fetches a call disposition by ID only. | Not stated |
| GET | /v2/call_sentiments | List call sentiments, Fetches multiple call sentiment records. The records can be sorted according to the respective parameters. Call sentiments must be configured in application. This will change in the future, but please | Not stated |
| GET | /v2/call_sentiments/:id | Fetch a call sentiment, Fetches a call sentiment by ID only. | Not stated |
| POST | /v2/conversations/calls | Create a new call, Creates a dialer call | Not stated |
| GET | /v2/conversations | Fetch conversations, Fetches multiple conversations. The conversations can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/conversations/:id/recording | Fetch Conversation media, Fetches an extended version of a Conversation including media | Not stated |
| GET | /v2/conversations/:id/extensive | Fetch an extensive conversation, Fetches an extended version of a Conversation, it will include AI generated features if they are available, such as, Summary, Actions Items and Key Moments | Not stated |
| GET | /v2/conversations/:id | Fetch a conversation, Fetches a single conversation | Not stated |
| GET | /v2/transcriptions | List Transcriptions, List Conversation Transcriptions | Not stated |
| GET | /v2/transcriptions/:id/artifact | Fetch a Transcription Artifact, Fetches a Conversation Transcription Artifact | Not stated |
| GET | /v2/transcriptions/:id/sentences | Fetch a Transcription's sentences, Fetches a Conversation Transcription's sentence data | Not stated |
| GET | /v2/transcriptions/:id | Fetch a Transcription, Fetches a Conversation Transcription | Not stated |
| GET | /v2/crm_account_team_members | List CRM Account Team Members, Fetches multiple CRM Account Team Member records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/crm_activities | List crm activities, Fetches multiple crm activity records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/crm_activities/:id | Fetch a crm activity, Fetches a crm activity, by ID only. | Not stated |
| GET | /v2/crm_activity_fields | List crm activity fields, Fetches multiple crm activity field records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/crm_team_members_with_roles | List CRM Account Team Members With Roles, Fetches multiple CRM Account Team Member records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/crm_users | List crm users, +1 (770) 756-8022 | Not stated |
| POST | /v2/custom_fields | Create a custom field, Creates a custom field. | Not stated |
| DELETE | /v2/custom_fields/:id | Delete a custom field, Deletes a custom field. | Not stated |
| GET | /v2/custom_fields | List custom fields, Fetches multiple custom field records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/custom_fields/:id | Fetch a custom field, Fetches a custom field, by ID only. | Not stated |
| GET | /v2/custom_roles | List custom roles, Fetches multiple custom role records. The records can be filtered, and sorted according to the respective parameters. A custom role is any role that is not Admin or User. | Not stated |
| GET | /v2/custom_roles/:id | Fetch a custom role, Fetches a custom role, by ID only. | Not stated |
| POST | /v2/data_control/account_and_people_redaction | Submit an account and people redaction request, Initiate a request to redact and delete all data regarding accounts and their related people. | Not stated |
| POST | /v2/data_control/account_redaction | Execute an account redaction workflow, Execute a workflow to affect data in all systems concerned with redacting a non-user account. | Not stated |
| POST | /v2/data_control/people_soft_deletion | Submit a people soft deletion request, This endpoint supports the ability to soft delete multiple People from Salesloft based on their Salesloft Person ID. | Not stated |
| GET | /v2/data_control/requests | Retrieve a list of Requests, Query Requests by some given filters | Not stated |
| GET | /v2/data_control/requests/:id | Fetch a Request record, Get the details for a given Request | Not stated |
| POST | /v2/data_control/right_to_be_forgotten | Submit a right to be forgotten request, This endpoint supports soft deleting a Person from Salesloft based on their Salesloft Person ID and redacting all P.I.I. (Personally Identifiable Data) from the Person and related Activity records and | Not stated |
| POST | /v2/email_missing_tags | Requests a check of the template for missed tags, Requests a check of the template for missed tags. Returns a list of missed tags. | Not stated |
| GET | /v2/email_template_attachments | List email template attachments, Fetches multiple email template attachment records. The records can be filtered and paged according to the respective parameters. Only attachments from email templates that the user has permission to | Not stated |
| POST | /v2/email_templates | Create Personal Email Template, Create a new personal email template | Not stated |
| GET | /v2/email_templates | List email templates, Fetches multiple email template records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/email_templates/:id | Fetch an email template, Fetches an email template, by ID only. | Not stated |
| PUT | /v2/email_templates/:id | Update Personal Email Template, Update a personal email template | Not stated |
| POST | /v2/external/configurations | Create a configuration, Creates a configuration. Valid object types are: people, users, accounts, and opportunities. Learn more about External ID configurations here. | Not stated |
| DELETE | /v2/external/configurations/:id | Delete a configuration, Delete a configuration, specified by id. | Not stated |
| GET | /v2/external/configurations | List team configurations, Returns all configurations for a team. | Not stated |
| POST | /v2/external_emails | Create an External Email, Creates an external email object. | Not stated |
| POST | /v2/external/mappings | Create a mapping, Creates a mapping. Valid object types are: people, users, accounts, and opportunities. Learn more about External ID mappings here. | Not stated |
| DELETE | /v2/external/mappings/:id | Delete a mapping, Deletes a mapping, specified by id. | Not stated |
| GET | /v2/external/mappings | List team mappings, Returns all mappings for a team, paginated and filtered by the date. | Not stated |
| POST | /v2/groups | Create a group, Creates a group. | Not stated |
| DELETE | /v2/groups/:id | Deletes a Group by ID | Not stated |
| GET | /v2/groups | List groups, Fetches multiple group records. The records can be filtered, and sorted according to the respective parameters. | Not stated |
| GET | /v2/groups/:id | Fetch a group, Fetches a group, by ID only. | Not stated |
| PUT | /v2/groups/:id | Update a group, Updates a group by ID. | Not stated |
| POST | /v2/imports | Create an import, Creates an import. | Not stated |
| DELETE | /v2/imports/:id | Delete an import, Deletes an import, by ID only. The associated people can be deleted as part of the deletion process. | Not stated |
| GET | /v2/imports | List imports, Fetches multiple imports. | Not stated |
| GET | /v2/imports/:id | Fetch an import, Fetches an import, by ID only. | Not stated |
| PUT | /v2/imports/:id | Update an import, Updates an import, by ID only. | Not stated |
| POST | /v2/integrations/signals/registrations | Create a Signal Registration, Create a Signal Registration. | Not stated |
| DELETE | /v2/integrations/signals/registrations/:id | Deletes a Signal Registration, Deletes a Signal Registration For additional information on deleting a Signal Registration, visit the signals details page. Please note that Signal Registrations that are globally install can not be | Not stated |
| GET | /v2/integrations/signals/registrations | List Signal Registrations, List all Signal Registrations for all Integrations. | Not stated |
| POST | /v2/integrations/signals/registrations/plays | Create a Play Registration, Create a Salesloft Play for a registered Signal and coinciding indicator. Plays are rulesets that turn Salesloft Signals into action when certain criteria are met. A Play cannot be registered without | Not stated |
| DELETE | /v2/integrations/signals/registrations/plays/:id | Delete a Play Registration, Deletes a Play Registration. Please note that Play Registrations which have been enabled can not be deleted. | Not stated |
| GET | /v2/integrations/signals/registrations/plays | List Play Registrations, Fetches all Play Registrations created by owner of associated integration. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/integrations/signals/registrations/plays/:id | Fetch a Play Registration, Fetch a Play Registration by ID. Please note that deleted Play Registrations cannot be shown. | Not stated |
| PUT | /v2/integrations/signals/registrations/plays/:id | Update a Play Registration, Salesloft Plays are rulesets that turn Salesloft Signals into action if and when certain criteria are met - when indicator(s) of an incoming Signal match indicator(s) of a previously configured Play r | Not stated |
| GET | /v2/integrations/signals/registrations/:id | Fetch a Signal Registration, Fetch a Signal Registration by ID. | Not stated |
| PUT | /v2/integrations/signals/registrations/:id | Update a Signal Registration, Update a Signal Registration. | Not stated |
| POST | /v2/live_website_tracking_parameters | Create an Live Website Tracking Parameter, Creates a Live Website Tracking parameter to identify a person | Not stated |
| GET | /v2/me | Fetch current user, Authenticated user information. This endpoint does not accept any parameters as it is represents your authenticated user. The "Users" resource provides user information for other users on the team. | Not stated |
| GET | /v2/meetings | List meetings, Fetches multiple meeting records. The records can be filtered, paged, and sorted according to the respective parameters. Meetings resource is responsible for events created via the Salesloft platform | Not stated |
| GET | /v2/meetings/reschedule_links/:id | Fetch a reschedule meeting link, Fetches a reschedule meeting link using the 'reschedule_guid' as a parameter in the URL path. For example, 'meetings/reschedule_links/a27659c0-058c-4732-928d-c3ad67670a99'. | Not stated |
| POST | /v2/meetings/settings/searches | List meeting settings, Fetches multiple meeting setting records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| PUT | /v2/meetings/settings/:id | Update a meeting setting, Updates a meeting setting, by ID only. | Not stated |
| PUT | /v2/meetings/:id | Update a meeting, Updates a meeting, by ID only. | Not stated |
| GET | /v2/mime_email_payloads/:id | Fetch the MIME content for email, Fetch the MIME content for email. | Not stated |
| POST | /v2/notes | Create a note, +1 (770) 756-8022 | Not stated |
| DELETE | /v2/notes/:id | Delete a note, Deletes a note owned by authorized account. This operation is not reversible without contacting support. This operation can be called multiple times successfully. | Not stated |
| GET | /v2/notes | List notes, Fetches multiple note records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/notes/:id | Fetch a note, Fetches a note, by ID only. | Not stated |
| PUT | /v2/notes/:id | Update a note, Updates a note. Any changes to the note or associated records will not reflect in your CRM. | Not stated |
| POST | /v2/ongoing_actions | Create an ongoing action, Creates an ongoing action. An ongoing action is an action that is not yet completed, but progress has been made towards the completion. The user should not need to do anything for an ongoing action to | Not stated |
| GET | /v2/opportunities | List opportunities, Lists multiple Opportunity records. Returns Opportunity records synced from the CRM and created via API. The records can be filtered, paged, and sorted using the parameters below and external ID param | Not stated |
| GET | /v2/opportunities/:id | Fetch an Opportunity, Fetches a single Opportunity record. Returns Opportunity records synced from the CRM and created via API. To Create, Update and Delete opportunities, refer to this External Mapping guide here. | Not stated |
| POST | /v2/opportunity_people | Create an Opportunity and Person Association, Associates Salesloft people with opportunities. Use this endpoint to associate members of a buying group with opportunities. | Not stated |
| DELETE | /v2/opportunity_people/:id | Delete an Opportunity and Person Association, Deletes an Opportunity and Person Association. | Not stated |
| GET | /v2/opportunity_people | List Opportunity and Person Associations, Lists associations between Salesloft people and opportunities that have been created by Salesloft or created via API. | Not stated |
| POST | /v2/opportunity_stages | Create an Opportunity Stage, Creates an Opportunity Stage. Opportunities cannot be created without valid stages. | Not stated |
| DELETE | /v2/opportunity_stages/:id | Delete an Opportunity Stage, Deletes an Opportunity Stage | Not stated |
| GET | /v2/opportunity_stages | List Opportunity Stages, Lists Opportunity Stages synced from the CRM and created via API. The records can be filtered, paged, and sorted using the parameters below. | Not stated |
| GET | /v2/opportunity_stages/:id | Fetch an Opportunity Stage, Fetches a single Opportunity Stage. | Not stated |
| PUT | /v2/opportunity_stages/:id | Update an Opportunity Stage, Updates an Opportunity Stage. | Not stated |
| GET | /v2/pending_emails | List pending emails, Fetches a list of emails ready to be sent by an external email service. Only emails sent with an External Email Client will appear here. | Not stated |
| PUT | /v2/pending_emails/:id | Update a pending email, Updates the status of an email sent by an External Email Client. Does not affect lofted emails. | Not stated |
| POST | /v2/people | Create a person, Creates a person. Either email_address or phone/last_name must be provided as a unique lookup on the team. | Not stated |
| DELETE | /v2/people/:id | Delete a person, Deletes a person. This operation is not reversible without contacting support. This operation can be called multiple times successfully. | Not stated |
| GET | /v2/people | List people, Fetches multiple person records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/people/:id | Fetch a person, Fetches a person, by ID only. | Not stated |
| PUT | /v2/people/:id | Update a person, Updates a person. | Not stated |
| POST | /v2/person_stages | Create a person stage, Creates a person stage. | Not stated |
| DELETE | /v2/person_stages/:id | Delete an person stage, Deletes a person stage. This operation is not reversible without contacting support. This operation can be called multiple times successfully. | Not stated |
| GET | /v2/person_stages | List person stages, Fetches multiple person stage records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/person_stages/:id | Fetch a person stage, Fetches a person stage, by ID only. | Not stated |
| PUT | /v2/person_stages/:id | Update a person stage, Updates a person stage. | Not stated |
| POST | /v2/person_upserts | Upsert a person, Upserts a person record. The upsert_key dictates how the upsert will be performed. The create and update behavior is exactly the same as the individual create and update endpoints. | Not stated |
| GET | /v2/phone_number_assignments | List phone number assignments, Fetches multiple phone number assignment records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/phone_number_assignments/:id | Fetch a phone number assignment, Fetches a phone number assignment, by ID only. | Not stated |
| GET | /v2/phone_numbers/caller_ids | List caller ids, Each entry is a possible caller ID match for the number. Multiple entries may be returned if the phone number is present on more than one person in the system. Phone number should be in E.164 format. | Not stated |
| GET | /v2/phone_numbers/recording_settings/:id | Fetch recording setting, Fetches the recording status for a given phone number, based on Do Not Record and Recording Governance for your team. Phone number should be in E.164 format. | Not stated |
| POST | /v2/saved_list_views | Create a saved list view, Creates a saved list view. | Not stated |
| DELETE | /v2/saved_list_views/:id | Delete a saved list view, Deletes a saved list view. This operation is not reversible without contacting support. This operation can be called multiple times successfully. | Not stated |
| GET | /v2/saved_list_views | List saved list views, Fetches multiple saved list view records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/saved_list_views/:id | Fetch a saved list view, Fetches a saved list view, by ID only. | Not stated |
| PUT | /v2/saved_list_views/:id | Update a saved list view, Updates a saved list view. | Not stated |
| POST | /v2/signals | Create a Signal, Deliver a Signal to Salesloft. Signals must follow the structure defined on the Signal Registration. | Not stated |
| GET | /v2/steps | List steps, Fetches multiple step records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/steps/:id | Fetch a step, Fetches a step, by ID only. | Not stated |
| GET | /v2/successes | List successes, Fetches multiple success records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/tags | List team tags, Fetches a list of the tags used for a team. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/tasks/counts | Fetch task counts, Fetches task counts data grouped by the task type. | Not stated |
| POST | /v2/tasks | Create a Task, +1 (770) 756-8022 | Not stated |
| DELETE | /v2/tasks/:id | Delete a task, Deletes a task. This operation is not reversible without contacting support. | Not stated |
| GET | /v2/tasks | List tasks, Fetches multiple task records. The records can be filtered, paged, and sorted according to the respective parameters. Tasks associated with cadence steps will not be returned in the response. | Not stated |
| GET | /v2/tasks/:id | Fetch a task, Fetches a task, by ID only. | Not stated |
| PUT | /v2/tasks/:id | Update a Task, +1 (770) 756-8022 | Not stated |
| GET | /v2/team | Fetch current team, Fetches the team of the authenticated user. | Not stated |
| GET | /v2/team_template_attachments | List team template attachments, Fetches multiple team template attachment records. The records can be filtered and paged according to the respective parameters. | Not stated |
| POST | /v2/team_templates | Create Team Email Template, Create a new team email template | Not stated |
| GET | /v2/team_templates | List team templates, Fetches multiple team template records. The records can be filtered, paged, and sorted according to the respective parameters. | Not stated |
| GET | /v2/team_templates/:id | Fetch a team template, Fetches a team template, by ID only. | Not stated |
| PUT | /v2/team_templates/:id | Update Team Email Template, Update a team email template | Not stated |
| POST | /v2/third_party_live_feed_items | Create a live feed item, Creates a live feed item that can be sent to users. May only be used by whitelisted Frontend Integrations with notifications:write, people:read, and accounts:read scopes. Reference the Salesloft | Not stated |
| GET | /v2/users | List users, Non Admin: Lists only your user, or all on team depending on group visibility policy Team Admin: Lists users associated with your team | Not stated |
| GET | /v2/users/:id | Fetch a user, by User ID or User GUID, +1 (770) 756-8022 | Not stated |
| PUT | /v2/users/:id | Update a user, by User ID or User GUID, +1 (770) 756-8022 | Not stated |
| POST | /v2/webhook_subscriptions | Create a webhook subscription, Creates a webhook subscription. Visit the webhooks page for additional details and a list of available webhooks. Request must be made with a valid Oauth token or API key. Scope requirements for this e | Not stated |
| DELETE | /v2/webhook_subscriptions/:id | Delete a webhook subscription, Deletes a webhook subscription. This operation is not reversible without contacting support. This operation can be called multiple times successfully. | Not stated |
| GET | /v2/webhook_subscriptions | List webhook subscriptions, Fetches all of the customer's webhook subscriptions for your application. | Not stated |
| GET | /v2/webhook_subscriptions/:id | Fetch a webhook subscription, Fetches a webhook subscription, by ID only. | Not stated |
| PUT | /v2/webhook_subscriptions/:id | Update a webhook subscription, Updates a webhook subscription. Request must be made with a valid Oauth token or API key. | Not stated |
No endpoint matches that filter.
