Authenticate requests to the Blogs API using an API key or OAuth token. Ensure your token has sufficient scope to read and write blog posts, categories, and authors.
Sakari SMS uses an API token to authorize sending messages. Keep this token secure and rotate it regularly for best security.
blogs/post.write; POST /blogs/posts; blogs/post-update.write; PUT /blogs/posts/:postId; blogs/check-slug.readonly; GET /blogs/posts/url-slug-exists; blogs/category.readonly; GET /blogs/categories; blogs/author.readonly; GET /blogs/authors; GET emails/builder; GET emails/schedule; etc.
Trigger: a new blog post is published in Blogs API
Action: send an SMS with the post title and a link through Sakari SMS
POST /blogs/posts
Required: title, content, slug, category, authorId; postId generated by API
Trigger: a blog post is updated in Blogs API
Action: SMS when important fields (title, excerpt) change
PUT /blogs/posts/:postId
Key fields: postId, title, slug, status
Trigger: daily schedule in Blogs API
Action: compile top posts and send a SMS digest via Sakari SMS
POST /blogs/posts/digest
Fields: digestDate, limit, filters
Automate post updates to subscribers without writing a line of code
Scale content distribution with automated SMS campaigns
Centralize content and messaging workflows in one place
This glossary covers API, endpoints, authentication, webhooks, and related terms to help you build your Sakari SMS and Blogs API integration.
An API is a set of rules that lets different software systems talk to each other.
An endpoint is a specific URL in an API that performs a defined function.
Authentication verifies that a request originates from a trusted source.
Payload is the data you send to or receive from an API call.
Automatically send a concise SMS with the post title and a link when a new post goes live.
Compile top posts of the week and send a single SMS digest to subscribers.
Segment your audience and trigger SMS updates when posts match topics of interest.
Generate an API key for Blogs API and securely store it.
Enable required endpoints like blogs/posts, blogs/categories, and authors.
Run test posts and verify SMS triggers.
In many setups you can connect without writing code by using prebuilt automations. However, a light touch of scripting may be needed if you want highly customized messages or complex triggers. The no-code paths still require basic configuration steps like selecting triggers and actions. You can start with built-in templates and extend later if needed.
Essential endpoints typically include creating and updating posts (blogs/posts), fetching categories (blogs/categories), and retrieving author details (blogs/authors). You may also use slug checks (blogs/check-slug.readonly) to prevent duplicates. The exact endpoints depend on your use case and the data you want to surface in SMS alerts.
Authentication is usually done via an API key or token. Include the token in the Authorization header for each request and scope it to read and write blog content as needed. Rotate credentials periodically and store them securely.
Yes. The Blogs API supports updating post fields such as title, content, and status. Deleting is typically possible via a dedicated endpoint or by updating the post to a deleted state, depending on your API provider. Check rate limits and permissions when performing edits programmatically.
Absolutely. You can customize the SMS body to include post title, a short excerpt, and a link. Use variables from the API response (title, excerpt, slug) and append a trackable URL to optimize engagement.
If you hit rate limits, throttle requests or queue posts for transmission. Implement exponential backoff and monitor API usage. Consider requesting higher limits from your API provider if your workflow requires it.
API credentials are found in the developer section of the Blogs API dashboard or your account settings. Treat credentials like passwords, store them securely, and rotate them periodically.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
