Bookd API Documentation

Effective Jan 2026

This document describes the API endpoint used by Zapier to integrate with Bookd. This is currently the only public api endpoint available to Bookd users. Other third party integrations and internal APIs are documented at the bottom of this page.

Overview

This API enables Zapier to create bookings in a Bookd account by securely identifying the correct user via an API token.

This endpoint is stable and intended specifically for Zapier integrations.

 

Base URL

https://www.bookd.biz/api/1.1/wf

 

Authentication

Zapier authenticates requests using an API token passed in the request body.

Endpoint: Create Booking

POST /zap_create_booking

 

Request Parameters:

- api_token (required)

- first_name

- last_name

- full_name

- email

- phone

- event_date

- venue

- venue_postcode

- title

- notes

 

Success Response:

Returns HTTP 200 with a JSON body including booking and contact data.

 

Error Response:

Returns HTTP 200 with success=false and an error message when authentication fails.

 

Contact Us

If you have any questions, concerns or complaints about this policy, please contact us:

 



Third-Party Integrations and External APIs

Bookd integrates with several third-party services to provide extended functionality. These integrations are managed internally by Bookd and are not exposed as standalone APIs unless explicitly documented elsewhere in this reference.

This section is provided for transparency and support purposes, particularly to clarify which functionality is handled internally versus what is available through the Bookd public API.


Google Calendar (OAuth 2.0 – Two-Way Sync)

Bookd supports a two-way calendar integration with Google Calendar using OAuth 2.0.

Purpose

  • Sync bookings and events between Bookd and a user’s Google Calendar

  • Reflect updates made in either system where applicable

Access & Scope

  • Users authenticate their own Google account within Bookd

  • Bookd requests access only to the scopes required for calendar synchronization

  • Authentication and token management are handled entirely by Bookd

API Availability

  • Google Calendar APIs are not exposed through the Bookd public API

  • Calendar data may appear in Bookd API responses as a result of synchronization

  • Third parties cannot directly manage Google Calendar connections via the Bookd API


Google Maps (Location Display)

Bookd uses Google Maps services to display and visualize event and booking locations within the application.

Purpose

  • Display addresses and map views associated with bookings or venues

  • Improve location clarity for users

API Availability

  • Google Maps APIs are used internally by Bookd

  • No Google Maps endpoints are exposed via the Bookd public API

  • Location data is surfaced only through Bookd’s own data models where applicable


Xero (Accounting Integration)

Bookd integrates with Xero to support accounting and financial workflows.

Purpose

  • Sync invoices and/or financial data between Bookd and Xero

  • Reduce manual accounting entry for users

Access & Scope

  • Users connect their own Xero account to Bookd

  • Authentication and permissions are handled internally by Bookd

API Availability

  • Xero APIs are not directly accessible through the Bookd public API

  • Accounting data may be reflected in Bookd records where supported

  • The Bookd API does not currently provide endpoints to manage Xero connections or configuration


Make (Email Forwarding and Automation)

Bookd integrates with Make (formerly Integromat) to support automation workflows, including email forwarding.

Purpose

  • Process forwarded emails

  • Automate the creation or updating of records within Bookd

  • Support advanced workflow automation

API Availability

  • Make integrations operate via supported Bookd API endpoints and/or internal processing logic

  • Email forwarding workflows are configured outside of the Bookd public API

  • The Bookd API does not expose Make-specific endpoints


Summary of API Scope

  • This documentation covers all public Bookd API endpoints available for third-party use

  • Internal systems and third-party integrations are intentionally abstracted

  • If functionality is not documented as an API endpoint, it is not currently available via the Bookd public API