Begin by obtaining an API key for the Blogs API and granting read/write permissions as needed. Use these credentials in your Loomly connector configuration to establish a secure connection.
Authorize Loomly to access your Blogs API account via OAuth or API key pairing. Follow prompts to complete setup, then test a sample post to verify the connection.
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; POST /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 Loomly drafts a post, push to Blogs API to create a new blog post.
Actions: call POST /blogs/posts, then verify slug with GET /blogs/posts/url-slug-exists.
POST /blogs/posts
title, content, slug, authorId, categoryId
Trigger: a scheduling event in Loomly signals a post should go live.
Actions: schedule via GET /blogs/posts/url-slug-exists and then use PUT /blogs/posts/:postId to update timing as needed.
GET /blogs/posts/url-slug-exists
slug, postId, status
Trigger: when a new author or category is added in Loomly, fetch from blogs/authors and blogs/categories.
Actions: retrieve authors (GET /blogs/authors) and categories (GET /blogs/categories) and map to Loomly.
GET /blogs/authors and GET /blogs/categories
authorId, categoryId
Automate publishing and updates without writing a line of code.
Streamline workflows across Loomly and your blog platform for consistent branding.
Save time with reusable templates and field mappings that speed up publishing.
This section covers endpoints, authentication, triggers, and field mapping used to connect Loomly with the Blogs API.
Application Programming Interface — a set of rules that lets applications communicate and share data.
A specific URL path and HTTP method that performs a defined action in an API.
The process of verifying identity to grant access to an API.
A URL-friendly version of a post title used in the web address.
Link Loomly briefs to blog topics and use the Blogs API to auto-create posts when a brief is approved.
Publish to blog and newsletter channels using synchronized endpoints to keep all channels up-to-date.
Use slug checks and automated updates to keep posts optimized for search engines over time.
Obtain API keys from the Blogs API and connect Loomly’s app connector.
Define when to create, update, or schedule posts across Loomly and Blogs API.
Map title, slug, content, author, and category between Loomly and the Blogs API.
Loomly connects to the Blogs API using API keys or OAuth, depending on what your setup supports. You’ll authenticate once, then Loomly can perform operations like create, update, and schedule posts. If your credentials expire, simply re-authenticate to restore access. This keeps your publishing flow uninterrupted. The integration is designed for non-developers, so you can manage settings from Loomly’s UI without coding.
Key endpoints include POST /blogs/posts for creating posts, GET /blogs/posts/url-slug-exists to validate slugs, and PUT /blogs/posts/:postId to update posts. For scheduling, use blogs/post-update.write and GET /blogs/posts/url-slug-exists to prevent duplicates. If you manage emails or other content, you can combine endpoints like GET emails/builder to support cross-channel workflows.
Slug checks are performed via GET /blogs/posts/url-slug-exists prior to creation. If the slug already exists, you can modify the title or slug in Loomly and retry. This helps prevent duplicate content and keeps URLs clean for SEO. You can also rely on slug generation rules in Loomly to maintain consistency.
Yes. You can pull authors and categories using GET /blogs/authors and GET /blogs/categories, then map those fields to Loomly’s post templates. This ensures author attribution and category taxonomy stay in sync across both platforms.
Map fields such as title, content, slug, authorId, and categoryId from Loomly to the corresponding Blogs API fields. Use the API documentation to align field names and data types. Regularly review mappings as your content strategy evolves.
If a post fails to publish, check the error response from the Blogs API for the exact cause (authentication, invalid fields, or slug conflicts). Correct the issue in Loomly and retry. You can also set up retries or alerts in Loomly to catch failures quickly.
Rate limits depend on yourBlogs API plan. Monitor responses for 429 status codes and implement backoff retry logic in your workflow. When in doubt, stagger post creation and scheduling to stay within limits while maintaining throughput.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
