X-Musement-Application header
To better analyze Musement API usage and identify areas of improvement, we have introduced the X-Musement-Application
header.
Partners will receive a unique Application value and are expected to include this value for all their API requests. If you currently do not have an Application value, you can request it at api-distribution@tui.com.
Consider the example request below for activities:
curl -X GET '{baseUrl}/activities' \
-H 'X-Musement-Version: 3.4.0' \
-H 'Authorization: Bearer {accessToken}'
Using the new X-Musement-Application
header, the request becomes:
curl -X GET '{baseUrl}/activities' \
-H 'X-Musement-Application: {applicationValue}' \
-H 'X-Musement-Version: 3.4.0' \
-H 'Authorization: Bearer {accessToken}'
The header will also be expected for authentication requests:
curl -X POST '{baseUrl}/login' \
-H 'X-Musement-Application: {applicationValue}' \
-H 'X-Musement-Version: 3.4.0' \
-H 'Content-Type: application/json' \
--data-raw '{
"client_id": "{clientId}",
"client_secret": "{clientSecret}",
"grant_type": "{clientCredentials}"
}'
This header is currently optional but there are plans to make it mandatory by the end of June 2022. Partners with existing integrations are expected to add this header as soon as possible.