Перейти к содержимому
Портал разработчика

FavoritesService_ListPropertiesWithCities

POST
/api/v1/favorites/properties
curl --request POST \
  --url https://dictionary.example.invalid/api/v1/favorites/properties \
  --header 'Content-Type: application/json' \
  --data '{ "hotels": [ "DEMO_VALUE" ] }'

Request Bodyrequired

Заголовок раздела «Request Bodyrequired»
Media typeapplication/json
object
hotels
required
Array<string>

Example 

{
  "hotels": [
    "DEMO_VALUE"
  ]
}

Responses

Заголовок раздела «Responses»

200

Заголовок раздела «200»

OK

Media typeapplication/json
object
hotels
required
Array<object>
object
city
required
object
name
required
string
country
required
string
hotels
required
object
key
additional properties
object
id
required
string
name
required
string
address
required
string
city
required
object
id
required
string
name
required
string
country
required
object
id
required
string
name
required
string
photos
required
Array<object>
object
url
required
string
rating
required
object
arrival
required
number format: float
cleaning
required
number format: float
place
required
number format: float
price
required
number format: float
service
required
number format: float
total
required
number format: float
reviewCount
required
integer format: int32
scores
required
integer format: int32
sources
required
Array<integer>
amenities
required
Array<object>
object
name
required
string
type
required
string
value
required
string
group
required
string
starRating
required
string

Example 

{
  "hotels": [
    {
      "city": null,
      "hotels": null
    }
  ]
}

default

Заголовок раздела «default»

Default error response

Media typeapplication/json

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

object
code

The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

integer format: int32
message

A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.

string
details

A list of messages that carry the error details. There is a common set of message types for APIs to use.

Array<object>

Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.

object
@type

The type of the serialized message.

string
key
additional properties
any

Example 

{
  "code": 1,
  "message": "DEMO_VALUE",
  "details": [
    {
      "@type": null
    }
  ]
}