Authenticate calls to the Blogs API using your API credentials. Use the provided API key with the appropriate scopes to access posts, categories, and authors.
Dub securely stores and rotates credentials and you’ll authorize the Dub app to access the Blogs API via OAuth2 or API key, depending on your setup.
Key endpoints include a mix of blog and emails operations such as: GET emails/builder, GET emails/schedule, POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/categories, GET /blogs/authors, GET /blogs/posts/url-slug-exists, POST /blogs/posts, POST /emails/builder/data. These endpoints power automation between Dub and the Blogs API to create, update, fetch, and schedule content.
Trigger: When new content is added or updated in Dub, automatically create a corresponding blog post in the Blogs API.
Actions: create post, attach content, set slug, assign author and category, schedule publish date.
Methods and paths: POST /blogs/posts to create; PUT /blogs/posts/:postId to update.
Key fields: title, content, slug, authorId, categoryId, publishAt.
Trigger: changes to categories or authors in Blogs API update Dub’s references.
Actions: fetch /blogs/categories and /blogs/authors; map IDs to local fields; create if needed.
Paths: GET /blogs/categories; GET /blogs/authors.
Key fields: categoryName, authorName, slug.
Trigger: when ready in Blogs API, trigger a scheduled publish in Dub.
Paths: POST /blogs/posts to create; POST /blogs/posts to schedule.
Key fields: postId, publishAt, status.
Eliminate manual data entry by automating post creation from Dub workflows.
Accelerate publishing with scheduled posts and cross-channel consistency.
Maintain brand voice by syncing authors and categories across systems.
Definitions of elements and processes used in this integration, including endpoints, authentication, data mapping, and scheduling.
A specific URL and HTTP method used to perform a defined action in the API (for example, POST /blogs/posts).
A URL-friendly string derived from the post title used in web addresses.
The process of verifying who you are to access protected API resources, commonly via API keys or OAuth.
The maximum number of API calls allowed in a given time window to protect the service.
Automatically generate draft blog posts in Blogs API when certain events occur in Dub (e.g., new contact added).
Keep author and category data synchronized between Dub and Blogs API to ensure accurate attribution.
Schedule posts from Dub on a publishing cadence that aligns with your editorial calendar.
In the Blogs API dashboard, create or locate your API key and secret, then copy them securely.
Choose OAuth or API key method, and securely store credentials in your integration tool.
Map the required fields (title, content, slug, author, category) and run a test to confirm successful data flow.
The Blogs API is the interface that lets Dub read and write blog posts, categories, and authors via API calls. It enables automation and seamless publishing between your content system and Dub. This section explains how to connect using API keys and endpoints. With proper authentication and field mapping, you can automate a complete publishing pipeline from Dub to the Blogs API.
Authentication ensures only trusted apps access your blog data. Use an API key with the correct scopes, or implement OAuth where supported, and store credentials securely in your integration tool. Rotate credentials regularly and follow the least-privilege principle to minimize risk.
Core endpoints for posting content include POST /blogs/posts to create posts and PUT /blogs/posts/:postId to update them. You may also use GET /blogs/posts/url-slug-exists to validate slugs and GET /blogs/categories or GET /blogs/authors to fetch related metadata. These endpoints give you end-to-end control from creation to publication.
Yes. You can schedule posts to publish at a future date by including a publishAt timestamp or date field when creating or updating a post. Automation can trigger scheduled publishing from Dub, ensuring consistent cadence with your editorial calendar.
No heavy coding is required. Many integrations are built using no-code tools like Zapier, connecting Dub to the Blogs API via standard HTTP actions. If you do code, you can customize mappings and error handling for robust automation.
Most APIs enforce a rate limit to protect service stability. Plan your calls (batching or pacing) and implement retry logic for transient errors. If you anticipate high volume, contact support to discuss elevated limits or optimized endpoints.
If the connection drops, check API credentials, network access, and endpoint availability. Re-authenticate if needed and retry the failed calls. Set up alerting in Dub or your automation tool to detect and recover from outages quickly.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
