To authenticate the Blogs API, obtain an API key from the GHL developer console and grant Dixa access to the required endpoints such as GET emails/builder and GET blogs/authors. Store the key securely and rotate it regularly.
In Dixa, connect to the Blogs API using OAuth2 or an API key, then authorize the scope needed (emails/builder.readonly and blogs.*).
Key endpoints used include: GET emails/builder, POST /emails/builder, POST /emails/builder/data, DELETE /emails/builder/:locationId/:templateId, GET emails/schedule, GET /blogs/posts, POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/posts/url-slug-exists, GET /blogs/categories, GET /blogs/authors.
Trigger: a new blog post is created in Blogs API and is published or queued for publishing.
Actions: call POST /blogs/posts to publish, update CMS fields, and push a notification to Dixa.
POST /blogs/posts
Key fields: title, content, slug, author, category, status
Trigger: when a blog post is updated in Dixa, push changes to Blogs API.
Actions: PUT /blogs/posts/:postId and POST /blogs/post-update.write
PUT /blogs/posts/:postId
Key fields: postId, title, content, slug
Trigger: new or updated categories/authors in Blogs API to reflect in Dixa.
Actions: GET /blogs/categories and GET /blogs/authors; map results into Dixa as needed.
GET /blogs/categories and GET /blogs/authors
Fields: categoryIds, authorIds
No-code setup with drag-and-drop connectors lets you assemble workflows quickly without writing code.
Faster time-to-value with reusable triggers, actions, and field mappings across apps.
Scalable content operations across platforms, reducing manual data entry and errors.
This glossary defines common terms used in this guide: endpoints, triggers, actions, methods, and fields.
API stands for Application Programming Interface. It is a set of rules that lets your apps communicate with external services.
POST is an HTTP method used to create a new resource on a server.
GET is an HTTP method used to retrieve data from a server.
PUT is an HTTP method used to update an existing resource on a server.
Create a Dixa notification that a new post is published, including a summary and link to the post.
Draft content in Dixa using templates that push to Blogs API to publish, ensuring consistency.
Automatically generate campaigns in Dixa from blog posts and update as posts change.
Connect your Blogs API key and Dixa account to establish trust and permissions.
Map blog fields to Dixa fields (title, content, slug, author, category).
Run tests to verify triggers and actions before going live.
No coding skills are required for the basics. The integration uses visual builders and prebuilt actions. If you are comfortable with API concepts, you can customize mappings and flows. For advanced needs, you can add custom logic or webhooks.
For basic syncing, you’ll use endpoints like GET /blogs/authors, GET / blogs/categories, and POST /blogs/posts. As your needs grow, you can incorporate PUT /blogs/posts/:postId and GET /blogs/posts/url-slug-exists to manage content effectively.
Security is handled via API keys and OAuth where supported. Keys are scoped to the required endpoints and can be rotated. Always use secure storage and restrict access to essential team members.
Yes. You can map author data from Blogs API to Dixa contact fields. This enables personalized outreach and accurate author attribution within campaigns and workflows.
Yes. PUT /blogs/posts/:postId allows updating existing posts. You can synchronize changes from Dixa back to Blogs API to keep content up to date.
API keys are created in the GHL developer console and then entered into the Dixa app integration settings. Keep them secure and monitor usage to detect unusual activity.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
