Hi,
I noticed that not all property info is present in the initial properties/v2/list endpoint, unless we go and ping each property separately with the properties/v2/detail endpoint.
Is there a chance to include any of these in the returned JSON with properties/v2/list?
PS: I can see that example responses actually contain these, they have a lot more properties than the actual data, but when I try with an actual location I get 15, max 16 keys for each property
Doe mee aan de discussie - voeg hieronder een opmerking toe
Hello,
Thanks, in that case you should fix the example responses as they are misleading and not correct, offering something that’s not available.
Regards.
Hello,
No, there isn’t.
Regards.