Use your API key with the required scope to securely access the Blogs API endpoints from Fliki. Store credentials securely and rotate keys regularly.
Fliki authenticates to the Blogs API using an API key and proper scopes (emails/builder.readonly for data reading, blogs/post.write for publishing).
Core endpoints include GET emails/builder, GET emails/schedule, POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/posts/url-slug-exists, GET /blogs/categories, GET /blogs/authors, and GET /blogs/posts/:postId for verification.
Trigger: when Fliki generates a new idea, create a draft post in Blogs API.
Actions: POST /blogs/posts with title, content, slug, and tags; set status to draft.
POST /blogs/posts
title, content, slug, tags, authorId, status
Trigger: update in Fliki triggers an update to an existing post.
Actions: PUT /blogs/posts/:postId with new content and slug.
PUT /blogs/posts/:postId
postId, title, content, slug, tags, status
Trigger: after publish, pull post details to confirm status.
GET /blogs/posts/:postId
postId, title, slug, status, publishedAt
Zero‑code integration with a visual workflow builder that connects Fliki actions to Blogs API endpoints.
Drag‑and‑drop triggers and actions streamline publishing and updating blog posts.
Unified data flow reduces manual steps and speeds up content automation.
This glossary defines terms and processes used in the integration, helping you implement quickly.
Application Programming Interface — a set of rules that enables software to communicate and perform actions.
Slug — the URL-friendly identifier derived from the post title used in URLs and checks.
Blog post object containing content, metadata, and publishing settings.
Method for proving identity when calling APIs, typically API keys or tokens.
Turn Fliki ideas into draft blog posts in Blogs API with one click.
Keep posts synced as changes happen in Fliki.
Schedule posts to publish at optimal times using Fliki data.
Generate an API key with the required scopes in your Blogs API dashboard.
Enter endpoint paths, methods, and authentication details in Fliki’s integration panel.
Run tests, verify post creation and updates, then go live.
A little or no coding is needed to set up the integration. Fliki provides a visual builder to connect to the Blogs API endpoints, so you can map fields like title and content without writing code. If you do have custom needs, the API is well-documented and supports standard HTTP requests. You can test endpoints in your sandbox environment before going live.
For basic publishing you typically need to access the blogs/posts creation endpoint (POST /blogs/posts) and possibly the slug check (GET /blogs/posts/url-slug-exists) to avoid duplicates. You’ll also want read access to fetch existing categories and authors as needed.
Use GET /blogs/posts/url-slug-exists to verify slug availability before creating or updating. If the slug exists, adjust the title or slug accordingly.
Yes. You can schedule posts by setting the publishAt or equivalent field in your request and configuring Fliki to trigger those publishes at desired times.
Typical scopes include blogs/post.write for publishing and blogs/check-slug.readonly for slug checks. Ensure your API key includes the minimal required scopes for your workflow.
Store API keys securely, rotate them periodically, and prefer server-side storage. Use Fliki’s secure credential handling and avoid exposing keys in client-side code.
API docs and sample requests are available in your Blogs API dashboard. Look for endpoints like POST /blogs/posts and GET /blogs/posts/url-slug-exists to get started.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
