Generate a secure API key in the Blogs API dashboard and grant Studio Pro the required permissions to read, create, and update blogs and emails.
In Studio Pro, add a new connection for the Blogs API and paste your API key to establish a trusted link.
Endpoint1: GET emails/builder — Retrieve email templates and builders. Endpoint2: emails/builder.write — Create or update email templates. Endpoint3: POST emails/builder — Configure a new email builder. Endpoint4: POST /emails/builder/data — Submit builder data. Endpoint5: DELETE /emails/builder/:locationId/:templateId — Delete a specific email template. Endpoint6: emails/schedule.readonly — Read-only access to email schedules. Endpoint7: GET emails/schedule — Retrieve scheduled emails. Endpoint8: blogs/post.write — Write access for blog posts. Endpoint9: POST /blogs/posts — Create a blog post. Endpoint10: blogs/post-update.write — Update a blog post. Endpoint11: PUT /blogs/posts/:postId — Update a specific post. Endpoint12: blogs/check-slug.readonly — Check slug availability. Endpoint13: GET /blogs/posts/url-slug-exists — Verify slug existence. Endpoint14: blogs/category.readonly — Read blog categories. Endpoint15: GET /blogs/categories — Get list of categories. Endpoint16: blogs/author.readonly — Read blog authors. Endpoint17: GET /blogs/authors — Get authors.
Trigger: When a new blog post is published (POST /blogs/posts).
Actions: Create an email draft, schedule it, or update templates using the emails builder.
Methods: POST /blogs/posts to publish, PUT /blogs/posts/:postId to update, GET /blogs/posts/url-slug-exists to validate slug.
Key fields: postId, slug, title, excerpt, content, authorId.
Trigger: Schedule events from blogs/schedule and emails/schedule.
Actions: Push posts to email builder or publish on set times.
Methods: GET emails/schedule, POST /blogs/posts (for scheduled content), GET /blogs/posts/url-slug-exists.
Key fields: scheduleId, postId, sendAt.
Trigger: Weekly digest generation from published posts.
Actions: Compile posts into a digest email using the emails builder and schedule.
Methods: GET /blogs/posts, POST /emails/builder, POST /blogs/posts to generate digest.
Key fields: digestId, postIds, publicationDate.
Automate content workflows without writing code.
Keep data in sync across blog posts, emails, and campaigns.
Speed up go-to-market with ready-made templates and triggers.
Key elements include endpoints, authentication, triggers, actions, and data fields used to connect Blogs API with Studio Pro.
Application Programming Interface: a standard set of rules that allows software applications to communicate.
A blog entry published via the Blogs API with content, title, and metadata.
A URL-friendly identifier derived from the post title used in the slug field.
A specific URL path in the API that performs an action such as create, read, update, or delete.
When a new post is created, Studio Pro automatically assembles and queues a targeted email to subscribers.
Aggregate recent posts into a digest and send on a schedule.
Validate slugs before publishing and auto-correct duplicates via endpoints.
In Blogs API, generate an API key and store it securely for Studio Pro.
In Studio Pro, add a new connection and paste your API key, then test the connection.
Create triggers and actions to automate posts and emails across endpoints.
You authenticate by adding your Blogs API key to the Studio Pro connection. Use the key from your Blogs API dashboard and select the appropriate access level (read/write). Studio Pro securely stores and uses that key to sign requests to endpoints like POST /blogs/posts and GET /blogs/posts/url-slug-exists.
To publish, use POST /blogs/posts to create a post, and PUT /blogs/posts/:postId to update an existing post. Ensure the slug is unique by checking with GET /blogs/posts/url-slug-exists.
Yes. Use the blogs/schedule endpoints to plan publish times and the emails/schedule to plan campaigns that accompany posts.
Emails require builder access; ensure you have builder.write permission for creating templates. The key fields for templates include name, subject, and content.
A single API key can be used across apps, but for security you can generate separate keys for each integration. Rotate keys regularly.
Use GET /blogs/posts/url-slug-exists to verify slug availability before publishing. If it exists, modify the slug or update the existing post.
Yes. Studio Pro provides a test/sandbox mode to simulate requests without affecting live data. Use a development workspace or sandbox environment.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
