Retrieve a review
GET/property/{connection_id}/review/{id}
Retrieves a single PropertyReview by its id. Obtain id values from the corresponding list endpoint. Use fields to return only the fields you need.
Parameters
fieldsstring array
Fields to return
rawstring
Raw parameters to include in the 3rd-party request. Encoded as a URL component. eg. raw parameters: foo=bar&zoo=bar -> raw=foo%3Dbar%26zoo%3Dbar
connection_idstring required
ID of the connection
idstring required
ID of the Review
Returns
| Response field | Type | Required | Description |
|---|---|---|---|
id | string | No | unique identifier for the review |
created_at | string (date-time) | No | when the review was created (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) |
updated_at | string (date-time) | No | when the review was last updated (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) |
listing_id | string | No | pointer to the Property Listing that was reviewed |
reservation_id | string | No | pointer to the Property Reservation that was reviewed |
guest_id | string | No | pointer to the Property Guest who wrote the review |
author_name | string | No | the reviewer name |
source | string | No | the channel the review was posted on, eg. Airbnb |
title | string | No | the review title |
content | string | No | the review text |
rating | number | No | the overall rating |
category_ratings | PropertyCategoryrating[] | No | ratings per category |
category_ratings[].category | enum | No | the rated category Values: CLEANLINESS, ACCURACY, COMMUNICATION, CHECKIN, LOCATION, VALUE, OTHER |
category_ratings[].rating | number | No | the category rating |
category_ratings[].comment | string | No | the guest comment for this category |
private_feedback | string | No | private feedback for the host |
response | string | No | the host public reply |
responded_at | string (date-time) | No | when the host replied (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format) |
is_public | boolean | No | whether the review is publicly visible |
metadata | PropertyMetadata[] | No | custom field values |
metadata[].id | string | No | the custom field identifier |
metadata[].slug | string | No | the custom field key |
metadata[].value | object | No | the custom field value |
metadata[].namespace | string | No | the scope or origin of the custom field |
metadata[].format | enum | No | the data type of the value Values: TEXT, NUMBER, DATE, BOOLEAN, FILE, TEXTAREA, SINGLE_SELECT, MULTIPLE_SELECT, MEASUREMENT, PRICE, YES_NO, CURRENCY, URL |
metadata[].extra_data | object | No | additional data about the custom field |
Errors
Errors return the HTTP status code and a JSON body with statusCode, error (the short label) and message (a human-readable detail).
{
"statusCode": 429,
"error": "Too Many Requests",
"message": "Too many requests to unified.to API; max requests per minute: N"
}| Status | Error | Meaning |
|---|---|---|
400 | Bad Request | The request was malformed or failed validation. |
401 | Unauthorized | The connection is likely broken; re-authorize it. |
403 | Forbidden | The connection is missing permissions or scopes. |
404 | Not Found | The requested resource does not exist. |
429 | Too Many Requests | Rate limit exceeded (see the two sources below). |
500 | Internal Server Error | An unexpected error occurred. |
501 | Not Implemented | Not supported by this integration. |
Errors from the underlying integration pass through: the integration's status comes back as ours (429, 401, 403, 404 or 5xx), usually with its message. When the integration's error body is unclear, Unified extracts what it can and returns a clearer message.
429 Too Many Requests
A 429 has two possible sources:
- The integration's own rate limit, passed through.
- Unified's workspace limit: a rolling 60 seconds, set by plan, with the message
Too many requests to unified.to API; max requests per minute: N.
const options = {
method: 'GET',
url: 'https://api.unified.to/property/5de520f96e439b002043d8dc/review/5de520f96e439b002043d8d8',
headers: {
authorization: 'bearer .....'
},
params: {
fields: '',
raw: '',
}
};
const results = await axios.request(options); Are we missing anything? Let us know
Was this page helpful?