integrations.sh
← all integrations

SalesLoft Platform

OpenAPI apis-guru customer_relation

SalesLoft helps transform sales teams into modern sales organizations - converting more target accounts into customer accounts

Homepage
https://api.apis.guru/v2/specs/salesloft.com/v2.json
Provider
salesloft.com
OpenAPI version
2.0
Spec (JSON)
https://api.apis.guru/v2/specs/salesloft.com/v2/openapi.json
Spec (YAML)
https://api.apis.guru/v2/specs/salesloft.com/v2/openapi.yaml

Tools (120)

Extracted live via the executor SDK.

  • accounts.deleteV2AccountsIdJson

    Deletes an account. This operation is not reversible without contacting support. This operation can be called multiple times successfully.

    Deleting an account will remove all connected people from that account.

  • accounts.getV2AccountsIdJson

    Fetches an account, by ID only.

  • accounts.getV2AccountsJson

    Fetches multiple account records. The records can be filtered, paged, and sorted according to the respective parameters.

  • accounts.postV2AccountsJson

    Creates an account.

    "domain" must be unique on the current team.

  • accounts.putV2AccountsIdJson

    Updates an account.

    "domain" must be unique on the current team.

  • accountStages.getV2AccountStagesIdJson

    Fetches an account stage, by ID only.

  • accountStages.getV2AccountStagesJson

    Fetches multiple account stage records. The records can be filtered, paged, and sorted according to the respective parameters.

  • accountTiers.getV2AccountTiersIdJson

    Fetches an account tier, by ID only.

  • accountTiers.getV2AccountTiersJson

    Fetches multiple account tier records. The records can be filtered, paged, and sorted according to the respective parameters.

  • accountUpsert.postV2AccountUpsertsJson

    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.

  • actionDetailsCallInstructions.getV2ActionDetailsCallInstructionsIdJson

    Fetches a call instruction, by ID only.

  • actionDetailsCallInstructions.getV2ActionDetailsCallInstructionsJson

    Fetches multiple call instruction records. The records can be filtered, paged, and sorted according to the respective parameters.

  • actions.getV2ActionsIdJson

    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.

  • actions.getV2ActionsJson

    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.

    If the requester is not an admin, this endpoint will only return actions belonging to the requester. If the request is an admin, this endpoint will return actions for the entire team. Additionaly, an admin may use the user_guid parameter to request actions that belong to specific users on the team.

  • activities.postV2ActivitiesJson

    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.

  • activityHistories.getV2ActivityHistories

    Fetches all of the customer's past activities for your application. Returns all the Activities that are found on the Salesloft Activity Feed. .

  • bulkJobs.getV2BulkJobs

    Fetches multiple bulk job records. The records can be filtered, paged, and sorted according to the respective parameters.

  • bulkJobs.getV2BulkJobsId

    Fetches a bulk job, by ID only.

  • bulkJobs.postV2BulkJobs

    Creates a bulk job. The type of the bulk job must be included when created.

    For additional information on creating bulk jobs, the types of supported bulk jobs, and examples of the bulk job flow, visit the .

  • bulkJobs.putV2BulkJobsId

    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.

    For additional information on creating bulk jobs, the types of supported bulk jobs, and examples of the bulk job flow, visit the .

  • bulkJobsJobData.getV2BulkJobsBulkJobsIdJobData

    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 the next batch of records.

  • bulkJobsJobData.postV2BulkJobsBulkJobsIdJobData

    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,000 records at a time. There is no limit to how many times you can create job data for a given bulk job.

    For additional information on creating bulk jobs, the types of supported bulk jobs, and examples of the bulk job flow, visit the .

  • bulkJobsResults.getV2BulkJobsBulkJobsIdResults

    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 polling is via use of the id[gt] filter. Pass the last id seen (i.e. id[gt]=1234) in order to get the next batch of records.

  • cadenceExports.getV2CadenceExportsIdJson

    Exports a cadence as JSON.

  • cadenceImports.postV2CadenceImportsJson

    New cadences can be created or steps can be imported onto existing cadences which do not have steps. .

  • cadenceMemberships.deleteV2CadenceMembershipsIdJson

    Cadence Membership

  • cadenceMemberships.getV2CadenceMembershipsIdJson

    Fetches a cadence membership, by ID only.

  • cadenceMemberships.getV2CadenceMembershipsJson

    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 current and historical time on a cadence. Cadence membership records are mutable and change over time. If a person is added to a cadence and re-added to the same cadence in the future, there is a single membership record.

  • cadenceMemberships.postV2CadenceMembershipsJson

    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 the authenticated team.

    A person cannot be added to a cadence on behalf of a teammate unless the cadence is a team cadence, the cadence is owned by the teammate, or the teammate has the Personal Cadence Admin permission.

  • cadences.getV2CadencesIdJson

    Fetches a cadence, by ID only.

  • cadences.getV2CadencesJson

    Fetches multiple cadence records. The records can be filtered, paged, and sorted according to the respective parameters.

  • calendarEvents.getV2CalendarEvents

    Returns all calendar events, paginated and filtered by the date.

  • calendarEvents.postV2CalendarEventsUpsert

    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 for integration instructions. Use calendar/events/upsert as an event type, and this spec as a data spec. This endpoint should be used directly for the time sensitive calendar event updates.

  • callDataRecords.getV2CallDataRecordsIdJson

    Fetches a call data record, by ID only.

  • callDataRecords.getV2CallDataRecordsJson

    Fetches multiple call data records. The records can be filtered, paged, and sorted according to the respective parameters.

    Call data records are records of all inbound and outbound calls through Salesloft. A call data record may be associated with a call, but does not have to be.

  • callDispositions.getV2CallDispositionsJson

    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 please contact us if you have a pressing use case.

  • callerIDs.getV2PhoneNumbersCallerIdsJson

    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.

  • calls.getV2ActivitiesCallsIdJson

    Fetches a call, by ID only.

  • calls.getV2ActivitiesCallsJson

    Fetches multiple call records. The records can be filtered, paged, and sorted according to the respective parameters.

  • calls.postV2ActivitiesCallsJson

    Creates a call. The parameters of this endpoint can be used to create an action and ensure that the CRM Task is mapped correctly.

  • callSentiments.getV2CallSentimentsJson

    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 contact us if you have a pressing use case.

  • conversationsCalls.postV2ConversationsCalls

    Enqueue a Conversations Call for processing

  • crmActivities.getV2CrmActivitiesIdJson

    Fetches a crm activity, by ID only.

  • crmActivities.getV2CrmActivitiesJson

    Fetches multiple crm activity records. The records can be filtered, paged, and sorted according to the respective parameters.

  • crmActivityFields.getV2CrmActivityFieldsJson

    Fetches multiple crm activity field records. The records can be filtered, paged, and sorted according to the respective parameters.

  • crmUsers.getV2CrmUsersJson

    Crm Users

  • customFields.deleteV2CustomFieldsIdJson

    Deletes a custom field.

  • customFields.getV2CustomFieldsIdJson

    Fetches a custom field, by ID only.

  • customFields.getV2CustomFieldsJson

    Fetches multiple custom field records. The records can be filtered, paged, and sorted according to the respective parameters.

  • customFields.postV2CustomFieldsJson

    Creates a custom field.

  • customFields.putV2CustomFieldsIdJson

    Update a custom field.

  • emails.getV2ActivitiesEmailsIdJson

    Fetches an email, by ID only.

  • emails.getV2ActivitiesEmailsJson

    Fetches multiple email records. The records can be filtered, paged, and sorted according to the respective parameters.

  • emailTemplateAttachments.getV2EmailTemplateAttachmentsJson

    Fetches multiple email template attachment records. The records can be filtered and paged according to the respective parameters.

  • emailTemplates.getV2EmailTemplatesIdJson

    Fetches an email template, by ID only.

  • emailTemplates.getV2EmailTemplatesJson

    Fetches multiple email template records. The records can be filtered, paged, and sorted according to the respective parameters.

  • externalEmails.postV2ExternalEmailsJson

    Creates an external email object.

  • groups.getV2GroupsIdJson

    Fetches a group, by ID only.

  • groups.getV2GroupsJson

    Fetches multiple group records. The records can be filtered, and sorted according to the respective parameters.

  • imports.deleteV2ImportsIdJson

    Deletes an import, by ID only. The associated people can be deleted as part of the deletion process.

    Admin users can access imports for the entire team, but non-admin users can only access their own imports.

  • imports.getV2ImportsIdJson

    Fetches an import, by ID only.

    Admin users can access imports for the entire team, but non-admin users can only access their own imports.

  • imports.getV2ImportsJson

    Fetches multiple imports.

  • imports.postV2ImportsJson

    Creates an import.

  • imports.putV2ImportsIdJson

    Updates an import, by ID only.

    Admin users can access imports for the entire team, but non-admin users can only access their own imports.

  • liveFeedItems.postV2ThirdPartyLiveFeedItems

    Creates a live feed item that can be sent to users. May only be used by whitelisted Frontend Integrations. Reference the Salesloft App Directory and Frontend Integrations sections for additional details.

  • liveWebsiteTrackingParameters.postV2LiveWebsiteTrackingParametersJson

    Creates a Live Website Tracking parameter to identify a person

  • me.getV2MeJson

    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.

  • meetings.getV2MeetingsJson

    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 using calendaring features. These events can relate to cadences, people, and accounts.

  • meetings.putV2MeetingsIdJson

    Updates a meeting, by ID only.

  • meetingSettings.putV2MeetingsSettingsIdJson

    Updates a meeting setting, by ID only.

  • meetingsSettingsSearches.postV2MeetingsSettingsSearchesJson

    Fetches multiple meeting setting records. The records can be filtered, paged, and sorted according to the respective parameters.

  • mimeEmailPayloads.getV2MimeEmailPayloadsIdJson

    Fetch the MIME content for email.

  • notes.deleteV2NotesIdJson

    Deletes a note owned by authorized account. This operation is not reversible without contacting support. This operation can be called multiple times successfully.

  • notes.getV2NotesIdJson

    Fetches a note, by ID only.

  • notes.getV2NotesJson

    Fetches multiple note records. The records can be filtered, paged, and sorted according to the respective parameters.

  • notes.postV2NotesJson

    Creates a note.

  • notes.putV2NotesIdJson

    Updates a note. Any changes to the note or associated records will not reflect in your CRM.

  • ongoingActions.postV2OngoingActionsJson

    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 be completed. An ongoing action can be later completed by creating an activity.

    Ongoing actions are marked as status=pending_activity.

  • pendingEmails.getV2PendingEmailsJson

    Fetches a list of emails ready to be sent by an external email service.

  • pendingEmails.putV2PendingEmailsIdJson

    Updates the status of an email sent by an External Email Client. Does not affect lofted emails.

  • people.deleteV2PeopleIdJson

    Deletes a person. This operation is not reversible without contacting support. This operation can be called multiple times successfully.

  • people.getV2PeopleIdJson

    Fetches a person, by ID only.

  • people.getV2PeopleJson

    Fetches multiple person records. The records can be filtered, paged, and sorted according to the respective parameters.

  • people.postV2PeopleJson

    Creates a person. Either email_address or phone/last_name must be provided as a unique lookup on the team.

  • people.putV2PeopleIdJson

    Updates a person.

  • personStages.deleteV2PersonStagesIdJson

    Deletes a person stage. This operation is not reversible without contacting support. This operation can be called multiple times successfully.

  • personStages.getV2PersonStagesIdJson

    Fetches a person stage, by ID only.

  • personStages.getV2PersonStagesJson

    Fetches multiple person stage records. The records can be filtered, paged, and sorted according to the respective parameters.

  • personStages.postV2PersonStagesJson

    Creates a person stage.

  • personStages.putV2PersonStagesIdJson

    Updates a person stage.

  • personUpsert.postV2PersonUpsertsJson

    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.

  • phoneNumberAssignments.getV2PhoneNumberAssignmentsIdJson

    Fetches a phone number assignment, by ID only.

  • phoneNumberAssignments.getV2PhoneNumberAssignmentsJson

    Fetches multiple phone number assignment records. The records can be filtered, paged, and sorted according to the respective parameters.

  • recordingSettings.getV2PhoneNumbersRecordingSettingsIdJson

    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.

  • savedListViews.deleteV2SavedListViewsIdJson

    Deletes a saved list view. This operation is not reversible without contacting support. This operation can be called multiple times successfully.

  • savedListViews.getV2SavedListViewsIdJson

    Fetches a saved list view, by ID only.

  • savedListViews.getV2SavedListViewsJson

    Fetches multiple saved list view records. The records can be filtered, paged, and sorted according to the respective parameters.

  • savedListViews.postV2SavedListViewsJson

    Creates a saved list view.

  • savedListViews.putV2SavedListViewsIdJson

    Updates a saved list view.

  • steps.getV2StepsIdJson

    Fetches a step, by ID only.

  • steps.getV2StepsJson

    Fetches multiple step records. The records can be filtered, paged, and sorted according to the respective parameters.

  • successes.getV2SuccessesJson

    Fetches multiple success records. The records can be filtered, paged, and sorted according to the respective parameters.

  • tags.getV2TagsJson

    Fetches a list of the tags used for a team. The records can be filtered, paged, and sorted according to the respective parameters.

    Tags can be applied to mulitple resource types.

  • tasks.getV2TasksIdJson

    Fetches a task, by ID only.

  • tasks.getV2TasksJson

    Fetches multiple task records. The records can be filtered, paged, and sorted according to the respective parameters.

  • tasks.postV2TasksJson

    Creates a task.

  • tasks.putV2TasksIdJson

    Updates a task.

  • team.getV2TeamJson

    Fetches the team of the authenticated user.

  • teamTemplateAttachments.getV2TeamTemplateAttachmentsJson

    Fetches multiple team template attachment records. The records can be filtered and paged according to the respective parameters.

  • teamTemplates.getV2TeamTemplatesIdJson

    Fetches a team template, by ID only.

  • teamTemplates.getV2TeamTemplatesJson

    Fetches multiple team template records. The records can be filtered, paged, and sorted according to the respective parameters.

    Team templates are templates that are available team-wide. Admins may use team templates to create original content for the entire team, monitor version control to ensure templates are always up to date, and track template performance across the entire organization. All metrics on a team template reflect usage across the team; individual metrics can be found with the email_templates API endpoint.

  • users.getV2UsersIdJson

    Fetches a user, by ID only.

  • users.getV2UsersJson

    Non Admin: Lists only your user, or all on team depending on group visibility policy Team Admin: Lists users associated with your team

  • webhookSubscriptions.deleteV2WebhookSubscriptionsId

    Deletes a webhook subscription. This operation is not reversible without contacting support. This operation can be called multiple times successfully.

  • webhookSubscriptions.getV2WebhookSubscriptions

    Fetches all of the customer's webhook subscriptions for your application.

  • webhookSubscriptions.getV2WebhookSubscriptionsId

    Fetches a webhook subscription, by ID only.

  • webhookSubscriptions.postV2WebhookSubscriptions

    Creates a webhook subscription. Visit the for additional details and a list of available webhooks. Request must be made with a valid Oauth token or API key.

  • webhookSubscriptions.putV2WebhookSubscriptionsId

    Updates a webhook subscription. Request must be made with a valid Oauth token or API key.

  • openapi.previewSpec

    Preview an OpenAPI document before adding it as a source

  • openapi.addSource

    Add an OpenAPI source and register its operations as tools