Actions389
- Contract Actions
- Ticket History Actions
- Ticket Note Webhook Actions
- Ticket Note Actions
- Ticket Webhook Actions
- Time Entry Actions
- Resource Actions
- Role Actions
- Resource Role Actions
- Search Filter Actions
- Service Actions
- Skill Actions
- Service Call Actions
- Survey Results Actions
- Survey Actions
- Ticket Actions
- Opportunity Actions
- Notification History Actions
- Invoice Actions
- Product Actions
- Product Vendor Actions
- Project Actions
- Project Charge Actions
- Project Phase Actions
- Project Task Actions
- Project Note Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Service Bundle Adjustment Actions
- Contract Ticket Purchase Actions
- Contract Service Unit Actions
- Domain Registrar Actions
- Holiday Actions
- Holiday Set Actions
- Contract Exclusion Billing Code Actions
- Contract Rate Actions
- Contract Exclusion Role Actions
- Contract Exclusion Sets Actions
- Contract Exclusion Set Excluded Role Actions
- Contract Exclusion Set Excluded Work Type Actions
- Contract Milestone Actions
- Contract Note Actions
- Contract Role Costs Actions
- Contact Groups Actions
- Contact Actions
- Contact Webhook Actions
- Contact Group Contacts Actions
- Contract Block Hour Factor Actions
- Contract Block Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Configuration Item Category Actions
- Configuration Item Category UDF Association Actions
- Configuration Item DNS Record Actions
- Configuration Item Note Actions
- Configuration Item Related Item Actions
- Configuration Item SSL Subject Alternative Name Actions
- Configuration Item Type Actions
- Configuration Item Webhook Actions
- Company Alert Actions
- Company Actions
- Billing Code Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Configuration Item Actions
- Configuration Item Billing Product Association Actions
Overview
The 'Service Call' resource with the 'Get Many' operation allows users to retrieve multiple service call records from the Autotask system. This operation is useful for scenarios where bulk data retrieval is needed, such as generating reports, syncing service call data with other systems, or analyzing service call trends. For example, a user might fetch all service calls within a date range or retrieve a limited number of recent service calls for dashboard display.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the service call records to retrieve and map in the output. Supports custom mapping and selection of specific fields. |
| Get All | Determines whether to return all matching service call records or limit the number of records returned. |
| Max Records | Specifies the maximum number of service call records to return when 'Get All' is false. Value range is 1 to 500. |
| Add Picklist Labels | If enabled, adds additional fields with human-readable labels for picklist fields in the service call data. |
| Add Reference Labels | If enabled, adds additional fields with human-readable labels for reference fields in the service call data. |
| Select Columns Names or IDs. | Allows selection of specific fields (columns) to include in the response. If none selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are promoted to top-level properties in each service call object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the service call record
- Requested service call fields as specified in the 'Fields' property_label - Human-readable labels for picklist or reference fields if enableduserDefinedFields- User-defined fields nested or flattened depending on 'Flatten User-Defined Fields' setting
Dependencies
- Requires an authenticated connection to the Autotask REST API via an API key credential.
Troubleshooting
- If no records are returned, verify that the query parameters and field mappings are correct and that the Autotask account has service call data available.
- Errors related to authentication indicate issues with the API key credential; ensure it is valid and has necessary permissions.
- Selecting too many fields or requesting all records without limits may cause performance issues or timeouts; consider limiting the number of records or fields.
- If picklist or reference labels are not appearing, check that the corresponding options ('Add Picklist Labels' and 'Add Reference Labels') are enabled.