​

Introduction

Ventrata is a proven and versatile booking platform built for high volume tours and attractions. With contactless booking, payment and check-in solutions we can provide the perfect solution to all your booking needs.

​

MoEngage × Ventrata

With the MoEngage and Ventrata integration, you can send the booking related updates of your users to MoEngage to create a richer user profile and trigger hyper-personalised campaigns. With this integration, you can create events as soon as a booking is updated in Ventrata.

​

Integration

​

Step 1: Get your MoEngage endpoint

To get a dedicated endpoint for your integration, please contact the MoEngage Support team. In your request, you must specify the common identifier used to link user profiles between MoEngage and the partner platform. For example, this is your email ID or the phone number of the user.

​

Step 2: Create webhook in Ventrata

You need to make an API call to create a webhook in Ventrata. Refer to Ventrata docs for more details.

• API endpoint: https://api.ventrata.com/octo/webhooks
• Method: POST
• Headers:
  { 
     "Content-Type": application/json, 
     "Authorization": "Bearer <Ventrata API key>" 
  }
  

Here, <Ventrata API key> is your API key issued to you by your supplier. Refer to the Ventrata doc for more details.

• Body:
  { 
     "event": "booking_update", 
     "url": "<MoEngage endpoint>" 
     "retryOnError": true,
     "useContactLanguage": true,
     "headers": {
        "Authorization": "Basic <API Token>",
        "Content-Type": application/json
     },
     "capabilities": ["octo/pricing"]
  }
  

Here, Once done, you will receive a successful response from webhook.

​

Step 3: View data in MoEngage

Once it is set, as soon as the event is triggered, the webhook will send an update to the MoEngage endpoint and data will start showing up on MoEngage as events. You can validate this from the user profile.

​

Event details

Details on the event created in MoEngage:

​

Rate Limits

To maintain platform stability, MoEngage limits ingestion of Ventrata data to a maximum of 500 requests per second (RPS) per workspace. If your workspace exceeds this limit, MoEngage returns an HTTP 429 (Too Many Requests) status code. Refer to Ventrata’s default retry policy to understand how rate limiting affects your data flow. For more information about payload size and the other ingestion limits, refer to Partner Data Ingestion Rate Limits.