Destination
Get a single Client Destination by DestinationId
Both methods are valid and return the same result: a single Destination entity identified by its unique DestinationId. The path-style is more intuitive and commonly used in RESTful APIs. The function-style follows OData conventions and may be required in certain query contexts (e.g., when the key contains special characters or is not a simple numeric ID).
<b>Path-style access: </b>/odata/v1/Destination/{DestinationKey}
<b>Example: </b>/odata/v1/Destination/1301
<b>Function-style access: </b>/odata/v1/Destination({DestinationKey})
<b>Example: </b>/odata/v1/Destination(1301)
get/odata/v1/Destination/{DestinationKey}
Path parameters
DestinationKeystring required
Query parameters
$selectstring
Selects which properties to include in the response.
Response
OK (DDF.Core.Entities.Destination object)
Example response
{
"@odata.context": "https://localhost:7051/odata/v1/$metadata#DDF.Core.Entities.Destination"
}