모든 토론으로 돌아가기
properties/v2/list-for-sale photos
drush81
2 года назад
Is there a reason that the list-sold endpoint result includes a photos array with urls, and the /list-for-sale endpoint only includes a count of the photos?
아래에 의견을 추가하고 토론에 참여하세요.
새 댓글을 게시하려면 로그인 / 가입
Hello,
According to UX/UI of the official application, the listing endpoints are mapped to listing pages. They often return a thumbnail image only in such pages. You will need to use get detailed endpoint to get all available photos. Anyway, we always try to fetch for as much as possible data from the source for you.
Regards.
The following request/response always includes the photos array
Request
properties/v2/list-sold
Response
{ …
“property_id”:"---------------",
“photo_count”:16,
“photos”:[…]16 items
… }
The following request/response from detail always includes the photos array
Request
properties/v2/detail - params: {property_id: ‘M9600363602’}
Response
{ …
“property_id”:“M9600363602”,
“photo_count”:16,
“photos”:[…]16 items
… }
The following request/response from the same property using list-for-sale does not include the photos array
Request
properties/v2/list-for-sale
Response
{ …
“property_id”:“M9600363602”,
“photo_count”:16
… }
Im wondering why the last example doesnt include the photos array like list-sold does
Hello,
Please don’t talk plain text, give some request and response samples to get help.
Regards.