Callback Data

As part of the pre-configuration, your Checkin.com flow will be set up and adjusted to work with your current back-end system.

When a registration has been completed, there will be an object called mapped or completeData in the callback data where you can find all user data formatted and named according to your requirements.

This way, you can re-use all your current API endpoints and validations.

In addition to the formatted data, there is also a normalized data structure which can be used for re-targeting and validations via the update events.

📘

Every setup is unique

Because your flow is tailor-made for you, the data in your production callback will be different from the example below.

Example data

{
  credentials: {
    consent: true, // Boolean
    email: "[email protected]", // String
    password: "password123" // String
  },
  user: {
    firstName: "Patrik", // String
    lastName: "Reitze", // String
    country: "GB", // String
    currency: 'USD', // String
    postalCode: "W18WLG", // String
    city: "London", // String
    streetName: "Cavendish Square", // String
    houseNumber: "B", // String
    phone: "07123456", // String
    phoneE164: "+497123456", // String; In E.164 format
    birthdate: "1967-05-23 00:00:00.00", // Date Object (UTC)
    newsletter: "Yes" // String
  }
}