API support for updating property Description and Accommodations Detail fields

It would be incredibly valuable to have write access to the Description and Accommodations Detail fields via the v2 API. Today these fields are read-only (and only available through the partnership-gated Listings endpoint), which blocks a lot of legitimate use cases for hosts managing their own accounts.

The use case driving this for me:

I manage 40+ short-term rental properties through OwnerRez. I'd like to run a small internal automation that refreshes the seasonal language in my listings on a weekly or monthly cadence — for example, swapping "cozy by the fire" language in January for "porch evenings on the Bourbon Trail" in July, while preserving every factual claim, amenity, and rule. The agent would read the current description, generate a seasonally-updated version, and write it back through OwnerRez so the changes sync to every channel I have connected (Airbnb, VRBO, Booking, direct site).

Without API write access, the only options are manual copy-paste across 80+ fields weekly (which won't get done), or building separate integrations against each channel's API (which isn't realistic for an independent host).

Other use cases I'd expect to be common:

• Bulk updates after rebranding or repositioning
• Auto-generating first-draft descriptions for new properties during onboarding using amenity/photo data already in OwnerRez
• Syncing listing content with an external CMS or knowledge base
• A/B testing description variants and rolling out the winner across a portfolio
• Periodic audits and updates against a content checklist (every listing mentions parking, distance to airport, etc.)

Suggested scope for v1:

• PATCH /v2/listings/{id} (or wherever appropriate) accepting description and accommodations_detail fields
• Same Personal Access Token auth model as the rest of the v2 API
• Rate-limited appropriately to prevent abuse

I understand listing content is sensitive and there are real concerns about API misuse (spammy edits, channel sync churn, etc.). Reasonable guardrails — rate limits, account-level toggles, partnership requirements for third-party apps but not for personal access tokens — would address most of those concerns.

Happy to be a beta tester if this gets prioritized. Thanks for considering.

— Brandon Farmer, Bourbon Rentals