Enquiries

The DASH API is a RESTFUL API that accepts URL based requests as well as JSON payloads. There are separate environments for test (staging) and live, please contact support to request the URL to use for your DASH instance.

Endpoint:

/api-v1/enquiries

The endpoint accepts the following request methods:

POST	Create an enquiry
GET	Read an enquiry / enquires
PUT	Update an enquiry
DELETE	Delete an enquiry

Authentication

Authentication is handled by way of a HTTP Authorization Bearer with a valid username and password. These should be provided with each request as part of the header information.

Your username is: J**********************5b

Your password is: ****************

Please ensure you keep these credentials secure.

Create an enquiry

To create an enquiry, you will need to provide a JSON payload in the body of your request.

Field list (customer elements):

Field:	Type:	Info:	Required:
`title`	[text]	Must be one of the following: 'Mr', 'Mrs', 'Ms', 'Miss', 'Mstr', 'Dr', 'Prof', 'Lord'	Optional
`first_name`	[text]	-	Yes
`last_name`	[text]	-	Yes
`contact_number`	[text]	All numbers are presumed to be UK unless prefixed with an international dialling code such as '+34' or '0034'.	*
`email_address`	[text]	-	*
`email_newsletter`	[integer]	‘Yes’ if the customer has consented to email marketing	Optional

* Either a contact_number or email_address must be provided.

Field list (holiday elements):

Field:	Legend:	Info:	Required:
`no_adults`	[integer]	Number of adults travelling	Yes
`no_children`	[integer]	Number of children travelling (including infants)	Optional
`departure_date`	[text]	Date format: 'yyyy-mm-dd'	Yes
`no_nights`	[integer]	Duration in nights	Optional
`holiday_type`	[text]	e.g. 'Multi-centre'	Optional
`destination`	[text]	e.g. 'Spain' or 'South America'	Optional
`details`	[text]	Additional information provided by the customer	Optional

Field list (enquiry elements):

Field:	Legend:	Info:	Required:
`enq_id`	[integer]	Used to determine if the enquiry has already been received (must be unique)	Optional
`rxd_datetime`	[integer]	When the enquiry was first submitted by the customer. Date / time format: 'yyyy-mm-dd hh:mm:ss'	Yes
`enq_method`	[text]	e.g. 'Summer Campaign'	Optional
`referrer`	[url]	The webpage the customer was on when they submitted this enquiry	Optional
`ip_address`	[text]	Valid IPV4 (preferred) or IPV6 ip address	Optional
`bing_click_id`	[text]	-	Optional
`google_click_id`	[text]	-	Optional
`utm_source`	[text]	-	Optional
`utm_campaign`	[text]	-	Optional

Example request (json):

{
      “first_name” : ”Joe”,
      “last_name” : ”Bloggs”,
      “contact_number” : ”+447788889999”,
      “email_address” : ”joe@bloggs.net”,
      “email_newsletter” : ”yes”,
      “no_adults” : 2,
      “departure_date” : ”2026-04-01”,
      “details” : ”We would like to go somewhere hot with a private beach.”,
      “rxd_datetime” : ”2025-12-14 11:34:01”,
      “referrer” : ”https://www.travelwebsite.com/deals/two-week-delights.html”, 
}

Example Response (json):

Upon receipt of a successful request, the endpoint will return a '200' HTTP code and will provide the id of the created enquiry:

{
      “status” : “success”,
      “data”: {
            “enquiry_id” : 12345,
      }
}

Error Handling:

If there is a problem with your request, the endpoint will return a '500' HTTP code and will provide details of the error:

{
      “status” : “error”,
      “message” : ”’rxd_datetime’ missing or invalid” 
}