Feature Requests

Sort by

• Newest Reply
• Newest Topic

Hi Nicole,

Although it wouldn't add the other guests and their contact information to the booking, you could create custom field codes asking for the information for the additional guests, such as their names and email addresses. This should show up on the POC form, and once it's been filled out, it should show up under the Custom Fields tab of the booking. More on how to set this up here: https://www.ownerrez.com/support/articles/capture-additional-fields-on-checkout-quote-acceptance

Once you have the email addresses for the additional guests, you could manually send emails to those guests about check-in instructions, property details, etc. 

Hello, 

The issue has been raised that it is common that different properties will need to map deposits to separate bank accounts.  I see no reason why anyone would need to map deposits to different channels.   Has there been a feature request for this?  Do I need to set up separate OwnerRez accounts to achieve this currently?  Or is there another workaround?

Thank you.  

Jory

Hey Jimmy,

I see what you’re getting at from a security standpoint.

Right now, our API doesn’t support scoped permissions like read-only vs. write. OAuth applications and personal access tokens are granted full access, and it’s up to the application itself to determine what actions it performs. So if your app is only making GET calls, it will effectively behave as read-only.

Since OAuth is already handling authentication securely, and the application controls which endpoints it calls, this isn’t something we currently have plans to change. Adding permission scoping at the token level would be a fairly large architectural shift.

That said, I appreciate you sharing the use case. It’s helpful context as we continue to evaluate API improvements over time.

-Steve

We appreciate you taking the time to submit this feature request! If you know other users who would benefit from this, we'd encourage you to share it with them so they can add their support by way of an upvote at the top of the page.

Hello OwnerRez Team,

I am requesting a new feature that would allow users to limit an OAuth application's access to be strictly read-only.

Current Problem
I am developing an application to pull daily updates on my vacation rentals. Per confirmation from Partner Help, currently, both personal access tokens and OAuth applications are granted full write access to the API.

For security and best practice, applications that only need to retrieve data, like my daily snapshot bot, should not be granted full write permissions. This unnecessarily expands the risk profile for the user's data should the application ever be compromised.

Requested Feature
Please add an option to scope a new OAuth application or Personal Access Token to "read-only" access. This would ensure that API calls using that specific token or app cannot perform any create, update, or delete actions, providing a more secure way to use the API for informational and reporting purposes.

This feature would significantly improve the security and utility of your API for developers building read-only integrations.

Thank you,

Jimmy

We appreciate you taking the time to submit this feature request! If you know other users who would benefit from this, we'd encourage you to share it with them so they can add their support by way of an upvote at the top of the page.

We appreciate you taking the time to submit this feature request! If you know other users who would benefit from this, we'd encourage you to share it with them so they can add their support by way of an upvote at the top of the page.

Exciting! Thank you for this update, Bri!

Owner Bookings made it through development and is moving to QA / Testing at this time! Do keep in mind that our testers may need to kick it back to our devs for some fine tuning, so there's not a great ETA I can provide yet. The ball is rolling though, and I've seen the work myself. It's coming along very nicely.

We'll keep everyone posted with updates as they become available.

I currently have about 55 properties listed with Homes and villas by Marriott through Hostaway and I would love to bring them over to Ownerrez and get rid of Hostawy. please advise me asap as to when I can do that 

We've received your feature request—thank you! If you think others would love this too, spread the word and invite them to upvote. Community feedback really helps us prioritize what to build next.

[This topic has been merged with another topic (Feature Request: Export and Import Listing Descriptions for AI Optimization). All unique votes have also been merged.]

[Another topic was closed as a duplicate of this topic (Archive or export entire Property Description)]

I'm aware of that but that's rather "old school", really want a dashboard info thing instead, way more useful.

Great suggestion—thanks for submitting! Know anyone else who'd benefit from this? Send them the link so they can add their vote and show there's interest in making this happen.

Hello!

Along with setting up tag automation, you can create a template and trigger to send yourself an email for any guests who haven't signed the RA yet. We have this support article that goes over how you can set it up: https://www.ownerrez.com/support/articles/trigger-example-reminder-yourself-renter-agreement-has-not-been-signed

We've received your feature request—thank you! If you think others would love this too, spread the word and invite them to upvote. Community feedback really helps us prioritize what to build next.

We appreciate you taking the time to submit this feature request! If you know other users who would benefit from this, we'd encourage you to share it with them so they can add their support by way of an upvote at the top of the page.

Throwing mine in for beta testing too! 

But does this require having 10 properties?

We've received your feature request—thank you! If you think others would love this too, spread the word and invite them to upvote. Community feedback really helps us prioritize what to build next.

Hallelujah 🙌 appreciate all the hard work! 

This is so exciting! A great option in tricky economic markets to allow guests to book with points. I’m very excited about this and would just want to put my name in the hat as a possible beta tester!

Development on an integration with Homes and Villas by Marriott Bonvoy is underway! There's no ETA I can provide at this time, but we will keep everyone posted as things progress.

It would be very helpful if the API v2 property photo endpoints included a room_id field (or similar room/space association) for each photo in the response.                                

Use case: We're building a custom property website that displays photos organized by room (bedroom, kitchen, pool, etc.). Currently, while OwnerRez allows assigning photos to rooms in the UI, there's no way to retrieve that association through the API. This means we have to manually tag or sort photos on our end, which is tedious and doesn't stay in sync when photos are updated in OwnerRez.                                                                        

What we'd like to see: When fetching photos via the API (e.g., GET /v2/properties/{id}/photos), each photo object would include a room_id or room_name field indicating which room it's assigned to, matching what's configured in the OwnerRez dashboard.

This would allow API consumers to programmatically organize photo galleries by room without manual intervention. Thank you!

Apologies for resurrecting an old thread here but I'm running into the same issue publishing a new listing to VRBO where my photos don't get assigned to rooms. Thankfully they're not getting random assignments; they're just not getting assigned to anything.

My question here is, if I actually go into my VRBO listing and assign those photos to rooms, will they stick or will they all get overwritten the next time I push an update from OwnerRez to VRBO?

Add a “Send Again” option directly within Communication History for previously sent messages.

Right now, even though the message is visible in Communication History, resending it requires navigating away and re-finding it under Messages, where “Send Again” is currently available.

Use Case
A common scenario:

• A guest says they can’t find their check-in instructions.
• The fastest way to confirm what was sent is: Booking → Communication History → locate the message
• At that point, the exact message is already on screen — but there’s no way to resend it from there.

Instead, the current workflow requires that I go back to the Booking → Messages → find the message → Send Again

This adds unnecessary time, steps, and friction for a very common task.

Why this would help

• Faster response time to guests

• Eliminates searching through the Messages list

• Keeps actions aligned with where the information already lives

Communication History already shows what was sent and when — adding a “Send Again” action here would streamline a simple, frequent workflow.

this is a major issue.  Are ya'll adjusting the rent and surcharges one by one on all airbnb reservations once you download the property management report into excel?

I second this.

It's going to be confusing for our customers to see a price then have VAT added only at the booking stage.

I think it's a reflection of how few people in the UK use Ownerrez that his is has not have more votes. It's essential for us an I wasn't aware this couldn't happen. 

I SAW IT!!! Thank you for the quick fix!!