We now support filtering by custom_fields on the Accounts List (https://developers.salesloft.com/api.html#!/Accounts/get_v2_accounts_json) and People List (https://developers.salesloft.com/api.html#!/People/get_v2_people_json) endpoints. Please note that the custom field values are case insensitive, but the custom field names are case sensitive.

You can use these new filters by passing up query parameters in the form of custom_fields[YOUR_FIELD_NAME]=YOUR_VALUE.

We have added several new API improvements for the SalesLoft Dialer:

• Sort calls by created_at
• Retrieve the PhoneNumberAssignment for a user
• Link a Call and CallDataRecord when creating a Call
• Provide the status of the CallDataRecord (phone outcome)

Call Data Records have been updated to allow for created_at filtering, displaying the call status, and to create linked records when logging a call. This addition allows for full call logging parity with our application.

It is now possible to filter by crm_id on our account list and people list endpoints. You can issue a request for a single crm_id, or an array of them. In order to submit an array request, the format is crm_id[]=A&crm_id[]=B

It is now possible to view Tags in the SalesLoft API. You can get started at https://developers.salesloft.com/api.html#!/Tags/get_v2_tags_json.

Person objects have a new field "contact_restrictions". This field indicates whether the person should not be contacted over certain channels. The two channels that we support on this initial release are "email" and "call".

This can be a change for your app if you are filtering based on donotcontact, as it is possible for someone to not be contactable over a channel, but have donotcontact=false. New filters for whether the person can specifically be emailed or called will be coming soon.

Email templates can now be filtered using the "search" parameter. This parameter will do a case insensitive likeness filter on title/subject of the email template.

Notes can now be created on behalf of a user for any token associated with a team admin. This is accomplished by passing the user_guid parameter while creating the note. A created note without the user_guid parameter will default to the requesting user.

the embedded Recording resource will have a new field called recording_status will be included on the call resource having values of

not_recorded: there is no recording available, and there will not be one becoming available.

pending: the recording is queued to be processed 

processing: the recording is currently being processed by the system

completed: the recording processing has been completed

This list of values are non exhaustive and may be added to in the future, completed and not_recorded should be considered as final statuses for a call.

Here is an example response

"recording": {
    "url": "https://recordings.salesloft.com/example",
    "status": "completed",
    "recording_status": "completed"
},

SalesLoft OAuth Apps now require whitelisting approval before allowing teams to utilize the app. The creating team can use the app without approval, which will allow for development to occur. There is a topic available at https://developers.salesloft.com/api.html#!/Topic/Whitelisting.

2 new endpoints are added to allow for completion of actions: Activity#create and OngoingAction#create.

These endpoints allow for frontend integration actions to be completed via our API. It is not possible to complete other types of actions at this time.

This changelog will track additions to the SalesLoft API resources and the documentation over time.