Authenticate CoordinateHQ to Blogs API using a secure API key with the appropriate scopes. Maintain least privilege, rotate keys regularly, and use HTTPS for all requests.
CoordinateHQ authenticates to Blogs API with credentials generated in your developer console. Store tokens securely, implement refresh workflows, and monitor for unusual activity.
Key endpoints include: GET emails/builder, GET emails/builder.readonly, POST emails/builder/data, GET /blogs/posts/url-slug-exists, POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/categories, GET /blogs/authors, GET /blogs/posts, GET /blogs/categories, GET /blogs/authors, GET emails/schedule, GET emails/builder, POST /blogs/posts, PUT /blogs/posts/:postId, DELETE /emails/builder/:locationId/:templateId. Use only the endpoints you need to power your CoordinateHQ workflows.
Trigger: A new blog post is created or published in Blogs API.
Actions: create/update a corresponding post in CoordinateHQ, populate SEO fields, and notify teams via email templates.
Method/Path: POST /blogs/posts or PUT /blogs/posts/:postId
Key fields: postId, slug, title, status
Trigger: Blog category or author updates in Blogs API.
Actions: map category/author data to CoordinateHQ content and refresh related SEO metadata.
GET /blogs/categories and GET /blogs/authors
Key fields: categoryId, authorId, name
Trigger: Post is scheduled for publication.
Actions: publish to site, share to newsletters, and push notifications to social channels.
POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/posts
Key fields: postId, publish_at, status
Lightning-fast setup with drag-and-drop workflows—no coding required.
Real-time data sync between Blogs API and CoordinateHQ content libraries.
Automated publishing and updates across channels with minimal effort.
This section defines core elements: API endpoints, triggers, actions, fields, and how they connect CoordinateHQ with Blogs API.
A set of rules and endpoints that let CoordinateHQ request and modify data in Blogs API.
A specific URL path and HTTP method used to perform an action.
A notification mechanism that pushes events from Blogs API to CoordinateHQ.
The URL-friendly string used in blog post URLs.
Automatically generate page titles, meta descriptions, and slugs from blog content to improve search visibility.
Embed live blog previews or summaries in email templates to entice reads.
Automatically publish to social channels and newsletters when a post goes live.
Generate an API key with proper scopes and securely store it.
Select required endpoints and map input/output fields between Blogs API and CoordinateHQ.
Run tests to verify data flows, then activate the connection for production.
Yes, there are rate limits that vary by plan. If you exceed the limit, requests may be throttled temporarily. Review your account plan in the dashboard to understand your quotas and adjust request patterns accordingly.
Yes. Blog fields can be customized via payload mappings and field aliases. Some advanced fields may require additional permissions; consult the API reference for field-level controls.
Use API keys or OAuth tokens, store credentials securely, and rotate them regularly. Always use HTTPS and prefer short-lived tokens with refresh capabilities.
Yes. Scheduling is supported via publish_at or equivalent parameters in the blogs endpoints. Configure your workflow to trigger at the desired time and CoordinateHQ will publish automatically.
If a slug already exists, the API may return a slug_exists error. You can retrieve existence with GET /blogs/posts/url-slug-exists and adjust the slug before retrying.
Webhooks are recommended to keep CoordinateHQ in sync with Blogs API events. If you cannot use webhooks, you can poll endpoints at a regular cadence, though webhooks are more efficient.
API documentation is available in the Blogs API developer portal. It includes endpoint details, examples, authentication guidance, and sample payloads.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
