Securely authorize the Blogs API with ON24 using API keys or OAuth, then manage tokens and permissions from your dashboard.
Authorize ON24 to access your Blogs API resources. Use the OAuth flow or API keys to grant permissions and protect credentials.
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 published in Blogs API
Actions: create ON24 emails or campaigns, update ON24 schedules, or notify teams.
POST /blogs/posts
postId, title, slug, status
Trigger: blog post published or updated
Actions: queue ON24 emails, update schedules, link webinars
PUT /blogs/posts/:postId
postId, slug, publishDate
Trigger: new category or author added or updated
Actions: push updates to blogs/categories and blogs/authors lists
GET /blogs/categories
categoryId, authorId, name
Automate workflows without writing code, saving time and reducing manual errors.
Real-time data syncing enables timely ON24 campaigns and blog updates.
Centralized control of content across platforms for consistent branding.
Key elements include endpoints, triggers, actions, data fields, and authentication flows that power the integration between Blogs API and ON24.
Application Programming Interface — a set of rules that allows two applications to communicate and exchange data.
A specific URL path and HTTP method that performs a defined action within an API.
A URL that receives real-time data from another application when events occur.
A URL-friendly version of a title used in constructing web addresses.
Automatically trigger ON24 emails or webinars whenever a new blog post is published in the Blogs API.
Use blog metadata and categories to tailor ON24 webinar pages and emails in real-time.
Capture attendee engagement and feed it back into the Blogs API for richer analytics.
Grab your API credentials and authorize access between Apps.
Select necessary endpoints from the list and set up event triggers in ON24.
Run tests to confirm data flow and then deploy the integration.
The supported endpoints include a mix of emails, blogs, and category endpoints such as GET emails/builder, POST /emails/builder/data, GET /blogs/posts/url-slug-exists, GET /blogs/categories, and more. Use these to build automations that create emails, post content, and manage schedules. If you need endpoints beyond the 17 listed, consult the API docs for additional methods.
Authentication between Blogs API and ON24 is achieved via API keys or OAuth. Start by generating an API key in Blogs API, then authorize ON24 to use it, and finally exchange tokens securely. Store tokens safely and rotate as recommended.
Yes. Map blog fields like title, slug, category, and author name to corresponding ON24 fields in your campaigns. Use triggers to pass data between systems and ensure field mappings are kept in sync.
Slug checks prevent broken links by validating whether a blog slug already exists before creating or updating a post. Use the provided GET /blogs/posts/url-slug-exists endpoint to verify availability.
Most endpoints have standard rate limits. Plan your requests, paginate responses, and implement exponential backoff to avoid throttling. If you expect high volume, contact support for higher quotas.
Webhooks are supported for real-time updates in some plans. Configure your webhook URL in Blogs API and verify signatures to secure the data feed.
Error logs and troubleshooting details can be viewed in your ON24 and Blogs API dashboards. Enable verbose logging during setup and review error codes returned by endpoints to isolate issues.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
