Authenticate to the Blogs API using your API key with the scope emails/builder.readonly to access templates and posting data from the Blogs API to Mobile Message.
Connect Mobile Message to the Blogs API using OAuth or API keys as supported, then grant permission to read and push blog updates into Mobile Message channels.
Key endpoints you will use include: 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/post.write; POST blogs/posts; PUT blogs/posts/:postId; GET /blogs/posts; GET /blogs/categories; GET /blogs/authors.
Trigger: when a new blog post is created in Blogs API, push a notification and optionally schedule a mobile message.
Actions: create a post in blogs, push to Mobile Message, trigger a notification sequence.
Method Path: blogs/posts POST and blogs/posts/:postId PUT to update; emails/builder endpoints to format messages.
Key fields: postId, title, slug, excerpt, content, author, publishDate.
Trigger: a template update in Blogs API triggers updates to the Mobile Message email builder.
Actions: pull templates, update emails/builder templates, clear caches.
Method Path: GET emails/builder and POST /emails/builder/data; DELETE /emails/builder/:locationId/:templateId.
Key fields: templateId, locationId, templateName, content, subject.
Trigger: when a blog post is scheduled in Blogs API, publish to Mobile Message channels.
Actions: publish, notify subscribers, track delivery.
Method Path: GET emails/schedule; POST blogs/posts; PUT blogs/posts/:postId.
Key fields: scheduleId, postId, publishTime.
Benefit 1: Build sophisticated workflows without writing code.
Benefit 2: Automate content driven communications across channels.
Benefit 3: Real time insights and fast iteration.
This section defines the critical elements and processes involved in linking Blogs API with Mobile Message.
A specific URL path that performs an action in an API.
A method for delivering real time data from one app to another.
The process of verifying identity to access APIs.
A URL friendly version of a post title used in links.
Capture reader interest and enroll them into mobile campaigns automatically.
Summarize longer posts into concise messages for mobile channels.
Deliver author specific updates to readers based on their interests.
Obtain API keys for Blogs API and grant Mobile Message access to read and post data.
Set up endpoint calls for blogs/posts, emails/builder, and schedules.
Create workflows that publish posts, send alerts, and track results in Mobile Message.
To authenticate, obtain an API key for the Blogs API and authorize Mobile Message to access the required scopes. Use the provided credentials to secure your requests. Ensure your environment uses HTTPS and stores keys securely. You may also configure OAuth if your setup supports it. After authentication, test a simple read of templates to verify access.
You typically need endpoints for creating and updating posts, fetching templates, and scheduling messages. Commonly used endpoints include blogs/posts, emails/builder, and emails/schedule. Depending on your workflow, you may also use the slug check and author/category endpoints for validation and categorization.
Yes. You can set up schedules that trigger blog alerts to Mobile Message channels at defined times or when posts go live. Use the blogs posts and emails schedule endpoints to coordinate timing and delivery. This helps keep your audience engaged with timely updates.
No fully manual coding is required for many scenarios. UIs and webhooks let you connect without writing code. For advanced automations, you can use simple scripts or a no code automation platform to orchestrate API calls between Blogs API and Mobile Message.
Templates can be synchronized by pulling template data from the Blogs API and pushing updates to the Mobile Message email builder. Regularly refresh templates and ensure subjects, content blocks, and styles map correctly to the Mobile Message templates.
Typical required fields include postId, title, slug, content, and publishDate. Ensure author and category data are available if you want personalized or segmented alerts. Validation of slug existence helps prevent duplicates.
Delivery analytics are shown in your Mobile Message dashboards and can be complemented by API event logs. Track opens, clicks, and deliveries for blog alerts, and use these insights to refine timing and content.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
