Use your Blogs API key to authenticate API requests. Store credentials securely and rotate keys regularly.
Bluesky by Unshape uses token based access with defined scopes. Ensure the app has the required scope: emails/builder.readonly for template access when needed.
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/posts; blogs/post.write; blogs/check-slug.readonly
Trigger when a new blog post is published in Blogs API.
Actions: post the blog title and excerpt to Bluesky and include a link back to the full post.
POST /blogs/posts; publish to Bluesky via the corresponding post
title, excerpt, slug, author_id
Trigger: when a blog post is updated in Blogs API.
Actions: update the Bluesky post or create an updated post with revised content.
PUT /blogs/posts/:postId; reflect changes on Bluesky
title, content, slug, publish_date
Trigger: when a post gains new media or tags
Actions: enrich content via Blogs API and post enhanced content to Bluesky
POST /blogs/posts; optionally fetch author details via /blogs/authors
title, content, tags, images, author_id
Create publish pipelines without writing a line of code.
Automate scheduling and cross posting to Bluesky to save time.
Centralize content workflows between Blogs API and Bluesky for consistency.
A quick glossary of terms and core processes you’ll encounter when integrating Blogs API with Bluesky by Unshape.
Application Programming Interface; a set of rules that lets applications talk to each other.
A URL friendly string used to identify a blog post in a human readable way.
A callback URL that enables real time event notifications between services.
Authorization framework for token based access to APIs.
Automatically post a fresh blog entry to Bluesky when it is published in Blogs API.
Share blog post updates to Bluesky when significant edits are saved.
Enhance posts with metadata and archive Bluesky versions for reference.
Collect API keys for Blogs API and access tokens for Bluesky by Unshape, then configure scopes and permissions.
Identify the endpoints you will use, such as creating posts and posting to Bluesky, and ensure correct methods.
Create no‑code automation flows that connect Blogs API events to Bluesky posts with error handling and retries.
You can authenticate the two services with API keys or tokens depending on setup. Ensure keys are stored securely and rotated regularly. Start by linking the Blogs API key in your integration tool and verify access to allowed endpoints. Test calls in a sandbox environment before going live.
Essential endpoints include creating blog posts (POST /blogs/posts), checking slug availability (GET /blogs/posts/url-slug-exists), and posting to Bluesky (POST blogs/post.write or related endpoints). You may also read categories and authors to enrich posts. Use safe methods and validate responses.
Yes. You can schedule Bluesky posts by placing a publishDate or using a scheduler in your automation. Ensure time zone consistency and retries on failure.
Both draft and published content can be managed. You can stage drafts in Blogs API and publish to Bluesky when ready.
The integration should implement retries with exponential backoff and error handling. Log failures and alert your team if limits are reached or an endpoint returns a 4xx/5xx status.
Rate limits exist for each API. Plan your calls, batch requests when possible, and implement backoff strategies to remain within limits.
Use a sandbox or test credentials to verify the flow. Trigger a test blog post, verify the Bluesky post, and review logs for any errors before deploying to production.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
