40 results found
-
Filter leads response by source / status / creation date
We are using leads to generate statistics & charts. We only need leads generated through ORBIRENTALWIDGET and ORBIRENTALFORM source.
Without requested filters, we are going through each of the leads, and using the targeted sources. Here, we are spending our api request quota.
It would be great if you could consider following changes in future updates.
1. Filter leads by sources.
2. Filter leads by statuses.
3. Filter leads by date created before / after.
4. Allowing lead sorting by creation date.15 votes -
Add Booking.com and Vrbo listing IDs to API
Currently, the property endpoint returns the Airbnb ID but not Booking.com or Vrbo IDs. Also, the property-channel-links endpoint only includes channels like Homads, Vacaymyway, Golightly and Hometogo (if any)
It would be beneficial if the API could return Booking.com and Vrbo property IDs as well, since they're major platforms many of us use. This would make it much easier to manage listings across channels through automation.
6 votes -
Apply the Promo Code when creating a quote/lead via API
With the new Promo Codes endpoint, we now have the capability to retrieve/manage promo codes. However, we are currently unable to apply a promo code when generating a quote or lead.
The PM requires the functionality to pass a promo code when retrieving a quote, in order to accurately display the price breakdown to the customer and initiate the checkout process.
5 votes -
5 votes
-
v3 API - /orders to expose actual discount amount
can we get the actual discount amount? that's what all other PMS do and its easier to use rather than doing calculations (for the user as well)
5 votes -
Bulk update amenities via API
Bulk update amenities via API. Otherwise 5 amenities would require 5 separate calls and that's bad to scale.
4 votes -
Ability to add new owner via API
That'd allow smooth workflow without going back to UI
4 votes -
Paginate /guests endpoint
The /guests endpoint currently returns all the guests in Hostfully. This doesn't scale very well and if a user has 1,000s of guests it's possible the endpoint could timeout or the response payload would be too large to send.
It would be great to add limit and offset query parameters to this endpoint just like you have for some of your other endpoints (e.g. /v2/leads)
This would not need to be a breaking change, you could have the endpoint behave the same way if no pagination parameters are provided so that nothing changes for any software that is currently using…
4 votes -
Add granular update details to UPDATED_PROPERTY webhook payload
Currently, when a property is updated, the webhook event UPDATEDPROPERTY is triggered, but the payload only contains the propertyUid and the eventtype. This makes it difficult for integrators to know what changed and which endpoint should be called next.
I would like the payload to include more granular details about the type of update, for example:
Pricing update
Photo update
Amenities update
General property details update
Pricing rule update, etc.
This would allow API users to call only the relevant endpoints instead of fetching all related resources. It improves efficiency, reduces API calls, and provides clarity for event-driven…
3 votes -
API for checking/updating property check-in instructions
As far as I can tell, there is no way to programmatically set/validate/update the property specific check-in instructions. We would love to automate this process.
3 votes -
Webhook for PINCODE_UPDATED
To have event PINCODEUPDATED for webhook, at the moment, there are only PINCODECREATED
PINCODE_DELETED3 votes -
Stripe webhooks for cases when guests close browsers too early and payment failed to be recorded
a guest has gone in to book online the payment has been taken and processed through stripe but the booking has not gone through. Dates are not blocked and neither them nor us have recived any confirmation. This is becoming a bit of a worry as it's 3 guests now. They have all said the browser was open for ages after as they were waiting for confirmation.
3 votes -
API for the secured Guidebook link
I use a messaging platform, I'd like to be able to import the secure link so I can build automated templates using the variable coming from the API,
2 votes -
Support copy Production data over to Sandbox
That'd be helpful for testing purpose, where dataset is readily available and as realistic as possible.
2 votes -
Support query (GET) /properties by multiple locations
Support query properties by multiple locations.
Example:
GET /properties?agencyUid=...&location=Yorkshire,Dales,London,Manchester&limit=100
or
GET /properties?agencyUid=...&location=Yorkshire Dales&location=London&location=Manchester&limit=100
2 votes -
Ability to import empty icalendars
I want to able to import calendars into your system via Ical even the calendar was empty.
2 votes -
Combine both property's public and internal names in GET /properties and POST /propertiesql endpoint
For Property names i.e. Public name and internal Property name, is it possible to get both values in a single endpoint?
Presently, we only receive the "name" key in the "properties-get-uid" endpoint, which necessitates additional requests to the "propertydescriptions-get" endpoint to obtain the public name for each property.
2 votes -
Order endpoint to expose discount information
In PMP, there are two types of discounts: length of stay and discount code, and neither can be retrieved via GET order request.
Because the length of stay reduction is applied straight to the rent, there is no information about the reduced amount in the order. The discount code contains a separate line item, but there is no information about the discount in the GET order; all we see is a gap between the baseAmount and subTotal; there is no apparent indication that a discount has been applied.
It would be helpful to have separate line items for discounts in…
2 votesWe partially support discount line items for v3.x, still need to have the other discounts exposed, like length of stay
https://dev.hostfully.com/reference/getall_9
-
Need within the Lead_sql for return of CLOSED / CANCELLED leads
There is no return within the Leadsql CLOSED / CANCELLED leads.
This means we can't work fully with the Leadsql to our back-end connection.
All other statuses are present but these are not. This means more API calls and with the limitation within the amount of API calls per hour this will be a problem.2 votes -
VRBO Commissions posted in Hostfully View Order
Post VRBO Commissions on each booking View Order. You have this enabled for Booking.com, but we have to look up VRBO commissions on VRBO platform. VRBO bills commissions in batches, so this is hard to find and include on Owner Statements at the end of each month.
1 vote
- Don't see your idea?