Use your Blogs API credentials (API key or OAuth token) with the required scope (emails/builder.readonly) to authorize requests from Tidbyt to the Blogs API.
Create a Tidbyt API token and securely store it in your app connection settings to authorize data retrieval from Blogs API.
Key endpoints include: GET emails/builder, 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 post is created in Blogs API.
Action: Push a Tidbyt card with the post title and a short excerpt.
POST /blogs/posts
title, slug, excerpt, publishDate
Trigger: a blog post is updated.
Action: refresh Tidbyt card to reflect changes.
PUT /blogs/posts/:postId
postId, title, content, status
Trigger: slug validation during post creation.
Action: check slug exists with endpoint and proceed accordingly.
GET /blogs/posts/url-slug-exists
slug, postId
Automate blog updates to Tidbyt without writing code.
Get real-time display updates as posts publish or change.
Easily map blog fields to Tidbyt card content.
A quick glossary of terms used in this guide to help you understand the integration.
Application Programming Interface.
A URL-friendly version of a post title used in links.
A specific path in an API you call to perform an action.
A secure authorization framework allowing apps to access data on behalf of a user.
Display title, publish date, and a short excerpt on Tidbyt.
Create a rotating card deck that cycles through recent posts.
Feature authors with their latest posts for recognition on Tidbyt.
Obtain API keys for Blogs API and the Tidbyt app, then authorize both sides.
Choose events like new posts or updates to trigger Tidbyt cards.
Map title, excerpt, and date to Tidbyt fields and test your workflow.
No coding is required. Use the Blogs API connection in your tool to authenticate and map fields, then use triggers like new posts to populate Tidbyt cards. Start with a simple post card and expand mappings as you become comfortable. You can automate reminders and previews without writing scripts.
Yes. Use a test or sandbox mode if available, or create a draft post to validate field mappings and timing. Verify API responses and display updates on a staging Tidbyt device before going live.
Yes. Use secure tokens (HTTPS, OAuth where available), apply least privilege scopes, and store keys in a secure vault. Rotate credentials regularly and monitor access logs for unusual activity.
For the first sync, essential endpoints include GET /blogs/authors to identify authors, GET /blogs/categories for taxonomy, GET /blogs/posts/url-slug-exists to validate slugs, and POST /blogs/posts to create the initial post. These establish the core flow from Blogs API to Tidbyt.
Yes. You can connect multiple Tidbyt displays by using separate Tidbyt tokens or accounts in your app configuration, each mapped to a different display or device group. Manage them from a single integration workspace.
Scheduling is supported by content updates and digests. You can set triggers for daily or time-based updates and map multiple posts into a rotating Tidbyt card set. Test timing to ensure cadence fits your display strategy.
API keys and tokens are available in your Blogs API dashboard and your Tidbyt developer console. Store them securely, then paste into the integration settings to authorize requests. If you lose keys, revoke and regenerate them from the respective portals.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
