To access Blogs API from StreetText, securely store your API key or OAuth token and grant the necessary access. Keep credentials private and rotate them regularly.
Authorize StreetText to access your Blogs data by completing the OAuth flow or by entering the API credentials in the integration settings.
blogs/post.write; POST /blogs/posts; PUT /blogs/posts/:postId; GET /blogs/posts/url-slug-exists; GET /blogs/categories; GET /blogs/authors; blogs/check-slug.readonly; GET /blogs/authors; GET /blogs/categories
Trigger: when a draft is ready in StreetText, publish a new post using POST /blogs/posts.
Actions: map title, slug, content, authorId, and categoryIds; set publish date and status.
POST /blogs/posts
title, slug, content, authorId, categoryIds, featuredImageUrl
Trigger: update a post via PUT /blogs/posts/:postId when content changes in StreetText
Actions: update title, content, slug, categories, and metadata
PUT /blogs/posts/:postId
postId, title, slug, content, categoryIds
Trigger: validate slug with GET /blogs/posts/url-slug-exists; fetch authors with GET /blogs/authors and categories with GET /blogs/categories
Actions: resolve slug conflicts, map authorId, map categoryIds
GET /blogs/posts/url-slug-exists; GET /blogs/authors; GET /blogs/categories
slug, authorId, categoryIds
Faster content publishing with automated workflows that connect StreetText campaigns to Blogs API posts.
Centralized content management across your blog, emails, and campaigns with one connection.
SEO-friendly metadata and slug handling with consistent category and author data.
Key elements include posts, slugs, authors, categories, and the endpoints that create, update, or fetch these items. The processes describe how StreetText orchestrates actions against Blogs API.
A blog entry created or stored in the Blogs API with title, content, slug, and metadata.
A URL-friendly string derived from the post title used to build the blog URL.
The writer responsible for a post; linked by authorId in the Blogs API.
A tag or grouping for posts to enable organization and filtering.
Turn high engagement StreetText campaigns into blog drafts in Blogs API and publish automatically when approved.
Repurpose blog posts into social updates or email content via StreetText using the Blogs API.
Auto-fill SEO metadata and slugs based on post content and target keywords.
Generate API credentials for Blogs API and attach to StreetText integration.
Match StreetText fields to Blogs API fields such as title, content, slug, authorId, and categoryIds.
Run test posts to verify publishing, updates, and data sync.
You can set up the connection using no-code workflow builders in StreetText by mapping fields to the Blogs API endpoints. No custom code is required to start publishing posts. The workflow handles creating posts with title and content and then returns a postId for future updates. You can test the sequence in a sandbox before going live.
Publishing a post requires using POST /blogs/posts with the post title, content, and metadata such as authorId and categoryIds. The API will return a postId you can reference for future updates with PUT /blogs/posts/:postId.
Yes. You can update posts after publishing by calling PUT /blogs/posts/:postId and supplying the fields to change, such as title, content, slug, or categories. Changes propagate to the published post.
To avoid duplicates, check slug existence with GET /blogs/posts/url-slug-exists before publishing or updating a post. This helps ensure each post has a unique URL.
Yes. The integration can fetch authors via GET /blogs/authors and categories via GET /blogs/categories, allowing you to map author and category data to posts during creation or updates.
While you can configure many aspects without code, some setup is required to map StreetText fields to the Blogs API fields and to configure authentication. A no-code builder is typically sufficient for most workflows.
Security is handled by using API keys or OAuth tokens. Store credentials securely, limit scopes to what’s needed (for example, read/write access to posts), rotate tokens regularly, and monitor access logs for unusual activity.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
