Authenticate to the Blogs API using your GHL API key with the scope emails/builder.readonly. Keep keys secure and rotate regularly.
TimeRex uses OAuth‑style tokens issued by your GHL account to access Blogs API endpoints. Grant permission to the Blogs API via the integration setup and store credentials securely.
– GET emails/builder – POST emails/builder – POST /emails/builder/data – DELETE /emails/builder/:locationId/:templateId – GET emails/schedule – GET /blogs/posts/url-slug-exists – POST /blogs/posts – PUT /blogs/posts/:postId – GET /blogs/categories – GET /blogs/authors – GET /blogs/categories?limit=… (and related category endpoints) – GET /blogs/posts (list or detail as needed) – GET /blogs/post-update (metadata placeholder) – GET /blogs/check-slug.readonly
Trigger: when a new draft is saved in TimeRex, automatically create a post in Blogs via POST /blogs/posts.
Actions: POST /blogs/posts to publish, set title, content, slug; ensure slug uniqueness with GET /blogs/posts/url-slug-exists.
Method path: POST /blogs/posts
Key fields: title, content, slug, author, category, publishDate
Trigger: TimeRex edits a post; reflect changes via PUT /blogs/posts/:postId.
Actions: PUT /blogs/posts/:postId to update; check slug with GET /blogs/posts/url-slug-exists as needed.
Method path: PUT /blogs/posts/:postId
Key fields: postId, title, content, slug
Trigger: TimeRex schedules posts for automated distribution across channels.
Actions: POST /blogs/posts to create with publishTime and channels; use scheduling endpoints to manage timing.
Method path: POST /blogs/posts
Key fields: postId, publishTime, channels, status
Benefit: Build end‑to‑end content workflows without writing code.
Benefit: Rapidly publish, update, and schedule content across platforms.
Benefit: Real‑time data sync and centralized control between TimeRex and your blog.
This guide covers endpoints, triggers, actions, and data fields used to connect Blogs API with TimeRex.
Definition: A set of rules that lets TimeRex communicate with Blogs API.
Definition: A specific URL path used to perform operations on the Blogs API.
Definition: A URL‑friendly version of a post title used in post URLs.
Definition: The process and tokens used to securely authorize TimeRex to access Blogs API.
Description: Use AI to draft compelling posts in TimeRex and then publish via Blogs API.
Description: Schedule posts to multiple channels based on audience engagement data.
Description: Automatically push edits from TimeRex to Blogs API as soon as they’re saved.
Collect your Blogs API key and authorize TimeRex to access the Blogs API with the required scope.
Choose the endpoints you need (blogs/posts, blogs/categories, blogs/authors, emails endpoints if used) and map fields.
Create a test workflow in TimeRex, run a test post, verify slug, publish time, and channel distribution.
Answer: Start by authenticating TimeRex with your Blogs API key, then connect the Blogs endpoints you plan to use. TimeRex will orchestrate posts, schedules, and updates across platforms without writing code.
Answer: At minimum, you’ll need GET /blogs/posts/url-slug-exists to ensure unique slugs, and POST /blogs/posts to create posts. You may also use PUT /blogs/posts/:postId to update existing posts and GET /blogs/categories or GET /blogs/authors for metadata.
Answer: Use TimeRex scheduling to publish posts to multiple channels. TimeRex can set publishDate/time and channel assignments when you create or update a blog post.
Answer: No coding required. The integration uses pre-built actions and triggers within TimeRex; simply connect your Accounts and map fields.
Answer: Authentication uses API keys and tokens; keep credentials secure, rotate keys regularly, and follow best practices for secret management.
Answer: Yes. Update a post with PUT /blogs/posts/:postId and TimeRex will sync changes to the live post and reflect slug and content updates.
Answer: Slug checks are available via GET /blogs/posts/url-slug-exists to prevent duplicates before publishing.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
