Authenticate requests with your Blogs API key and OAuth credentials from CASEpeer. Store credentials securely and rotate keys regularly to maintain security.
CASEpeer uses its own integration credentials to access the Blogs API. Ensure the app is authorized and that necessary permissions for posts, authors, and categories are granted.
GET /blogs/authors; GET /blogs/categories; GET /blogs/posts/url-slug-exists; POST /blogs/posts; PUT /blogs/posts/:postId; POST /blogs/posts; GET /blogs/posts; GET /blogs/post-update; GET /blogs/check-slug.readonly; GET /blogs/categories; GET /blogs/authors; GET emails/builder; POST emails/builder; GET emails/schedule; POST /emails/builder/data; DELETE /emails/builder/:locationId/:templateId; emails/schedule.readonly
Trigger: a new CASEpeer post is ready and published via POST /blogs/posts
Actions: POST /blogs/posts to create, PUT /blogs/posts/:postId to update, provide title, content, slug, authorId, and categoryId
POST /blogs/posts
Required fields: title, content, slug, authorId, categoryId
Trigger: new authors or categories added in CASEpeer update blogs/authors and blogs/categories
Actions: GET /blogs/authors and GET /blogs/categories to fetch, then map into CASEpeer
GET /blogs/authors; GET /blogs/categories
Key fields: authorId, categoryId, name
Trigger: before publish, check slug exists using GET /blogs/posts/url-slug-exists
Actions: verify slug, then POST /blogs/posts; optionally schedule using available scheduling endpoint
GET /blogs/posts/url-slug-exists; POST /blogs/posts
Key fields: slug, postId
Automates content publishing without writing code.
Keeps taxonomy and posts in sync across CASEpeer and your blog.
Speeds up editorial workflows with templates and triggers.
A quick glossary of posts, slugs, authors, categories, and the API actions used to connect CASEpeer with the Blogs API.
A blog article that can be created, edited, and published via the Blogs API.
A URL-friendly identifier derived from the post title used in the post URL.
The writer credited with a post; can be synced from CASEpeer to the blog system.
A taxonomy grouping posts by topic; used for filtering and organization.
Set up trigger-driven campaigns that publish blog posts automatically when CASEpeer events occur.
Sync authors and categories to drive a dynamic editorial schedule in CASEpeer.
Automate slug checks and SEO-friendly url creation as part of publishing tasks.
Obtain an API key for Blogs API and authorize the connection in CASEpeer.
Select posts, authors, categories, and slug check endpoints to enable publishing and syncing.
Run tests to validate data flow and error handling.
The integration lets CASEpeer trigger blog creation and updates directly through the Blogs API, removing manual steps. Use templates and mappings to control how data flows from CASEpeer to your blog platform, ensuring consistency.
No heavy coding is required; CASEpeer provides connectors and actions to simplify integration. You may need to supply API credentials and configure permissions. For advanced setups, you can customize mappings via webhooks.
Essential endpoints include POST /blogs/posts, GET /blogs/posts/url-slug-exists, and PUT /blogs/posts/:postId. Also use GET /blogs/authors and GET /blogs/categories for taxonomy alignment.
Use GET /blogs/posts/url-slug-exists to verify slug availability before publishing. If the slug is taken, adjust and retry to avoid duplicates.
Update existing posts with PUT /blogs/posts/:postId. You can also use PATCH if supported, and maintain version history as needed.
Yes. Sync authors and categories by regularly polling GET /blogs/authors and GET /blogs/categories, and schedule automated updates in CASEpeer.
Refer to the API docs and CASEpeer templates for setup guidance. If you need more help, contact support or your account manager.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
