Account managed-by updated
The entity managing this account on its behalf changed.
Recipients: SELF. Delivery: POST to your registered URL; respond 2xx within 10s. Non-2xx or timeout is retried 10 times over ~3 days (1m, 5m, 30m, 2h, 6h, 12h, then daily); 4xx other than 408/429 is terminal. Wink-Event-Id is your idempotency key.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Header Parameters
Section titled “Header Parameters”Example
t=1755000000,v1=5d41402abc4b2a76b9719d911017c592...Signature over t + "." + rawBody. See the security scheme.
Example
0198a4f2-6b0e-7c1d-9a3e-2f4b8c6d1e0aEvent identifier — identical for every endpoint of this recipient and every retry.
Example
0198a4f2-6b0f-7d2e-8b4f-3a5c9d7e2f1bDelivery identifier — unique per subscription endpoint.
Example
managing_entity.managed_by.updatedEvent type key (same as type in the body).
Example
11-based attempt number.
Example
2.0Wire contract version.
Request Bodyrequired
Section titled “Request Bodyrequired”object
Unique event identifier. Identical for every endpoint of this recipient and every retry; use it as your idempotency key.
Example
b7e4c1a2-3f5d-4e8a-9c21-6f0b5d8e3a47The event payload. Its schema depends on type; every payload carries links.self.
When the event happened on the platform (UTC).
Example
2026-08-15T09:30:00ZThe managing entity this delivery is addressed to.
Example
d5b8a3c2-9e6f-4a1b-8d34-7c2e1f0a5b69Why the addressed managing entity receives this event.
Example
SUPPLIERVersion of the payload contract (the shape of object). Currently 2.
Example
2Event type key, e.g. booking.create. The list of keys is documented under Webhooks.
Example
booking.createSummary of a managing entity (account).
object
Country of the business address, ISO-3166 alpha-2.
Last change to the record.
Links to fetch the full resource this event is about. self is the SUPPLIER-side canonical resource URL (/api/managing-entity/{hotel}/extranet/…). AFFILIATE and AGENT recipients cannot call it — use your own reseller/agent endpoints for the same resource id.
object
Absolute URL of the resource, on the SUPPLIER-side canonical path (/api/managing-entity/{hotel}/extranet/…). If you receive this event as an AFFILIATE or AGENT rather than the supplier, call your own reseller/agent endpoint for the same resource id instead — the REST ACL applies either way.
Example
https://api.wink.travel/api/managing-entity/3c6b1a5d-8e2f-4a0b-9c7d-6e4f0a8b2c51/extranet/booking/9c7d6e4f-0a8b-2c51-3c6b-1a5d8e2f4a0bManaging entity identifier.
Display name.
Platform status.
Entity type (HOTEL, TRAVEL_AGENT, …).
URL-friendly slug.
Responses
Section titled “Responses”Acknowledged. Any 2xx marks the delivery SUCCEEDED.
Rejected. Terminal (no retry) except 408 and 429, which are retried.
Failed. Retried per the schedule above.
