Settings and activity
4 results found
-
Combine both property's public and internal names in GET /properties and POST /propertiesql endpoint
2 votesAn error occurred while saving the comment AdminDuc Tu (Admin, Hostfully) shared this idea ·
-
1 vote
AdminDuc Tu (Admin, Hostfully) shared this idea ·
-
15 votes
AdminDuc Tu (Admin, Hostfully) supported this idea ·
An error occurred while saving the comment AdminDuc Tu (Admin, Hostfully) commented
ChargeAutomation would love to have /leads response filtered by leadType as well.
AdminDuc Tu (Admin, Hostfully) shared this idea ·
-
1 vote
AdminDuc Tu (Admin, Hostfully) shared this idea ·
We need the property’s public name to be included in the following endpoints:
- GET /api/v3.2/properties
- GET /api/v3.2/properties/multi-units/unit-types
Specifically, we are looking for the same public name values that is currently available under /api/v3.2/property-descriptions for each property,
We already have those 2 endpoints and we don't want to introduce another one.. This causes huge load on our end which we want to avoid