Assistant planning workflow
Submit a travel inquiry with the traveler’s permission.
This interface supports one confirmed travel-planning request to Selena Huck. It creates an inquiry for personal follow-up. It does not book travel, collect payment, hold inventory, or provide a live quote.
Contract published September 30, 2026. OpenAPI description · API catalog · Privacy notice
Review and confirm before submitting
- Read the public guides and collect the traveler’s trip style, planning window, traveler count, comfortable total budget, name, and email. Preserve exact dates, airports, traveler and room configurations, and priorities in the optional fields. Ask for consequential missing details rather than inventing them.
- Explain that submitting stores the inquiry and consent time, attempts a traveler planning-snapshot email, and schedules advisor notifications. A planning snapshot is guidance, not a live quote. Provide the privacy notice.
- Ask for contact permission using the statement below. Offer marketing consent as a separate optional choice. Declining marketing does not prevent a response to the trip request.
- Show the exact trip and contact details that will be sent, the contact preference, and both consent choices. Obtain explicit final confirmation to submit that reviewed request. General interest in travel, an earlier request for research, or a generated example is not submission confirmation.
- Submit once only after confirmation. If any material field or consent choice changes, review the updated payload and obtain confirmation again. A browser assistant can instead help the traveler use the three-step quiz; the traveler should review and submit it.
- Report the actual response. A 201 confirms storage; report the email flag accurately. Never describe this as a booking, hold, inbox delivery, or guaranteed advisor notification.
Required contact consent
I agree that Selena may contact me by email about this travel request. I can ask to stop at any time.
Send literal JSON consent: true only when the traveler gives this permission and confirms submission. The server validates this boolean; it cannot independently verify that the assistant obtained the final confirmation.
Separate optional marketing consent
Also send me occasional Escape Mode travel inspiration and planning updates. I can unsubscribe at any time.
Keep marketingConsent false or omitted unless separately and explicitly chosen. Do not infer marketing consent from contact consent, preselect it for the traveler, or use a request for a quote as marketing permission.
Supported request
POST https://escapemodetravels.com/api/leads with Content-Type: application/json. The total body must be no more than 16,384 UTF-8 bytes.
No API key, OAuth token, or account is required for this public submission interface. Server-side HTTPS clients are supported. Cross-origin browser integration is not enabled. If an Origin header is present, its hostname must match the API request hostname. Server-side clients normally send no Origin header; do not forge browser origins or bypass a rejection.
Use only the documented field set. The supported contract limits are listed below. The current server trims strings and truncates overlong strings; assistants must keep within the limits so traveler details are not silently lost. Unknown optional values must be omitted, not guessed.
| Field | Required | Allowed value / limit | Meaning |
|---|---|---|---|
tripType | Yes | cruise, all-inclusive, bahamas-caribbean, disney-universal, europe, family-group, not-sure | Trip style chosen by the traveler. |
timing | Yes | 0-3, 3-6, 6-12, 12-plus, exploring | Planning window, not an exact departure date. Put exact dates in notes if known. |
travelers | Yes | 1, 2, 3-5, 6-plus | Traveler count range. Put exact traveler and room requirements in notes if known. |
budget | Yes | under-3000, 3000-5000, 5000-8000, 8000-15000, 15000-plus, not-sure | Comfortable total planning range in USD; not a verified package price. |
firstName | Yes | string, up to 80 characters | Traveler's first name; must be nonempty after trimming. |
email | Yes | string, up to 254 characters | Traveler's email; trimmed, lowercased, and checked for a simple local@domain.suffix shape. |
consent | Yes | boolean true | I agree that Selena may contact me by email about this travel request. I can ask to stop at any time. Set true only after explicit permission and final submission confirmation. |
marketingConsent | No | boolean, default false | Also send me occasional Escape Mode travel inspiration and planning updates. I can unsubscribe at any time. Optional, separate opt-in. Omit or send false unless the traveler explicitly chooses it. |
phone | No | string, up to 40 characters | Optional phone number. The server does not validate phone format. |
contactPreference | No | email, phone | Use phone only when the traveler requests it and provides a phone number. Otherwise the server uses email. |
destination | No | string, up to 120 characters | Destination idea; omit if undecided. |
departureAirport | No | string, up to 80 characters | Departure airport or city supplied by the traveler. |
notes | No | string, up to 1200 characters | Trip dates, traveler/room configuration, priorities, and other nonsensitive details confirmed by the traveler. |
conciergeContext | No | string, up to 1200 characters | Optional short traveler-approved conversation summary. Appended to notes; combined stored notes are limited to 1,200 characters, with notes first. |
referrerName | No | string, up to 100 characters | Optional referral name supplied by the traveler. |
offer | No | string, up to 120 characters | Optional real site offer identifier; do not invent a promotion or price. |
sessionId | No | string, up to 80 characters | Optional session identifier. Omission creates a UUID. This is not an idempotency key. |
source | No | string, up to 100 characters | Optional source label, such as assistant. Omission or empty text becomes direct. |
utmSource | No | string, up to 120 characters | Optional known campaign source. |
utmMedium | No | string, up to 120 characters | Optional known campaign medium. |
utmCampaign | No | string, up to 160 characters | Optional known campaign name. |
utmContent | No | string, up to 160 characters | Optional known campaign content identifier. |
referrer | No | string, up to 500 characters | Optional actual referring page URL. Do not invent attribution. |
Budget values are total planning ranges in USD. Timing and traveler count use ranges; put exact dates and traveler/room counts in notes when known. A phone preference is honored only with a phone number; otherwise the server uses email. The notes and optional conversation summary share a stored 1,200-character limit, with notes first.
Keep passport images or numbers, payment-card details, passwords, government identification, medical records, and other highly sensitive information out of this interface. Share only traveler-approved, relevant details; use a secure method from Selena if sensitive booking information is later needed.
Example payload — documentation only
This example does not represent a real traveler or permission. Replace it with reviewed details; do not submit it for testing.
{
"tripType": "cruise",
"timing": "exploring",
"travelers": "2",
"budget": "3000-5000",
"firstName": "Example Traveler",
"email": "traveler@example.com",
"consent": true,
"marketingConsent": false,
"contactPreference": "email",
"source": "assistant",
"notes": "Example only. Replace with the traveler's confirmed trip details before submitting."
}Responses and errors
A created inquiry returns HTTP 201 and JSON with a UUID leadId and boolean emailSent. Save the ID for the traveler’s records; it is not a credential and does not grant access to retrieve or change the inquiry.
emailSent: true means the email service accepted the traveler snapshot. It does not prove inbox delivery. emailSent: false with 201 means the inquiry was still stored and the automatic traveler email failed. Advisor notifications are separate background work; this response does not confirm their delivery.
| HTTP status | Meaning |
|---|---|
| 200 | Unexpected non-created response. Do not interpret this as a stored inquiry; only 201 is documented creation success. Do not retry automatically. |
| 201 | Inquiry stored. Returns leadId and emailSent. emailSent=true means the email service accepted the traveler snapshot, not that it reached the inbox. Advisor notifications run separately and are not confirmed by this flag. |
| 400 | The request was not valid. Malformed JSON, a non-object JSON body, or a body over 16,384 UTF-8 bytes. |
| 403 | Invalid request origin. A supplied Origin header has an invalid or different hostname. |
| 422 | Please complete the required trip and contact fields. Missing or invalid required fields, option values, email, or literal boolean consent=true. |
| 429 | This request has already been received. Selena will follow up soon. At least three inquiries for this normalized email have been stored in the preceding ten minutes. This is a rate limit, not a lookup or idempotency guarantee. |
| 500 | Something went wrong. Please try again. Persistence or other server processing failed. Some side effects may already have occurred; do not automatically retry. |
Errors use JSON with an error message. Transport or platform failures may have a different body. Do not promise a delivery or follow-up deadline.
Storage, emails, and retries
- Successful processing stores the inquiry, campaign/source details, contact-consent time, a lead-created event, and internal follow-up priority.
- Only a separate
marketingConsent: truecreates or updates the email’s marketing subscription and opt-in time. Omitting or declining it does not subscribe this request, and does not unsubscribe a prior subscription. Privacy requests can be sent to Selena. - The server attempts the traveler snapshot email and queues an advisor notification. A failed traveler email also triggers an attempt at an advisor follow-up alert. Acceptance is not inbox delivery; advisor email errors do not change an already-created response.
- There is no idempotency key, automatic duplicate suppression, or supported inquiry-status lookup. A sessionId does not prevent duplicates. Each accepted POST may create another inquiry and send more emails.
- Do not retry automatically after a timeout, 500, 429, or unexpected response. A timeout or 500 can happen after records were saved or an email was attempted. Explain the uncertain outcome and ask the traveler to contact Selena rather than risking a duplicate.
- For a clear 400 or 422, correct the stated problem, review any changed payload, and obtain confirmation before a new submission. Do not work around a 403 origin rejection.
Scope
Only the public planning-inquiry submission is supported by this contract. Private advisor operations and internal site interfaces are not advertised as assistant capabilities. Assistants should use public pages for research and this confirmed submission workflow for a planning inquiry.