47 results found
-
Do not change refresh token every time tokens are refreshed
Since working with APIs is unpredictable by nature, in this case, something went wrong and the credentials in our system were not updated as expected.
This is expected, as a lot of processes can go wrong, from network issues to database issues and more.
This is the reason I think that cases like the one we are discussing are expected and we will face them again in the future. It is not anyone's fault, it is the nature of the process.
Because of this, I think if the refresh token could always stay the same, we would easily update the…
1 vote -
Ability to PATCH /properties with specific fields only, without including required fields like pricing.dailyRate
Using the PATCH properties endpoint, if we want to update the "cleaningFee" within the "pricing" object, we are also required to supply the "dailyRate" value in order to keep the call from failing.
This is not desirable, because the PMS "dailyRate" may have been updated for many reasons, multiple times, and there is no "sync" from PMS back to our database, making this a very manual process to keep things aligned.
The only workaround we can think of now is a complex "round-trip" of data:
- call GET Properties endpoint to grab any data that may be overwritten during PATCH
- compare…
1 vote -
Send Owner Information to Breezeway
Breezeway has the ability to send automated messages to Owners during Owner Stays, but Hostfully does not send the Owners contact information to Breezeway to use this very helpful feature.
1 vote -
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 -
Expose balance field via /orders endpoint
Easier for certain workflow. As of now, the only option is to use GraphQL for that.
1 vote -
1 vote
-
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 -
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 -
API Ability to support Pushing Multiple Annual and Seasonal Check in/out days
This feature allows hosts to enforce a specific day of the week - or several - for their guests to check-in on, and subsequently check-out on. It’s possible to set Annual and Seasonal Check-in/Checkout days.
1 vote -
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 -
Support updating the rental conditions per property via the API
It is noted in the v1.5->3 upgrade guide that v3's agencies endpoint supports a "rentalConditions" field, but no other APIs seem to exist for updating the per-property rental conditions. It would be great to automate these to ensure they are accurate and make changing all properties a lot easier
1 vote -
Support parameterized variables for GraphQL API
Support parameterized variables for GraphQL API
1 vote -
API for assigning services to property
API for connecting for services and property, similar to /api/v3/property-ownership but for service assignment
1 vote -
Webhook for PINCODE_UPDATED
To have event PINCODEUPDATED for webhook, at the moment, there are only PINCODECREATED
PINCODE_DELETED3 votes -
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 -
Ability to import empty icalendars
I want to able to import calendars into your system via Ical even the calendar was empty.
2 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 -
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
- Don't see your idea?