Obtain an API key with the scope emails/builder.readonly to access content and templates within Blogs API. Store credentials securely, rotate keys regularly, and use them only over secure connections.
Generate a service token for SolarWinds Service Desk to securely call Blogs API endpoints. Use OAuth where supported and keep tokens confidential.
Endpoints involved include: GET /emails/builder, POST /emails/builder, POST /emails/builder/data, DELETE /emails/builder/:locationId/:templateId, GET emails/schedule, GET /blogs/posts, POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/posts/url-slug-exists, GET /blogs/categories, GET /blogs/authors, GET /blogs/category.readonly, GET /blogs/author.readonly, POST /blogs/post-update, and GET /blogs/posts/url-slug-exists.
Trigger: When a ticket is marked as blog-ready, create a new post in Blogs API.
Actions: POST /blogs/posts to publish; verify unique slug with GET /blogs/posts/url-slug-exists; optionally update later with PUT /blogs/posts/:postId.
POST /blogs/posts
title, content, excerpt, slug, author_id, category_id
Trigger: A SolarWinds ticket update requires a blog post update.
Actions: PUT /blogs/posts/:postId to apply changes; check slug existence with GET /blogs/posts/url-slug-exists; refresh metadata as needed.
PUT /blogs/posts/:postId
postId, title, content, slug, category_ids, author_id
Trigger: New draft is created in Blogs API and needs category/author mapping.
Actions: GET /blogs/categories and GET /blogs/authors to map category_id and author_id for the post.
GET /blogs/categories
category_id, author_id
Fast, drag-and-drop automations let you connect posting, updating, and routing without writing code.
Publish posts, schedule updates, and trigger notifications with simple workflows.
Centralized control of categories and authors improves governance and consistency.
This glossary explains the core terms and workflows used to connect Blogs API with SolarWinds Service Desk, including authentication, endpoints, and data mappings.
Application Programming Interface: a set of rules that enables two applications to communicate and exchange data.
A callback URL that triggers when a defined event occurs in a system.
An authorization framework that allows secure access to APIs without sharing passwords.
A URL-friendly string used to identify a blog post.
Automatically publish release notes from SolarWinds tickets to Blogs API when a product update is approved.
Create blog posts from customer tickets and testimonials to showcase wins.
Push a daily digest of support milestones to an internal blog post.
Create API credentials with the required scope and authorize the connection.
Link POST /blogs/posts and PUT /blogs/posts/:postId, plus slug checks and category/author lookups.
Create no-code flows to trigger blog actions from SolarWinds events and schedule posts.
Yes. You can publish blog posts from SolarWinds Service Desk by creating a blog post via POST /blogs/posts. This creates a new entry in Blogs API. You can also publish drafts and then move them to published status as part of your automation. The setup uses no-code workflows to trigger the publish action when a ticket reaches the blogging stage.
Use an API key with the appropriate scope for Blogs API (such as emails/builder.readonly for content access) and securely manage tokens. If supported, you can also implement OAuth for ongoing secure access without exposing credentials. Rotate keys regularly and apply least-privilege access.
For basic publishing, you’ll typically need POST /blogs/posts to create posts, GET /blogs/posts/url-slug-exists to ensure a unique slug, and optionally PUT /blogs/posts/:postId to make updates. You may also reference GET /blogs/categories and GET /blogs/authors to populate mapping fields.
Use GET /blogs/posts/url-slug-exists to check if a slug is already in use before creating or updating a post. This helps avoid collisions and maintain clean URLs. If the slug exists, you can generate a new slug or update the existing post by its ID.
Map authors and categories by querying GET /blogs/authors and GET /blogs/categories. Use the returned IDs to set author_id and category_id on your posts. This ensures proper attribution and organization within the Blogs API.
Yes. You can schedule posts through automation by setting up a trigger that publishes at a specified time or after a defined delay. Scheduling is typically handled within your no-code workflow and uses the Blogs API create/post update actions at the desired time.
No-code solutions are excellent for standard workflows, but complex data transformations, advanced validations, or deeply customized logic may require lightweight scripting. Be mindful of API rate limits and ensure your automations gracefully handle errors and retries.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
