Views
Views are composed of columns and pseudo columns. Views are similar to tables in the way that data is represented; however, views do not support updates. Entities that are represented as views are typically read-only entities. Often, a stored procedure is available to update the data if such functionality is applicable to the data source.
Queries can be executed against a view as if it were a normal table, and the data that comes back is similar in that regard.
Dynamic views, such as queries exposed as views, and views for looking up specific combinations of project_team work items are supported.
Adapter Views
| Name | Description |
| AccountStages | Returns multiple account stage records. The records can be filtered, paged, and sorted according to the respective parameters. |
| AccountTiers | Returns multiple account tier records. The records can be filtered, paged, and sorted according to the respective parameters. |
| ActionDetails | Returns multiple call instruction records. The records can be filtered, paged, and sorted according to the respective parameters. |
| Actions | Returns 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. Additionally, an admin may use the user_guid parameter to request actions that belong to specific users on the team. |
| CadenceMemberships | Returns 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. |
| Cadences | Returns multiple cadence records. The records can be filtered, paged, and sorted according to the respective parameters. |
| CallDataRecords | Returns 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 | Returns 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 | Returns each entry that 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 | Returns multiple call records. The records can be filtered, paged, and sorted according to the respective parameters. |
| CallSentiments | Returns 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. |
| CRMActivities | Returns multiple crm activity records. The records can be filtered, paged, and sorted according to the respective parameters. |
| CRMActivityFields | Returns multiple crm activity field records. The records can be filtered, paged, and sorted according to the respective parameters. |
| CRMUsers | Returns multiple crm user records. |
| Emails | Returns multiple email records. The records can be filtered, paged, and sorted according to the respective parameters. |
| EmailTemplateAttachments | Returns multiple email template attachment records. The records can be filtered and paged according to the respective parameters. |
| EmailTemplates | Returns multiple email template records. The records can be filtered, paged, and sorted according to the respective parameters. |
| Groups | Returns multiple group records. The records can be filtered, and sorted according to the respective parameters. |
| MIMEEmailPayloads | Returns the MIME content for email. |
| Notes | Returns multiple note records. The records can be filtered, paged, and sorted according to the respective parameters. |
| PersonStages | Returns multiple person stage records. The records can be filtered, paged, and sorted according to the respective parameters. |
| Steps | Returns multiple step records. The records can be filtered, paged, and sorted according to the respective parameters. |
| Successes | Returns multiple success records. The records can be filtered, paged, and sorted according to the respective parameters. |
| Tags | 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 multiple resource types. |
| Team | Returns the team of the authenticated user. |
| TeamTemplateAttachments | Returns multiple team template attachment records. The records can be filtered and paged according to the respective parameters. |
| TeamTemplates | 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 | Returns Non Admin: Lists only your user, or all on team depending on group visibility policy Team Admin: Lists users associated with your team. |