Learn how to obtain API credentials, set the correct scopes, and securely refresh tokens so MDirector can manage blog posts via the Blogs API.
MDirector must be granted the proper permissions to call the Blogs API endpoints, with read/write access aligned to your publishing needs.
– GET emails/builder – GET emails/builder.write – POST emails/builder – POST /emails/builder/data – DELETE /emails/builder/:locationId/:templateId – emails/schedule.readonly – GET emails/schedule – 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
Trigger when a new blog draft is ready in MDirector to push to Blogs API.
Actions: create post, set slug, publish, and schedule if needed.
Endpoint path: POST /blogs/posts or PUT /blogs/posts/:postId
Key fields: title, content, author, category, slug, publishDate
Trigger on new or updated posts to pull content into MDirector.
Actions: fetch posts via GET /blogs/posts, map fields, store locally, and trigger retargeting.
Endpoint path: GET /blogs/posts, GET /blogs/categories
Key fields: postId, title, slug, date, status
Trigger: monthly audit of posts and SEO health.
Actions: run checks via GET /blogs/check-slug.readonly, generate a report, notify teams.
Endpoint path: GET /blogs/authors, GET /blogs/categories
Key fields: slug existence, author, category, read/write permissions
No coding required: configure automations with drag-and-drop logic and API calls.
Real-time publishing and updates across channels from a single workflow.
Scalability across multiple endpoints and team permissions without custom scripts.
Definitions of core terms and how they fit into the integration lifecycle.
Application Programming Interface; a set of rules that enables software components to communicate.
A specific URL path for an API operation.
Authorization framework allowing apps to access user data with consent.
A URL-friendly string derived from a post title used in the URL.
Pull items from a news feed and publish them as blog posts using POST /blogs/posts with mapped fields.
Generate weekly recap posts and schedule distribution to email campaigns via Blogs API endpoints.
Regularly check slug availability and post health, sending alerts when improvements are needed.
Obtain API keys and set the proper scopes (emails and blogs) for MDirector to access the Blogs API.
Select endpoints from the list and map fields such as title, content, category, and slug to MDirector fields.
Run tests to verify post creation, slug checks, and publish flow; then deploy the automation to production.
You’ll need a set of API keys with at least read/write access to the blogs and emails endpoints. Ensure the OAuth scopes match the operations you intend to run (read for viewing content, write/publish for posting). Keep keys secure and rotate them periodically.
Yes. In the integration settings you can restrict which endpoints are exposed to MDirector. Start with essential endpoints like POST /blogs/posts and GET /blogs/categories, then expand as needed while monitoring security and rate limits.
Use the slug check endpoint GET /blogs/posts/url-slug-exists to verify slug availability before publishing. If the slug exists, you can auto-generated alternate slugs or update existing posts.
Common mappings include: title -> post title, content -> body/content, author -> authorId, category -> categoryId, slug -> slug, publishDate -> publish date. You may also map status and featured fields as supported.
Create a test project or sandbox workflow, publish a draft, and verify the response. Use non-production data, enable verbose logging, and monitor endpoint responses for errors before going live.
To disconnect, remove the API credentials from the MDirector integration settings and revoke access in the API provider. To reconfigure, re-create keys, re-authorize, and re-map fields as needed.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
