Expedia Group Deposit API is one of 15 APIs that Expedia Group publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Deposit. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes
3 operations
across 1 path,
and defines 11 schemas.
It is described by OpenAPI 3.0.1, at version 1.0.
Requests are made against a single base URL, https://services.expediapartnercentral.com/.
3 operations1 paths11 schemas1 DELETE1 GET1 PUT
Metadata
The identity and technical contract details declared by the specification.
Expedia Group Deposit API declares
1 security scheme
for authenticating requests.
It accepts HTTP basic authentication (Basic).
By default, every request must be authenticated.
Paths & Operations 3
Across 1 path, the API surfaces 3 operations — 1 DELETE, 1 GET, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Deposit 3
The Deposit resource
GET
/properties/{propertyId}/depositPolicy
Expedia Group Obtain the deposit policy for a given property
getDepositPolicy1 param→ 200401403404500503
PUT
/properties/{propertyId}/depositPolicy
Expedia Group Create/update the deposit policy for a given property
Expedia Group Delete the deposit policy for a given property
deleteDepositPolicy1 param→ 204401403404500503
Schemas 11
The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are DateRange (3 properties), PaymentPolicy (3 properties), ExceptionPolicy (3 properties), Deposit (3 properties). Each schema is shown below with its type and property counts.
ExceptionPolicy
object
3 properties
Deposit
object
3 properties
Link
object
Object describing a single link to a resource to which this deposit policy is linked to.
1 property1 required
Links
object
Object describing links to other resources to which this deposit policy is linked to.
2 properties2 required
PaymentPolicy
object
3 properties2 required
SuccessfulGetResponse
object
1 property1 required
DateRange
object
3 properties2 required
ErrorResponse
object
1 property1 required
Error
object
An object describing an error returned by the service.
2 properties2 required
PaymentTime
object
Order of payments in the array matters. Payments must be specified in chronological order: UPONBOOKING followed by DAYSPRIOR followed by UPONARRIVAL.
2 properties1 required
DefaultPolicy
object
2 properties1 required
Specification
The full machine-readable OpenAPI contract behind this narrative.
