Authorize Brivity to access the Blogs API using OAuth or an API key with the scope emails/builder.readonly, then securely store credentials in Brivity’s app settings.
In Brivity, connect to the Blogs API by entering credentials and granting access to emails, schedules, and blog endpoints required for automation.
API Endpoints for Brivity + Blogs API: GET emails/builder; POST emails/builder; POST /emails/builder/data; DELETE /emails/builder/:locationId/:templateId; GET emails/schedule; GET /blogs/posts/url-slug-exists; POST /blogs/posts; PUT /blogs/posts/:postId; blogs/post.write; blogs/check-slug.readonly; GET /blogs/categories; GET /blogs/authors; GET /blogs/posts; GET /blogs/authors; GET /blogs/categories; GET /blogs/posts/url-slug-exists; GET /blogs/categories; GET /blogs/authors
Trigger when a new blog post is created in Blogs API to auto-create or update a matching email template in Brivity’s Email Builder.
Actions: fetch post data via POST /blogs/posts; populate Email Builder template via POST emails/builder; schedule delivery if needed.
POST /blogs/posts → POST emails/builder
postId, title, slug, excerpt, content, authorId, emailTemplateId
Trigger on blog post updates to refresh related email campaigns and newsletters.
Actions: PUT /blogs/posts/:postId to update; GET /blogs/posts/url-slug-exists to verify slug; update emails/builder templates accordingly.
PUT /blogs/posts/:postId → POST emails/builder/data
postId, slug, title, updatedAt, emailTemplateId
Trigger when authors or categories change to keep campaigns aligned with content taxonomy.
Actions: GET /blogs/authors and GET /blogs/categories to pull metadata; apply to email segments and blog promos.
GET /blogs/authors; GET /blogs/categories → update email templates
authorId, categoryId, name, slug
Create powerful blog-to-email workflows without writing a line of code.
Centralize content data in one place to accelerate campaigns and reporting.
Iterate faster with real-time sync between blog posts and email templates.
This glossary defines terms and processes used in connecting Blogs API with Brivity for clarity and quick reference.
A set of endpoints and rules that allow Brivity to interact with the Blogs API securely.
A URL-friendly string used to identify a blog post in the system.
Paths in the API used to perform actions like reading emails or creating posts.
A token used to authenticate requests between Brivity and the Blogs API, typically with a defined scope.
Whenever a new post is published, automatically generate a matching email template to announce it to subscribers.
Schedule campaigns that send blog summaries via Brivity’s Email Builder on a set cadence.
Sync author data and categories to deliver targeted newsletters based on author popularity and taxonomy.
Create an API key or OAuth app in Blogs API and copy the credentials into Brivity.
Set scopes to include emails/builder.readonly and any post-related scopes your workflows require.
Run tests in a sandbox, confirm data flows between posts and emails, then deploy to production.
No specialized coding is required. Brivity provides a guided setup to connect to the Blogs API using OAuth or API keys. You configure credentials in Brivity and enable the needed scopes. Once connected, you can map blog data to email templates and campaigns. If you prefer, you can also reuse existing templates and trigger flows without touching code. During testing, verify that emails populate correctly from blog post data and that updates propagate to campaigns as expected.
Start with GET emails/builder to pull existing email templates and POST /blogs/posts to create a new post template. Then test POST /emails/builder/data to push blog content into an email template. Finally, validate the integration with a sample post to confirm end-to-end flow. As you gain confidence, expand to additional endpoints like PUT /blogs/posts/:postId for updates and GET /blogs/categories for taxonomy-aware campaigns.
Yes. Brivity uses standard OAuth or API keys to secure communication with the Blogs API. Tokens are scoped to read-only emails for most workflows, and you can tighten permissions as needed. Always store tokens securely and rotate credentials on a regular cadence. For added security, enable IP whitelisting and monitor access logs within Brivity.
Absolutely. You can trigger emails automatically when a new blog post is published by wiring POST /blogs/posts to create or update an email template in the Email Builder. Schedule these emails or deliver them immediately depending on your cadence. This ensures readers are notified of fresh content and keeps campaigns aligned with live publishing.
Slug checks prevent duplicate posts by validating a unique URL slug before publishing. Use GET /blogs/posts/url-slug-exists to verify availability, then proceed with create/update actions. If a slug already exists, Brivity can prompt you to adjust the title or slug automatically. This reduces content duplication and improves site SEO health.
Rate limits vary by endpoint and plan. To avoid throttling, stagger requests, implement exponential backoff, and batch non-urgent updates. Monitor response headers for remaining quota and gracefully retry when limits are approached. For high-volume publishers, consider spreading actions across multiple intervals and leveraging government-endorsed best practices for API usage.
To disconnect, simply remove the connected Blogs API credentials in Brivity’s integration settings and revoke the app’s access from the Blogs API console. After disconnecting, you can retain historical data for reference, but new automations will stop syncing until you re-authenticate. If you plan to reconnect later, re-run the setup flow from the beginning with fresh credentials.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
