Authenticate to the Blogs API using your API Key and OAuth token. Ensure your token has the required scope emails/builder.readonly for safe access.
To connect Beacon to the Blogs API, generate API credentials in the Beacon account and grant permission to the Blogs API. Keep keys secure and rotate periodically.
Core endpoints include GET emails/builder, POST blogs/posts, PUT blogs/posts/:postId, GET blogs/posts/url-slug-exists, GET blogs/categories, GET blogs/authors, and more. These enable content creation, updates, and metadata management from Beacon.
Trigger: When a new Beacon post is published
Actions: Create a blog post in Blogs API with the Beacon post title and content; assign slug and category; schedule publish.
POST /blogs/posts
Key fields: title, content, slug, author, category, status
Trigger: When a Beacon post is updated
Actions: Update the corresponding post in Blogs API via PUT /blogs/posts/:postId; refresh content and metadata
PUT /blogs/posts/:postId
Key fields: postId, title, content, slug, status
Trigger: When a blog post receives a comment or update in Blogs API
Actions: Retrieve post details via GET /blogs/posts/:postId and push updates to Beacon notes or comments
GET /blogs/posts/:postId
Key fields: postId, lastModified, comments, status
Automate publishing and updates without writing a line of code
Streamline content workflows from creation to publication
Maintain consistency across Beacon and Blogs API data with automated synchronization
Understand endpoints, triggers, actions, and data mapping that enable a smooth no code integration
A concrete URL and method that you call to perform a function in the API, for example GET /blogs/posts
An event in Beacon or the Blogs API that starts an automation, such as a new post created
An operation performed as part of an automation, such as creating or updating a blog post
A URL-friendly identifier for a post used in SEO and routing
Set Beacon to publish a weekly roundup post by pulling content from Blogs API via GET endpoints and formatting in Beacon templates
Push post status changes from Blogs API back to Beacon to keep teams aligned
Automatically generate a newsletter draft in Beacon from new Blogs API posts
In Beacon, create an app and copy the Blogs API key and secret
Define a trigger for new or updated Beacon posts and map actions to Blogs API endpoints
Run tests, review logs, and enable the live integration
No coding is required. The integration uses a no code connector within Beacon to trigger actions in the Blogs API. This keeps setup fast and approachable for non-developers. If you prefer, you can customize data mapping and use filters to control what posts are published.
Endpoints commonly used include GET /blogs/posts, POST /blogs/posts, PUT /blogs/posts/:postId, and GET /blogs/posts/url-slug-exists to validate slugs. You can select which endpoints to surface in your workflow.
Authentication uses API keys and OAuth tokens; store securely. Scopes determine what you can access; set emails/builder.readonly for read operations.
Yes, you can update existing posts by mapping to PUT endpoint. Be mindful of postId and slug matching to update the right post.
Map title, content, slug, and publish status from Beacon fields to Blogs API. Consider using a field mapping template to reuse across posts.
Rate limits depend on your Blogs API plan; plan for bursts. If you hit limits, implement backoff and retry logic.
For support, contact Rankr support or check your API provider’s docs. We also provide step-by-step tutorials and sample templates.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
