Yes, you are able to book tee times in the Sandbox environment. Booked tee times will not be sent to course tee sheets and the payment information used will not be charged. By convention, only tee times where the time ends in a multiple of 10 can be booked (ie: 10:00, 10:10, 10:20, etc...). Other tee times will result in a tee time not found error when reserving the round.
This is an unfortunate implementation detail that is present due to the fact that the classes that implement that part of the contract make use of inheritance. This is how the client must specify to the API the type of object that should be created when deserializing the message.
An additional limitation is that the property must be the first property. If it is not, the deserializer will not know what properties to look for during deserialization.
Skip and take are paging parameters that let you retrieve the information returned by certain operations. Skip is the ordinal distance from the first item in the full result set. Take is the maximum number of items to be returned.
For example, using the set {A, B, C, D}
Expanded properties gives the API client the ability to load optional data that is not returned by default. User have the option to populate one or more expandable properties. If no value is specified then no expanded properties will be populated. The values of the "expand" parameter will vary depending on the operation being called and the return type supported. For details of expanded properties that are supported for each operation please refer to the documentation for the operation. To specify multiple expanded properties, use the pipe delimiter which has a url encoding of "%7c".
REST Call With One Expanded Property
GET /rest/customers/[email protected]?expand=LoyaltyStatus
REST Call With Two Expanded Properties
GET /rest/channel/1650/facilities/11107?expand=CourseStatistics%7cRatingSummary