To authorize access you will generate an API key or OAuth credentials for the Blogs API and grant the scope for emails/builder.readonly. Use the key in requests and keep it secure.
Radius Agent uses the provided credentials to authenticate with the Blogs API. Ensure the scope matches emails/builder.readonly and test calls from your Zapier connector.
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; POST /blogs/posts; GET /blogs/categories; GET /blogs/authors
Trigger: New blog draft is ready in Blogs API and can be pushed to Radius Agent for posting.
Actions: Use POST /blogs/posts to create a post, populate title and content, then set slug and metadata.
POST /blogs/posts
title, content, slug, authorId, categoryId
Trigger: New or updated category or author in Blogs API
Actions: GET /blogs/categories and GET /blogs/authors to fetch lists, then map to Radius Agent
GET /blogs/categories
id, name
Trigger: When drafting a post check slug exists in Blogs API
Actions: GET /blogs/posts/url-slug-exists to verify, then GET /blogs/posts to retrieve post data
GET /blogs/posts/url-slug-exists
slug, postId
Automate publishing and updating posts without touching code
Keep content in one place with a single source of truth
Faster go live with templates and automatic slug creation
Elements and processes describe endpoints, authentication, mapping data, and error handling
A URL friendly version of a post title used in links
A specific API URL to perform an action or fetch data
Make a blog post live via the API
Real time notifications when data changes
Use Radius Agent triggers to create outlines and draft posts in Blogs API
Sync categories and authors for consistent taxonomy
Auto create slugs and SEO metadata
Obtain API keys, set scope emails/builder.readonly, and test basic calls
Connect endpoints and map fields in your Zapier workflow
Run tests, verify data, and enable automation
Authentication for the Blogs API is handled through a secure API key or OAuth credentials. You will provide the key in your requests and grant the necessary scopes. Always store credentials securely and rotate them regularly. Verify access by making a simple test call to a non destructive endpoint like GET blogs/categories. This confirms that your connection is live and authorized. If errors occur, check that the scope matches emails/builder.readonly and that the endpoint path is correct.
To publish a post you typically use the endpoint POST /blogs/posts. Provide the post title, content, slug, and metadata such as authorId and categoryId. Validate the slug with GET /blogs/posts/url-slug-exists before publishing to avoid duplicates. You can also update an existing post with PUT /blogs/posts/:postId. Use a test post to confirm formatting and field mapping.
Yes. Radius Agent can fetch and map lists for categories and authors using GET /blogs/categories and GET /blogs/authors. You can create or update local references in Radius Agent to keep taxonomy in sync. This helps ensure your posts always reference valid categories and authors.
Slug existence checks are available via GET /blogs/posts/url-slug-exists. If the slug is already in use, you should generate a new slug before publishing. Implement a small loop in your workflow to retry with a unique slug if needed. This prevents duplicate URLs and improves SEO stability.
Yes. No code testing is possible through Zapier or a test environment you set up. Create a test workflow that invokes the publish endpoint with sample data, inspect the response, and adjust mappings. Use test data to validate field alignment and error responses before going live.
Common errors include authentication failures, invalid endpoint paths, and missing required fields. Implement retries with exponential backoff for transient errors. Log responses and map error codes to friendly messages in your automation so you can quickly diagnose issues.
Endpoint documentation is available in the Blogs API reference. It covers available endpoints, required fields, and example requests. You can also view sample payloads and response schemas to help with field mapping and integration testing.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
