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/mcpnow reports version2.0.0. sms_consentis required.submit_venue_inquiry,submit_vendor_inquiryand the REST inquiry endpoints require a booleansms_consent. Ask the user whether WedStay may text them about the request. A missing or non boolean value returns400with codesms_consent_required. See Inquiries.- Per stay pricing object. Venue results carry a structured
pricingobject for the stay, in the same currency the listing shows. See Venues. budget_max.search_venuesacceptsbudget_max, compared against each venue's starting price in the listing's own currency.calculate_pricingslug mode and strict regions. Pass a venueslugto 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_staykeys. The*_nightlyaliases are deprecated and will be removed on 2027-01-06. - Rate limit headers. Every
429carriesRetry-After, andX-RateLimit-Resetis a Unix timestamp in seconds. See Rate Limits.