Ventrata

Configuration inputs can be set in your Ventrata checkout solution by doing one of two things:

Update Data-Config Attribute - by adding the below piece of code, replacing the <code>input</code> with the name of one of the supported inputs and specifying its value, see the configuration table below. Include multiple inputs separated by a comma <code>,</code> .

Add input to Script or Button - add the input to your data-config for script or button in the below format. Include multiple inputs separated by a comma <code>,</code> .

&lt;script src="https://cdn.checkout.ventrata.com/v3/production/ventrata-checkout.min.js" type="module" data-config='{"apiKey":"&lt;YOUR_API_TOKEN&gt;", "input1": "value", "input2": "value" } }'&gt;&lt;/script&gt;

- Update Data-Config Attribute - by adding the below piece of code, replacing the <code>input</code> with the name of one of the supported inputs and specifying its value, see the configuration table below. Include multiple inputs separated by a comma <code>,</code> .
 
 "input1" : "value", "input2" : "value"
 
- Add input to Script or Button - add the input to your data-config for script or button in the below format. Include multiple inputs separated by a comma <code>,</code> .
 
 &lt;script src="https://cdn.checkout.ventrata.com/v3/production/ventrata-checkout.min.js" type="module" data-config='{"apiKey":"&lt;YOUR_API_TOKEN&gt;", "input1": "value", "input2": "value" } }'&gt;&lt;/script&gt;

Ventrata checkout support the following configuration inputs:

Configuration inputs are settings and parameters that define how checkout operates and behaves.

Supported Configuration Inputs

Dashboard

Home

Status

About

Developer Docs

Careers

Release Notes

Resources

Company

Find answers and get help from Intercom Support and Community Experts

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Title

Track the progress of all tickets related to your company.

Tickets portal.

{assigneeName} needs more information from you

Input	Default	Description
`"lang"`	by default not set	optional, lower case, for example, `en, cs` 📒 NOTE If both `"lang"` and `"currency"` are specified in the `data-config`, the globe icon used to select the language and currency on the checkout is hidden as these parameters are predefined. This is typically used with the multi-booking feature. Learn more
`"currency"`	by default not set	optional, upper case, for example, `USD, EUR, CZK` 📒 NOTE If both `"lang"` and `"currency"` are specified in the `data-config`, the globe icon used to select the language and currency on the checkout is hidden as these parameters are predefined. This is typically used with the multi-booking feature. Learn more
`"env"`	by default not set	`"live"` OR `"test"` ; if left empty checkout defaults to `test`
`"apiKey"`	your `apiKey` MUST be defined at least once per script import	your apiKey is located in your Ventrata dashboard Locate apiKey
`"embedded"`	false	Allows the usage of embedded mode. The page requires the presence of an HTML element with the `ventrata-embedded-widget` attribute. Learn more
`"multibooking"`	`false`	Allows the usage of a cart (having multiple bookings for the same order). It will trigger the bottom bar, which informs users about the current order content. Learn more
`"productID"`	by default not set	ID of the product If not set, product list will be shown.
`"optionID"`	by default not set	ID of the option if set, the option is pre-selected
`"bookingID"`	by default not set	ID of the booking (used only for `multibooking`) Its presence needs to be paired with `orderID`. Learn more
`"orderID"`	by default not set	ID of the order (used only for `multibooking`) Its presence needs to be paired with `bookingID` . Learn more
`"checkMarketingConsent"`	by default not set	if set to true, marketing consent will be pre-selected for users on the Contact Details of the Checkout page
`"referrer"`	by default not set	string value, for example, `hilton.com` Learn more
`"page"`	by default not set	string value; trigger checkout with a specific page in the checkout process such as Tickets or Checkout; use only in combination with `orderID`, supported values: [`”checkout”`] > `{"page": "checkout"}` Learn more