...
- Webhooks are only available for applications with grant type client_credentials using an access of type "Agency Manager" (single agency access) and scope "api.profilesondemand.read".
- Notifications can not be tailored to include / exclude specific profiles. Notifications will be sent for all profiles within a travel agency.
- Notifications might be delivered, even if no actual profile data has been changed.
- The notification itself denotes a profile identifier and nothing more. Specifically, it does not contain any profile data or information on what may have changed within the profile.
Receiving Webhooks
TBD
Message authentication
Each webhook invocation will be TBD: Header HMAC-SHA256
Payload
| Code Block | ||
|---|---|---|
| ||
{
"profileType": "TRAVELLER",
"event": "UPDATE",
"uuid": "25b46ba4-0e9e-4baa-83bd-ac21a50ef998",
"company": {
"uuid": "34f277f5-2618-4c9e-aa08-affa9f02dfaa"
}
} |
| Field | Description |
|---|---|
| TBD | Timestamp in format "TBD" of when the event has originally happened |
| profileType | The profile type for which this notification is sent:
|
| event | The notification type:
|
| uuid | The Umbrella Faces UUID of the affected profile |
| company.uuid | For profileType TRAVELLER only: UUID of the company currently associated with the traveler profile. |
Message authentication
Each Webhook invocation will include the custom header "X-FacesWebhookSignature", which consist of the request body hashed using HMAC-SHA256 with the secret configured during Webhook setup in hex format.
Example: Using the above payload and secret S3cret! one would compute a hash value of TBD
Delivery
Payloads are delivered via HTTPS POST only. Each notification will be transmitted with an individual POST request without applying any batching logic.
...