Submit venue booking requests and vendor contact inquiries through the WedStay API.

Inquiry Endpoints

Submit booking requests to venues and contact inquiries to vendors. Each call creates a real lead, so submit only with the user's explicit go-ahead.

Venue requests: A WedStay concierge replies within 24 hours.
Vendor inquiries: Screened by WedStay, then sent to the vendor, who replies within 3 business days.

Both endpoints require sms_consent. Ask the couple: "OK if WedStay texts you about this request?" Send true only if they said yes. With false, WedStay replies by email. A request without a boolean sms_consent is refused with a 400 (invalid_request_error, param: "sms_consent") and nothing is submitted.

Submit venue inquiry

POST /api/v1/inquiries/venue

Submit a booking request to a specific venue. A WedStay concierge replies within 24 hours.

Request body

Field	Type	Required	Description
`property_slug`	string	Yes	The venue's URL slug (from search results)
`start_date`	string	Yes	Check-in date (ISO 8601: `2026-09-19`)
`end_date`	string	Yes	Check-out date (ISO 8601: `2026-09-22`)
`event_guests`	number	Yes	Number of event guests
`overnight_guests`	number	No	Number of overnight guests
`guest_name`	string	Yes	Full name of the person inquiring
`guest_email`	string	Yes	Contact email address
`guest_phone`	string	No	Contact phone number
`message`	string	No	Additional details or questions (max 5000 chars)
`sms_consent`	boolean	Yes	Ask the couple: 'OK if WedStay texts you about this request?' Send true only if they said yes.

Example request

curl -X POST "https://www.thewedstay.com/api/v1/inquiries/venue" \
  -H "Authorization: Bearer ws_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "property_slug": "texas/canyon-lake/texas-wedding-village-14-cabins-sleep-100-pool-event-spaces-for-300-sleeps-84",
    "start_date": "2026-09-19",
    "end_date": "2026-09-22",
    "event_guests": 80,
    "overnight_guests": 30,
    "guest_name": "Sarah Johnson",
    "guest_email": "sarah@example.com",
    "guest_phone": "+1-555-0123",
    "message": "Looking for a weekend wedding with outdoor ceremony space.",
    "sms_consent": true
  }'

Example response

{
  "data": {
    "inquiry_id": "550e8400-e29b-41d4-a716-446655440000",
    "status": "submitted",
    "message": "Your booking request has been submitted. A WedStay concierge replies within 24 hours."
  },
  "request_id": "req_abc123def456"
}

Submit vendor inquiry

POST /api/v1/inquiries/vendor

Send a contact inquiry to a vendor. Screened by WedStay, then sent to the vendor, who replies within 3 business days.

Request body

Field	Type	Required	Description
`vendor_slug`	string	Yes	The vendor's URL slug (from search results)
`guest_name`	string	Yes	Full name of the person inquiring
`guest_email`	string	Yes	Contact email address
`guest_phone`	string	No	Contact phone number
`event_date`	string	No	Event date (ISO 8601: `2026-09-20`)
`event_location`	string	No	Where the event will be held
`event_guests`	number	No	Guest count
`budget_range`	string	No	Budget range (e.g. "$3000-$5000")
`service_needed`	string	No	Specific service needed
`message`	string	No	Details about what you need (max 5000 chars)
`sms_consent`	boolean	Yes	Ask the couple: 'OK if WedStay texts you about this request?' Send true only if they said yes.

Example request

curl -X POST "https://www.thewedstay.com/api/v1/inquiries/vendor" \
  -H "Authorization: Bearer ws_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "vendor_slug": "sidpix-studios",
    "guest_name": "Sarah Johnson",
    "guest_email": "sarah@example.com",
    "event_date": "2026-09-20",
    "event_location": "Canyon Lake, Texas",
    "message": "Need a photographer for a 3-day weekend wedding, 80 guests.",
    "sms_consent": false
  }'

Example response

{
  "data": {
    "inquiry_id": "550e8400-e29b-41d4-a716-446655440000",
    "status": "submitted",
    "message": "Your inquiry has been received. Screened by WedStay, then sent to the vendor, who replies within 3 business days."
  },
  "request_id": "req_abc123def456"
}

Retries and idempotency

Inquiry endpoints are idempotent. Retrying a submission never creates a second lead.

Send an X-Idempotency-Key header with any value that uniquely identifies the submission:

curl -X POST https://www.thewedstay.com/api/v1/inquiries/venue \
  -H "Authorization: Bearer ws_live_..." \
  -H "X-Idempotency-Key: booking-01HZY5K9" \
  -H "Content-Type: application/json" \
  -d '{ "property_slug": "texas/canyon-lake/texas-wedding-village-14-cabins-sleep-100-pool-event-spaces-for-300-sleeps-84", ... }'

Situation	Result
Same key, same body	The original response is returned. No second lead.
Same key, different body	`409 idempotency_conflict`. Use a new key for a new request.
Same key, first request still running	`409 idempotency_in_progress`. Retry in a few seconds.
No key sent	The body is fingerprinted, so identical retries are still deduplicated.

Keys are remembered for 24 hours. A retry does not consume an extra slot from your inquiry limit. It does still count against your overall request quota, so retry with backoff.

Rate limits

Inquiry endpoints have stricter rate limits than read endpoints to prevent spam:

Tier	Venue inquiries	Vendor inquiries
Free	5 per day	5 per day
Pro and Partner	5 per day	5 per day

What happens after submission

WedStay's team is notified right away.
Venue requests: A WedStay concierge replies within 24 hours.
Vendor inquiries: Screened by WedStay, then sent to the vendor, who replies within 3 business days.
The couple's sms_consent answer is stored with the inquiry, with the time and the source. With false, WedStay replies by email.

Inquiry Endpoints

Submit booking requests to venues and contact inquiries to vendors. Each call creates a real lead, so submit only with the user's explicit go-ahead.

Venue requests: A WedStay concierge replies within 24 hours.
Vendor inquiries: Screened by WedStay, then sent to the vendor, who replies within 3 business days.

Submit venue inquiry

POST /api/v1/inquiries/venue

Submit a booking request to a specific venue. A WedStay concierge replies within 24 hours.

Request body

Field	Type	Required	Description
`property_slug`	string	Yes	The venue's URL slug (from search results)
`start_date`	string	Yes	Check-in date (ISO 8601: `2026-09-19`)
`end_date`	string	Yes	Check-out date (ISO 8601: `2026-09-22`)
`event_guests`	number	Yes	Number of event guests
`overnight_guests`	number	No	Number of overnight guests
`guest_name`	string	Yes	Full name of the person inquiring
`guest_email`	string	Yes	Contact email address
`guest_phone`	string	No	Contact phone number
`message`	string	No	Additional details or questions (max 5000 chars)
`sms_consent`	boolean	Yes	Ask the couple: 'OK if WedStay texts you about this request?' Send true only if they said yes.

Example request

curl -X POST "https://www.thewedstay.com/api/v1/inquiries/venue" \
  -H "Authorization: Bearer ws_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "property_slug": "texas/canyon-lake/texas-wedding-village-14-cabins-sleep-100-pool-event-spaces-for-300-sleeps-84",
    "start_date": "2026-09-19",
    "end_date": "2026-09-22",
    "event_guests": 80,
    "overnight_guests": 30,
    "guest_name": "Sarah Johnson",
    "guest_email": "sarah@example.com",
    "guest_phone": "+1-555-0123",
    "message": "Looking for a weekend wedding with outdoor ceremony space.",
    "sms_consent": true
  }'

Example response

{
  "data": {
    "inquiry_id": "550e8400-e29b-41d4-a716-446655440000",
    "status": "submitted",
    "message": "Your booking request has been submitted. A WedStay concierge replies within 24 hours."
  },
  "request_id": "req_abc123def456"
}

Submit vendor inquiry

POST /api/v1/inquiries/vendor

Send a contact inquiry to a vendor. Screened by WedStay, then sent to the vendor, who replies within 3 business days.

Request body

Field	Type	Required	Description
`vendor_slug`	string	Yes	The vendor's URL slug (from search results)
`guest_name`	string	Yes	Full name of the person inquiring
`guest_email`	string	Yes	Contact email address
`guest_phone`	string	No	Contact phone number
`event_date`	string	No	Event date (ISO 8601: `2026-09-20`)
`event_location`	string	No	Where the event will be held
`event_guests`	number	No	Guest count
`budget_range`	string	No	Budget range (e.g. "$3000-$5000")
`service_needed`	string	No	Specific service needed
`message`	string	No	Details about what you need (max 5000 chars)
`sms_consent`	boolean	Yes	Ask the couple: 'OK if WedStay texts you about this request?' Send true only if they said yes.

Example request

curl -X POST "https://www.thewedstay.com/api/v1/inquiries/vendor" \
  -H "Authorization: Bearer ws_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "vendor_slug": "sidpix-studios",
    "guest_name": "Sarah Johnson",
    "guest_email": "sarah@example.com",
    "event_date": "2026-09-20",
    "event_location": "Canyon Lake, Texas",
    "message": "Need a photographer for a 3-day weekend wedding, 80 guests.",
    "sms_consent": false
  }'

Example response

{
  "data": {
    "inquiry_id": "550e8400-e29b-41d4-a716-446655440000",
    "status": "submitted",
    "message": "Your inquiry has been received. Screened by WedStay, then sent to the vendor, who replies within 3 business days."
  },
  "request_id": "req_abc123def456"
}

Retries and idempotency

Inquiry endpoints are idempotent. Retrying a submission never creates a second lead.

Send an X-Idempotency-Key header with any value that uniquely identifies the submission:

curl -X POST https://www.thewedstay.com/api/v1/inquiries/venue \
  -H "Authorization: Bearer ws_live_..." \
  -H "X-Idempotency-Key: booking-01HZY5K9" \
  -H "Content-Type: application/json" \
  -d '{ "property_slug": "texas/canyon-lake/texas-wedding-village-14-cabins-sleep-100-pool-event-spaces-for-300-sleeps-84", ... }'

Situation	Result
Same key, same body	The original response is returned. No second lead.
Same key, different body	`409 idempotency_conflict`. Use a new key for a new request.
Same key, first request still running	`409 idempotency_in_progress`. Retry in a few seconds.
No key sent	The body is fingerprinted, so identical retries are still deduplicated.

Keys are remembered for 24 hours. A retry does not consume an extra slot from your inquiry limit. It does still count against your overall request quota, so retry with backoff.

Rate limits

Inquiry endpoints have stricter rate limits than read endpoints to prevent spam:

Tier	Venue inquiries	Vendor inquiries
Free	5 per day	5 per day
Pro and Partner	5 per day	5 per day

What happens after submission

WedStay's team is notified right away.
Venue requests: A WedStay concierge replies within 24 hours.
Vendor inquiries: Screened by WedStay, then sent to the vendor, who replies within 3 business days.
The couple's sms_consent answer is stored with the inquiry, with the time and the source. With false, WedStay replies by email.

Inquiries

Inquiry Endpoints

Submit venue inquiry

Request body

Example request

Example response

Submit vendor inquiry

Request body

Example request

Example response

Retries and idempotency

Rate limits

What happens after submission

On this page

Inquiries

Inquiry Endpoints

Submit venue inquiry

Request body

Example request

Example response

Submit vendor inquiry

Request body

Example request

Example response

Retries and idempotency

Rate limits

What happens after submission

On this page