SalesLoft

This documentation for the SalesLoft integration describes the technical capabilities of this integration, including authorization, scopes/permissions, and utilized endpoints. For more information on how to integrate SalesLoft, visit our connection instructions.

Version

This integration utilizes the SalesLoft API v2.

Base URL

The base URL used for all SalesLoft API endpoints:

https://api.salesloft.com/v2

---

Authentication & Authorization

The DataGrail SalesLoft integration connects using OAuth 2.0 with the following credentials: Client ID and Client Secret.

Sensitive Credentials

Publicly exposing your API credentials can allow unauthorized access to SalesLoft API endpoints by a third party. DataGrail stores your API credentials encrypted and protected.

Endpoints Utilized

DataGrail uses the following endpoints to authorize and test the connection:

Method	Endpoint	Purpose	Docs
POST	/me.json	Verify connection
GET	https://accounts.salesloft.com/oauth/authorize	Request authorization
POST	https://accounts.salesloft.com/oauth/token	Get and refresh access token

---

Limits

Limits in SalesLoft are calculated using the leaky bucket algorithm. All requests that are made after rate limits have been exceeded are throttled and an HTTP 429 Too Many Requests error is returned. Requests succeed again after enough requests have emptied out of the bucket.

• DataGrail supports requests throttling to stay within 70-80% of specified service rate limits.
• DataGrail processes API responses with HTTP 429 status to interrupt requests, waiting and retrying (using an exponential backoff strategy).

---

Capabilities

Access

DataGrail's SalesLoft integration provides Synchronous Access capabilities for the following supported identifier category: Email.

Data Interactions

For Access requests, DataGrail will take the following actions:

1. Search for people using the Data Subject Email.
2. Fetch additional associations by URLs extracted from details of the collected people, such as accounts, users.
3. Fetch cadence memberships linked to the collected persons by the person_id.
4. Fetch notes associated with the collected persons by the person_id.
5. Fetch calls and select objects if called_person matches one of the collected persons.
6. Fetch CRM activities using URLs extracted from the collected call details, if present.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
GET	/accounts/id.json	Fetches an account, by ID only
GET	/activities/calls.json	Fetches multiple call records
GET	/cadence_memberships.json	Fetches multiple cadence membership records
GET	/crm_activities/id.json	Fetches multiple crm activity records
GET	/notes.json	Fetches multiple note records
GET	/people.json	Fetches multiple person records
GET	/users/id.json	Fetches a user

---

Deletion

DataGrail's SalesLoft integration provides Synchronous Deletion capabilities for the following supported identifier category: Email.

Data Interactions

For Deletion requests, DataGrail will take the following actions:

1. Search for people using the Data Subject Email.
2. Delete detected persons.
3. Fetch cadence memberships linked to the collected persons by the person_id.
4. Delete detected cadence memberships.
5. Fetch notes associated with the collected persons by the person_id.
6. Delete detected notes.

Endpoints Utilized

Method	Endpoint	Purpose	Docs
GET	/cadence_memberships.json	Fetches multiple cadence membership records
DEL	/cadence_memberships/cadence_id.json	Delete a cadence membership
GET	/notes.json	Fetches multiple note records
DEL	/notes/note_id.json	Delete a note
GET	/people.json	Fetches multiple person records
DEL	/people/person_id.json	Deletes a person

---