WedStay
info@thewedstay.comGet the iOS App

Subscribe to our newsletter

By subscribing, you agree to receive emails and texts from WedStay. Unsubscribe anytime.

For Everyone

  • About Us
  • Is WedStay Legit?
  • How It Works
  • Download App
  • Blog
  • Reviews
  • FAQs
  • Terms
  • Privacy
  • Contact
  • We're Hiring!
  • Creator Program
  • Sitemap
  • Developers & API

For Couples

  • Wedding Venues
  • Wedding Venue Buyout
  • Wedding House Rentals
  • How WedStay Works
  • WedStay One Wedding Website
  • Wedding Venue Finder
  • Wedding Quizzes
  • Venue Style Quiz
  • How Venue Matcher Works
  • 2026 Wedding Trends
  • Viral Wedding Estates
  • Wedding Vendors
  • Wedding Inspiration
  • Non-Traditional Weddings
  • Wedding Weekend Experience
  • Wedding Planning Checklist Tool
  • Planning Tools
  • WedStay-Style Weddings
  • Venue Cost Calculator
  • Wedding Weekend Cost Calculator
  • Wedding Financing

For Property Owners

  • Submit Your Property
  • Wedding Industry Insights
  • Revenue Opportunities
  • WedStay Operating System
  • Property Transformation
  • Effortless Hosting
  • Top Wedding Trends

For Vendors

  • Join The WedStay Collective
  • Wedding Vendors
  • Wedding Photographers
  • The Ultimate Wedding Vendor Guide: A Former Bride's Tell-All

© 2026 WedStay. All rights reserved.

This site is not affiliated with or endorsed by Airbnb.

    WedStay Developers
    WedStay Developers
    API Referencethewedstay.com

    Getting Started

    WedStay APIQuickstart

    Endpoints

    VenuesVendorsPricingBlogInquiries

    Reference

    ErrorsRate LimitsChangelog

    Integrations

    MCP ServerChatGPT ActionBuilding AI-Powered Widgets

    Changelog

    Dated changes to the WedStay API, the MCP server, and the response shapes they return.

    Changelog

    Changes that affect integrations, newest first.

    2026-10-08

    • MCP server 2.0.0. The server at https://www.thewedstay.com/api/ai/mcp now reports version 2.0.0.
    • sms_consent is required. submit_venue_inquiry, submit_vendor_inquiry and the REST inquiry endpoints require a boolean sms_consent. Ask the user whether WedStay may text them about the request. A missing or non boolean value returns 400 with code sms_consent_required. See Inquiries.
    • Per stay pricing object. Venue results carry a structured pricing object for the stay, in the same currency the listing shows. See Venues.
    • budget_max. search_venues accepts budget_max, compared against each venue's starting price in the listing's own currency.
    • calculate_pricing slug mode and strict regions. Pass a venue slug to price that venue with the same engine as its page. Regions must be one of the listed ids or aliases; an unknown region returns an error. See Pricing.
    • Benchmark keys. Cost benchmarks use *_base_per_stay keys. The *_nightly aliases are deprecated and will be removed on 2027-01-06.
    • Rate limit headers. Every 429 carries Retry-After, and X-RateLimit-Reset is a Unix timestamp in seconds. See Rate Limits.

    Previous

    Rate Limits

    Next

    MCP Server

    On this page

    Changelog2026-10-08