Authenticate requests with your GHL credentials and the required scope (emails/builder.readonly) to securely access blog endpoints like creating and scheduling posts.
BoothBook connects to GHL using OAuth tokens or API keys. Tokens are stored securely and refreshed automatically to keep your connection live.
GET emails/builder; GET emails/schedule; POST emails/builder; POST /emails/builder/data; DELETE /emails/builder/:locationId/:templateId; GET /blogs/authors; GET /blogs/categories; GET /blogs/posts/url-slug-exists; GET /blogs/posts; POST /blogs/posts; PUT /blogs/posts/:postId
Trigger: A new blog post is created in Blogs API (POST /blogs/posts).
Actions: Create or update a corresponding BoothBook content block and schedule the post for publication.
Method/Path: POST /blogs/posts
Key fields: postId, title, slug, summary, content
Trigger: BoothBook’s scheduler fetches latest blogs (GET /blogs/posts) and publishes according to calendar.
Actions: Create or update BoothBook entries to reflect published posts or upcoming scheduled items.
Method/Path: GET /blogs/posts
Key fields: postId, publishDate, title, status
Trigger: When a post title or slug changes (GET /blogs/posts/url-slug-exists) to verify uniqueness.
Actions: Update BoothBook content, SEO titles, and meta descriptions using PUT /blogs/posts/:postId.
Method/Path: PUT /blogs/posts/:postId
Key fields: postId, slug, title, seoTitle, metaDescription
Automate content publishing without writing any code.
Create a centralized content workflow between your CMS and BoothBook.
Accelerate time-to-publish with reusable templates and triggers.
Core elements include endpoints, triggers, actions, authentication, data fields, and workflows that connect the Blogs API with BoothBook.
Application Programming Interface: a set of rules that lets BoothBook interact with Blogs API securely.
A specific URL path that performs a defined action in the Blogs API.
Process of proving identity and obtaining an access token to call the GHL APIs.
A URL-friendly, unique identifier for a blog post used in routing and SEO.
Automatically generate BoothBook social posts whenever a new blog post is published via Blogs API.
Sync SEO titles and meta descriptions to BoothBook for consistent multi-channel SEO.
Automatically populate BoothBook’s editorial calendar with upcoming blog posts and publishing reminders.
Collect your GHL API key and ensure the scope includes the endpoints you will use (emails/builder.readonly, etc.).
Make a test call to a safe endpoint like GET /blogs/authors and verify the response in BoothBook.
Create a BoothBook workflow that uses a blog post trigger to create or update content blocks.
A GHL API connection lets BoothBook pull and push data to Blogs API securely. It uses defined scopes to control access. This ensures only the needed data can be read or written. The connection is authenticated and tokens are refreshed automatically to maintain access.
The supported endpoints include core blog actions such as GET /blogs/authors, GET /blogs/categories, GET /blogs/posts/url-slug-exists, POST /blogs/posts, PUT /blogs/posts/:postId, and GET /blogs/posts. You can also utilize emails endpoints for related automation as needed. Endpoints outside blogs can be used for ancillary automation as you scale.
No-code setup is possible with the BoothBook app connector. You map fields and trigger events without writing code, though understanding endpoints and data fields helps to ensure a clean integration.
All connections use secure TLS, token-based authentication, and token refresh. Store credentials securely and monitor API responses to catch issues early.
Yes. You can schedule posts from BoothBook to go live at a chosen time by integrating with the Blogs API’s posting endpoints and BoothBook’s scheduler.
Slug conflicts are handled by checking existence with GET /blogs/posts/url-slug-exists before creating or updating. If a slug exists, BoothBook can revise the slug or update the existing post accordingly.
Logs for API activity are available in BoothBook’s dashboard and via the API response history. Use them to troubleshoot errors or latency and to audit data changes.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
