Securely authenticate DocsBot AI to the Blogs API using API keys or OAuth. Keep credentials secret, set appropriate scopes, and rotate keys regularly.
DocsBot AI will use a secure credential method compatible with your workflow. Configure the method in your project settings and apply the Blogs API scope to access emails and blogs.
Key endpoints include: GET emails/builder, POST emails/builder, POST /emails/builder/data, GET emails/schedule, PUT /blogs/posts/:postId, POST /blogs/posts, GET /blogs/posts/url-slug-exists, GET /blogs/categories, GET /blogs/authors, GET /blogs/posts, etc.
Trigger: new DocsBot AI draft is finalized to publish as a blog post and send a confirmation email.
Actions: create or update a blog post via POST /blogs/posts, populate email templates with POST /emails/builder/data.
Method examples: POST /blogs/posts, GET emails/builder, POST /emails/builder/data
Key fields: postId, title, slug, locationId, templateId
Trigger: schedule publish and mail go out at a set time.
Actions: publish posts with PUT /blogs/posts/:postId and send email with GET /emails/builder.
Method examples: PUT /blogs/posts/:postId, GET /blogs/posts/url-slug-exists
Key fields: postId, publishDate, slug
Trigger: draft changes saved triggers a validation pass.
Actions: check slug uniqueness via GET /blogs/posts/url-slug-exists and update post with PUT /blogs/posts/:postId.
Method examples: GET /blogs/posts/url-slug-exists, PUT /blogs/posts/:postId
Key fields: slug, postId, status, lastEdited
Create blog posts from templates without writing code.
Automate email campaigns using blog data and newsletters.
Schedule posts and emails with simple triggers and dashboards.
This glossary covers common terms you’ll see when connecting APIs, including endpoints, methods, triggers, and fields.
Application Programming Interface: a defined method to interact with a service.
A URL path and HTTP method that performs an action on the API.
A URL-friendly identifier for a blog post.
Make a blog post visible on your site or feed.
Generate blog posts with DocsBot AI and automatically assemble newsletters using GET emails/builder and POST /emails/builder/data.
Create drafts, check URL slug existence with GET /blogs/posts/url-slug-exists, then publish via POST /blogs/posts.
Pull latest posts with GET /blogs/posts and send summaries via emails/builder.
Generate and securely store your API key or OAuth credentials for the Blogs API.
Set up allowed endpoints including emails, blogs, and scheduling with scope emails/builder.readonly.
Create sample flows to fetch templates, create posts, and test sending emails.
You can start without coding by using webhooks and automations in DocsBot AI to trigger actions based on blog events. Leverage built-in templates and the endpoints for emails and blogs to assemble your flows. For more complex logic, you can sprinkle in lightweight scripting, but most workflows can be built without writing code.
Essential endpoints include GET emails/builder, POST emails/builder/data, POST /blogs/posts, GET /blogs/posts/url-slug-exists, PUT /blogs/posts/:postId, GET /blogs/categories and GET /blogs/authors. Start with authentication, then fetch templates, create a post, check slug, and finally publish.
Use GET /blogs/posts/url-slug-exists to verify slug uniqueness before creating or updating. If a conflict exists, adjust the slug and retry. Use PUT /blogs/posts/:postId to apply updates once you have a valid slug.
Yes. You can schedule posts and emails by combining the scheduling endpoints with blog publish endpoints and email templates. Create a trigger for publishDate and a corresponding email send action.
Recommended methods include API keys with scoped permissions and OAuth. Rotate credentials regularly, monitor scopes, and follow best practices for storing secrets securely.
No-code triggers are possible via DocsBot AI automations. Use scheduled or event-based triggers to call endpoints like GET /blogs/posts/url-slug-exists and POST /blogs/posts to create and publish posts without writing code.
API rate limits and quotas are documented in the developer portal. If you hit limits, stagger requests, cache responses where appropriate, and consider upgrading your plan or contacting support for higher quotas.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
