Passing data to other systems

There are a few different ways to send data from to other platforms. 

In this article:

Using Zapier
Using outgoing webhooks in your notifications
Send data to Zapier through Webhooks
Using our API

Using Zapier

Zapier is a third party tool that allows you to connect over 1,000 apps. This means you can easily transfer data from through to your CRM or email service provider. Check out our article here on integrating Zapier to your account.

Using Outgoing Webhooks

Webhooks are a convenient way to pass data from one application to another with minimal programming ability. Similar to the use of an API, webhooks have a protocol to either retrieve information, send information or delete it from a server. can send webhook events that notify your application any time an event happens on your account.

Webhooks will fire off after a specific event has occurred i.e. a booking is made, rescheduled, or cancelled.

Essentially there are three things needed for a webhook to work properly:

An endpoint URL

This is where you will be sending the data.

The request type


This tells the webhook what to do with the information.

The payload

This is the information that you will be passing through.

You will be able to fill in any  shorthand code you have available to pull in information from your booking event and pass it through your webhook.

The basic formatting will look like (in JSON):


 "startDateTime": "{START}",

 "endDateTime": "{END}",

 "firstName": "{FNAME}",

 "email": "{EMAIL}"


The formatting for this is important to ensure that accurate information is delivered. You will be able to pass through any information that is collected and you have a shorthand code to reference (even custom ones you create).

The endpoint URL is something that will be provided by the application or service you are passing this information into. Many companies will have documentation on how to use webhooks through their platforms, including the correct parameters you need to specify in the first " " set.

Encoding webhooks for special characters

Use encoding tags to preserve special characters passed through webhooks.

There are two tags to encode special characters, one for the webhook's URL and one for the webhook's payload.


These tags will allow special characters to appear correctly when passed through webhooks.

Setting up a webhook

Selecting the booking page you want to add a webhook, and click Edit Settings.

  1. Select Notifications from the left menu.
  2. Click Actions under the sub-menu.
  3. Click into the step you wish to have the webhook fire (Confirmation, Reschedule, Cancellation, Reminder)
  4. Click the + to add a new notification
  5. Click Webhook
  6. Enter URL
  7. Choose method
    1. GET - retrieves information about a resource.
    2. PUT - Creates a new resource
    3. POST - Changes an existing resource
    4. PATCH - Repairs a resource
    5. DELETE - deletes a resource
  8. Add payload
  9. Save changes

Send data to Zapier through Webhooks

Video overview: API

API connections require a bit more programming to work correctly. Similar to a webhook you will use the same methods to send data from into other platforms and applications. The biggest difference between API and webhooks is that API will require authentication (typically an API key) to connect correctly. Also there will be specific URL destinations for making changes. 

Accessing your account API key

Public API documentation

The Support Team can help with basic API questions, but isn't trained at in-depth API troubleshooting. You may need to hire a developer to help you configure something using the API. If you're a developer who wants to build your own integration with YCBM, check out our API documentation.