Перейти к содержимому
API для партнёров

ReviewService_Create

POST
/api/v1/reviews
curl --request POST \
--url https://dictionary.example.invalid/api/v1/reviews \
--header 'Content-Type: application/json' \
--data '{ "review": { "author": "DEMO_VALUE", "avatar": "DEMO_VALUE", "hotel": "DEMO_VALUE", "advantages": "DEMO_VALUE", "disadvantages": "DEMO_VALUE", "photos": [ null ], "starRating": 1, "starService": 1, "starPlace": 1, "starPrice": 1, "starCleaning": 1 } }'
Media typeapplication/json
object
review
required
object
author
required
string
avatar
string
hotel
required
string
advantages
required
string
disadvantages
required
string
photos
Array<string>
starRating
required
integer format: uint32
starService
required
integer format: uint32
starPlace
required
integer format: uint32
starPrice
required
integer format: uint32
starCleaning
required
integer format: uint32

Example

{
"review": {
"author": "DEMO_VALUE",
"avatar": "DEMO_VALUE",
"hotel": "DEMO_VALUE",
"advantages": "DEMO_VALUE",
"disadvantages": "DEMO_VALUE",
"photos": [
null
],
"starRating": 1,
"starService": 1,
"starPlace": 1,
"starPrice": 1,
"starCleaning": 1
}
}

OK

Media typeapplication/json
object
review
required
object
id
required
string
provider
required
integer format: enum
author
required
string
avatar
string
date
required
string format: date-time
hotelId
required
string
hotel
required
string
advantages
required
string
disadvantages
required
string
photos
required
Array<object>
object
url
object
meta
object
updatedAt
string format: date-time
provider
integer format: enum
translations
object
key
additional properties
string
value
string
category
string
guid
string
description
string
tags
Array<object>

Tag - Photo tag object with id and name. Analytics spec: Tag as object with id and name fields.

object
id

Tag ID (1-7)

integer format: int32
name

Tag name (BEDROOM, KITCHEN, BATHROOM, YARD, VIEW_FROM_WINDOW, POOL, OTHER)

string
aspectRatio
number format: float
dateAdd
string
isPrimary
boolean
starRating
required
integer format: uint32
starService
required
integer format: uint32
starPlace
required
integer format: uint32
starPrice
required
integer format: uint32
starCleaning
required
integer format: uint32
createdAt
required
string format: date-time
text
required
string
providerId
required
string

Example

{
"review": {
"id": "DEMO_VALUE",
"provider": 1,
"author": "DEMO_VALUE",
"avatar": "DEMO_VALUE",
"date": "2026-11-15T12:00:00Z",
"hotelId": "DEMO_VALUE",
"hotel": "DEMO_VALUE",
"advantages": "DEMO_VALUE",
"disadvantages": "DEMO_VALUE",
"photos": [
null
],
"starRating": 1,
"starService": 1,
"starPlace": 1,
"starPrice": 1,
"starCleaning": 1,
"createdAt": "2026-11-15T12:00:00Z",
"text": "DEMO_VALUE",
"providerId": "DEMO_VALUE"
}
}

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
}
]
}