To authorize access to the Blogs API from Zakeke, configure an OAuth flow or API keys and ensure the requested scope is granted (emails/builder.readonly).
Within Zakeke, set up an app connection for the Blogs API using the client credentials provided by your Blogs API account, and assign the correct permissions for reading and writing blog data.
Key endpoints used in this integration include: GET emails/builder, POST emails/builder, POST /emails/builder/data, DELETE /emails/builder/:locationId/:templateId, GET emails/schedule, POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/posts/url-slug-exists, GET /blogs/categories, GET /blogs/authors.
Trigger: New blog post is created in Blogs API
Actions: Create a corresponding post in Zakeke, publish to product pages or marketing content, and notify teams
Endpoint: POST /blogs/posts
Key fields: slug, title, content, authorId, publishedAt
Trigger: Blog post updated in Blogs API
Actions: Update the matching Zakeke post, preserve history, and refresh related content
Endpoint: PUT /blogs/posts/:postId
Key fields: postId, slug
Trigger: New blog post is created but slug exists
Actions: Validate slug, prompt for alternate slug, or auto-suggest a unique slug
Endpoint: GET /blogs/posts/url-slug-exists
Key fields: slug
Build complex workflows without writing code using a visual builder
Automate publishing and updates between Blogs API and Zakeke for consistent content
Centralize control in a single connector to speed up deployments
Core elements and processes include API endpoints, authentication, triggers, actions, and data mapping between Blogs API and Zakeke.
An interface that allows Blogs API and Zakeke to communicate and exchange data programmatically.
A URL-friendly identifier for a blog post used in links and routing.
A blog entry created in Blogs API that can be published or updated in Zakeke.
A specific URL path that performs an action in the API.
Automatically push new blog posts from Blogs API to Zakeke product updates or marketing content.
Keep product pages and blogs in sync with minimal setup using webhooks.
Enforce consistent slugs and metadata across both platforms with automated checks.
Obtain API keys from the Blogs API and register the Zakeke app in your dashboard.
Select the relevant endpoints (posts, slug checks, categories) and map fields.
Run tests, monitor logs, and enable automation in production.
No coding is required to set up the integration. The no-code connector provides triggers, actions, and mappings in a visual builder. You can configure the flow with a few clicks and test it in a sandbox before going live.
Key endpoints include: GET emails/builder, POST emails/builder, POST /emails/builder/data, DELETE /emails/builder/:locationId/:templateId, GET emails/schedule, POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/posts/url-slug-exists, GET /blogs/categories, GET /blogs/authors. Map blog fields to their Zakeke counterparts to keep data in sync.
Use a secure API key or OAuth flow. The Blogs API should grant the scope emails/builder.readonly (and any write scopes if you plan to publish or update content). Ensure tokens are rotated regularly and stored securely in Zakeke.
Use the slug-exists endpoint to check for duplicates before creating a post. If the slug is taken, you can auto-suggest an alternative or prompt the user to adjust the title. This prevents broken links and SEO issues.
Yes. You can map fields such as slug, title, content, author, categories, and published date from Blogs API to the corresponding Zakeke content fields, enabling consistent display across platforms.
Test the integration in a staging environment by triggering sample posts and updates. Monitor webhook activity and API responses, then review mappings and error handling before going live.
Endpoint documentation for the Blogs API and the Zakeke app connector is available in your developer portal and the API reference. Review the endpoints, authentication methods, and data mappings to maximize reliability.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
