Authenticate to the Blogs API from Fence Cloud by using an API key or OAuth credentials provided by your Blogs API admin. Include the credentials in each request via the Authorization header.
Fence Cloud stores and uses your credentials securely to access Blogs API. After you set up the connection, credentials can be rotated or revoked from the Connections panel.
GET emails/builder — retrieve email templates POST /emails/builder — create a new email template POST /emails/builder/data — submit email data GET /blogs/posts — fetch blog posts POST /blogs/posts — create a post PUT /blogs/posts/:postId — update a post GET /blogs/posts/url-slug-exists — check slug availability GET /blogs/categories — list categories GET /blogs/authors — list authors GET emails/schedule — read email schedules DELETE /emails/builder/:locationId/:templateId — delete an email template
Trigger: A new post is drafted in Fence Cloud and automatically published in Blogs API.
Actions: Use POST /blogs/posts to publish; map title, content, slug, author, and categories.
POST /blogs/posts
title, content, slug, authorId, categoryIds, publishDate
Trigger: Edits in Fence Cloud push updates to Blogs API.
Actions: Use PUT /blogs/posts/:postId to save edits; optionally update scheduling via blogs/schedule endpoints.
PUT /blogs/posts/:postId
postId, title, content, slug, categoryIds
Trigger: Periodic sync pulls latest authors and categories from Blogs API.
Actions: Retrieve authors via GET /blogs/authors and categories via GET /blogs/categories and map into Fence Cloud.
GET /blogs/authors
authorId, name, categoryId, categoryName
Automate publishing workflows without writing code.
Keep content in sync across platforms automatically.
Improve publishing speed and data accuracy with automated error handling.
A concise glossary of terms used in this integration, and how elements connect through endpoints and data mappings.
A specific URL path and HTTP method used to interact with a service.
The process to prove identity and authorize access to an API, typically via API keys or OAuth.
A callback URL that receives real-time event data from an API.
A URL-friendly string derived from the title used in the blog post URL.
Automatically publish new posts to social channels and newsletters when approved in Fence Cloud.
Pull author bios and category data to enrich posts during publication for richer previews.
Queue evergreen posts for re-sharing and updating over time without manual effort.
Generate credentials in the Blogs API admin panel and add them to Fence Cloud’s Connections screen.
Choose endpoints like POST /blogs/posts and GET /blogs/authors, then map title, content, slug, and metadata.
Run test requests, review responses, and deploy to production with ongoing monitoring.
No code is required. Fence Cloud provides a visual connections canvas to authenticate, map fields, and configure endpoints for the Blogs API. You can set up the integration in minutes and start automating publishing workflows. If you have developers, you can extend the setup, but it is not necessary to get started. The platform handles retries, logging, and monitoring to keep your workflow reliable.
Essential endpoints typically include POST /blogs/posts to publish, and GET /blogs/posts/url-slug-exists to prevent duplicate slugs. You may also use GET /blogs/authors and GET /blogs/categories to populate metadata during publish. Depending on your workflow, PUT /blogs/posts/:postId may be used to update posts after initial publish.
Map title to title, content to content, slug to slug, and author/category relationships to their IDs. Use Fence Cloud’s field mapping UI to align data types and apply defaults where needed. Test mappings with sample data to ensure the published posts render correctly in your channels.
Yes. You can schedule posts and manage updates by combining the blogs/schedule endpoints with post creation and update calls. Automation can trigger publishing at set times or after approvals, ensuring content goes live on a predictable schedule.
Webhooks notify Fence Cloud of events from Blogs API, enabling near real-time syncing. Configure the webhook URL in Blogs API and subscribe to relevant events such as post creation, updates, and status changes to keep data current.
If an error occurs, Fence Cloud surfaces the error details and retries according to your settings. Check the connection logs, verify credentials, and re-run failed tests to restore the workflow quickly.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
