Use your Blogs API keys to grant Chiirp access so you can read and write blog data from Chiirp.
Grant Chiirp permission to operate on your Blogs API account with OAuth or token based flow.
Core endpoints include GET emails/builder, GET emails/schedule, POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/posts/url-slug-exists, GET /blogs/categories, GET /blogs/authors, and POST /blogs/posts data related actions as needed.
Trigger: a new draft is created in Chiirp and ready to publish
Actions: create a blog post in Blogs API, set slug, and publish when approved
Endpoint path: POST /blogs/posts
Key fields: title, content, author, category
Trigger: post changes detected in Chiirp
Actions: update post via PUT /blogs/posts/:postId, sync slug and metadata
Endpoint path: PUT /blogs/posts/:postId
Key fields: postId, title, content
Trigger: slug created or checked before publish
Actions: verify URL slug with GET /blogs/posts/url-slug-exists and assign category via GET /blogs/categories
Path: GET /blogs/posts/url-slug-exists
Fields: slug, category
Faster content shipping without writing code.
Reliable data sync between Apps with minimal setup.
Scalable publishing with built in validation and retries.
A quick glossary of core terms and processes used when connecting Chiirp to Blogs API.
Application Programming Interface, a set of rules that lets apps talk to each other.
A URL friendly version of a post title used in the web address.
The process of granting access to an application after identity verification.
A specific URL in an API that performs an action or returns data.
Whenever a draft is ready, push a posting plan to social channels to boost reach.
Notify subscribers when a new post goes live to drive traffic.
Slice blog content into newsletter snippets for reuse.
Generate an API key or use OAuth to authorize Chiirp to access Blogs API resources.
Choose the endpoints you need such as creating and updating posts and checking slug availability.
Test in a staging environment, then deploy to production with monitoring.
Chiirp is a no code integration that connects your Blogs API account to Zapier workflows. It lets you pull and push blog data without writing code. To get started, generate API credentials in Blogs API and authorize Chiirp in the connector settings so your workflows can read and write posts, authors, categories, and related data.
No coding is required. The Chiirp connector provides a UI based setup to map fields and select endpoints. If you need more control, you can add filters and paths in Zapier to tailor when actions run.
For publishing, essential endpoints include POST /blogs/posts to create posts, PUT /blogs/posts/:postId to update, GET /blogs/posts/url-slug-exists to ensure unique slugs, and GET /blogs/categories and GET /blogs/authors to assign metadata. You can also read or write blog data using blogs/post.write or blogs/post.update.write as needed.
Use OAuth2 or API tokens and store credentials securely. Restrict the scope to only what you need, rotate credentials regularly, and enable logging and alerts for suspicious activity. If your setup includes multiple teams, consider separate keys per environment.
Yes. Posts can be updated after publishing using PUT /blogs/posts/:postId. Slug changes can trigger slug regeneration and you can recheck slug availability before publishing new versions. Always maintain a postId reference to keep data in sync.
Slug conflicts are resolved by checking availability via GET /blogs/posts/url-slug-exists. If a slug already exists, you can auto generate a unique slug or append a numeric suffix. This prevents collisions and preserves SEO value.
Official documentation for the Blogs API and Chiirp connector is available in the developer docs and the Rankr help center. If you need further guidance, contact Rankr support for a walkthrough.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
