Requests to the Blogs API require a valid access token. Use Bearer tokens in the Authorization header or an API Key as a header when required. Keep credentials secure and rotate regularly.
In SwagUp, generate a Private App API Key for connecting to the Blogs API. Store this key securely (e.g., in your vault or environment variables) and reference it in your Zapier workflow or integration step.
Endpoint list (selected): – GET emails/builder – POST emails/builder – POST /emails/builder/data – DELETE /emails/builder/:locationId/:templateId – GET emails/schedule – PUT /blogs/posts/:postId – POST /blogs/posts – POST /blogs/post-update.write – GET /blogs/posts/url-slug-exists – GET /blogs/categories – GET /blogs/authors – GET blogs/categories – GET blogs/author.readonly – GET /blogs/authors – GET /blogs/check-slug.readonly Note: You may not use all endpoints in every flow.
Trigger: When a new draft is ready in SwagUp, create a blog post via POST /blogs/posts.
Actions: map title, content, excerpt, slug, and publish status to POST /blogs/posts; set authorId via /blogs/authors if needed; attach category.
Method/Path: POST /blogs/posts
Key fields: title, content, slug, authorId, categoryId, excerpt
Trigger: Updated content in SwagUp triggers PUT /blogs/posts/:postId
Actions: call PUT /blogs/posts/:postId with new content; update slug if changed; refresh metadata
Method/Path: PUT /blogs/posts/:postId
Key fields: postId, title, content
Trigger: New categories or authors created in Blogs updates SwagUp
Actions: fetch categories/authors via GET /blogs/categories and GET /blogs/authors and map to SwagUp fields
Method/Path: GET /blogs/categories and GET /blogs/authors
Key fields: categoryId, name; authorId, name
No-code setup lets non-developers automate content workflows quickly.
Automations reduce manual publishing and data entry.
Centralized mapping ensures brand consistency and SEO tuning.
This glossary defines essential terms and the processes used to connect the Blogs API with SwagUp, with quick-reference definitions.
API: A set of rules that lets SwagUp talk to the Blogs API to create, fetch, update, and manage blog posts, categories, and authors.
Webhook: A real-time notification sent from Blogs API to SwagUp when content changes occur.
Authentication: The method used to prove identity, typically API keys or OAuth tokens, required to call endpoints.
Slug: A URL-friendly version of a post title used to construct human-readable URLs.
Automatically pull top posts from Blogs API and republish a weekly roundup in SwagUp newsletters.
Use predefined templates to generate SEO-friendly posts in Blogs API from SwagUp draft content.
Automatically share new blog posts to connected social channels via SwagUp.
Create a Private App in SwagUp and generate an API key; store securely.
Test the connection by calling a simple endpoint (e.g., GET /blogs/categories) to verify access.
Create a Zapier-like workflow to post new SwagUp drafts to Blogs API using POST /blogs/posts.
You need a valid API key or OAuth token from Blogs API and a Private App key from SwagUp. Store credentials securely and rotate them regularly. Ensure your account has access to the required endpoints.
For basic publishing, start with creating posts (POST /blogs/posts) and updating them (PUT /blogs/posts/:postId). You’ll also want to check slug existence (GET /blogs/posts/url-slug-exists) and category listing (GET /blogs/categories).
Yes. Use PUT /blogs/posts/:postId to update title, content, or slug after publishing. Include the postId in the path and pass the updated fields in the body.
To ensure SEO-friendly slugs, update the slug value in your request. You can verify a slug via GET /blogs/posts/url-slug-exists before creating or updating a post.
No-code tools can handle this integration through prebuilt actions and webhooks. You don’t need to write code unless you want a highly customized flow.
Categories are listed with GET /blogs/categories and authors with GET /blogs/authors. Map these values into your SwagUp workflow to tag and attribute posts correctly.
Test the connection by running a small flow that creates a post or checks slug availability. Review any error messages and adjust headers or data mapping accordingly.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
