ContractServiceBundleUnits

This entity describes the number of units of a specific service bundle that are associated with a Recurring Service contract for a specific date range. They provide information used in billing for the service bundle.

The start and end dates of the date range are determined by either the beginning or end date of a billing period (as specified by the Contract Billing Period type) or by an adjustment to the number of units of the service bundle. That is, each billing period generates one ContractServiceBundleUnit unless the number of service bundle units is adjusted within the billing period. When the number of ServiceBundle units for one ServiceBundle on a contract is adjusted, a new ContractServiceBundleUnit is created with a start date equal to the effective date of the adjustment. The end date for the ContractServiceBundleUnit will be the end date of the billing period in which the adjustment becomes effective or, if another adjustment is made in the same billing period, the effective date of that adjustment. Refer to About recurring service contract entity relationships.

BEFORE YOU BEGIN  It's important to understand how Recurring Service Contracts interact with Autotask and influence other entities. Before you use the API to create or manage this type of contract, we recommend that you read our Adding a recurring service contract article. Then, review the Conditions and requirements and Special field attributes sections of this article to get started.

NOTE  You can refer to the Online Help to find root and child access URLs of the entity you wish to query. Refer to Finding resource and child access URLs of REST API entities for more information.

Entity details

Entity Name: ContractServiceBundleUnits

Entity Path:

/atservicesrest/v1.0/ContractServiceBundleUnits

Parent Entity:

Contracts

Can Create:  
Can Update:  
Can Query:
Can Delete:  
Can Have UDFs:  

Conditions and requirements

  • Resources with security levels that specify limited or no contract visibility cannot create, update, or query this entity.
  • If the Multi-currency Installed Module is enabled, the following field will return the relevant Customer Currency values instead of the Internal Currency values: Price.
  • The following field will return the saved Internal Currency values: internalCurrencyPrice.

Special field attributes

Field Conditions and Requirements

cost

This entity field will return no information if the user account making the query does not have sufficient privileges to view cost data in the Autotask UI. Additionally, if an update request does not have the necessary permissions, the API will ignore the call's values for the field even if they are blank or would be otherwise required.

Field definitions

The following table describes the standard Autotask fields for this entity. Refer to the following articles for more information about working with these fields:

To learn how to query picklist endpoints, refer to Understanding picklists.

Notes

  • For string datatypes, the number in parentheses ( ) indicates the maximum number of characters allowed.
  • LT indicates Local Term.
  • If this entity has child collections, they will appear in a Child collection access URLs or an Entity URLs and relationships drop-down in the Entity details section of this article.
  • You can call the /query/count/ endpoint of a resource to determine how many records a collection holds.
Field Name Datatype Read-Only Is Required Reference Name Picklist
approveAndPostDate datetime      
contractID integer Contracts  
contractServiceBundleID integer     ContractServiceBundles  
cost decimal      
endDate datetime    
id integer    
internalCurrencyPrice (Multi-currency module only) decimal      

organizationalLevelAssociationID

integer

 

OrganizationalLevelAssociations

 
price decimal      
serviceBundleID integer ServiceBundles
startDate datetime    
units integer    

Additional resources