Bookings and Forms

All routes here need a project API key: Authorization: Bearer gi_live_.... See Authentication.

Bookings#

Read bookings created by visitors and confirm, decline, or cancel them.

• Confirming and cancelling may update Google Calendar and send email.
• Cancel accepts an optional reason. Decline accepts an optional reason and notify flag; confirm takes no body.
• Creating bookings is covered in the Booking API.

Forms and responses#

Manage forms, their pages and fields, submitted responses, private response files, and the inbox.

• Reorder endpoints take the complete ordered list of IDs.
• Each form step is one page. Keep settings.pageLayout on the step settings and settings.transition on the form settings.
• Forms return name, slug, type, status, and settings. Steps contain display and visibility data. Fields contain type, label, settings, options, contact mapping, and visibility.
• Deleting a response removes its stored values and its files.

All responses. GET /responses filters by formId and pages with limit and offset. It returns { responses, hasMore }, and each response includes formName and values.

Inbox. GET /inbox with view=review (the default) returns leads and booking requests nobody has handled yet; view=screened returns pitches and spam. Filter with formId. Each item has a kind (submission or booking) and booking details when present. Returns { items, counts: { review, screened } }. POST /inbox/:kind/:id/done removes an item from the review list; confirming or declining a booking does this automatically.

Re-labeling. PATCH /form-responses/:responseId/label sets the label to lead, review, spam, junk, or bot, and the submission leaves the review list. Marking it a lead creates the contact and runs workflows. Marking it spam, junk, or bot deletes the contact the submission created when nothing else is attached to it (notes, next action, tags, bookings, or other submissions); the response reports contactRemoved.