Authenticate with the Blogs API using the provided API key and the scope emails/builder.readonly to access endpoints securely and retrieve scheduling and email data.
Award Force connects to the Blogs API via OAuth or API tokens. Configure credentials in the app settings, authorize the connection, and test the link to ensure data can flow between systems.
Key endpoints include GET emails/builder, GET emails/schedule, POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/categories, GET /blogs/authors, and GET /blogs/posts/url-slug-exists. These cover email creation, scheduling, blog post publishing, and catalog synchronization.
Trigger when a new blog post is created in Blogs API
Send an email through emails/builder and schedule follow ups with emails/schedule
POST /blogs/posts
title, content, slug, author, category
Trigger when a new category or author is added or updated in Blogs API
Create or update blog categories via blogs/category and authors via blogs/author endpoints and reflect in Award Force
GET /blogs/categories and GET /blogs/authors
category_name, author_name, author_id
Trigger when a blog post is updated or published to send email notifications
Use emails/builder to craft templates and emails/schedule to send timed updates
GET emails/schedule
schedule_time, recipient_list, template_id
Automate publishing and notification workflows without writing code
Keep data synchronized across Blog and Awards platforms
Improve engagement with targeted emails and timely updates
Definitions of terms and processes used in this GHL integration between Blogs API and Award Force.
A set of rules and endpoints that allow apps to talk to each other programmatically
A specific URL that performs an action or returns data
An open standard for granting access to resources securely
A URL friendly identifier for a blog post
Send an automated email when a new award is published to keep teams informed
Create categories automatically based on Award Force inputs
Push blog posts to social channels and newsletters via the Blogs API
Create and approve the connection between Award Force and the Blogs API
Enable and map endpoints such as POST /blogs/posts and GET /blogs/categories
Run tests with sample data, verify webhooks, and deploy
You can authenticate with an API key tied to the Blogs API. Use the scope emails/builder.readonly. This ensures read only access to composing emails and retrieving schedules. If you need write permissions, request additional scopes.
To publish posts you will use the blogs posts endpoints such as POST /blogs/posts or PUT /blogs/posts/:postId to update. Ensure your payload includes title, content, slug and optional author and category.
Yes, endpoints for categories and authors exist. Use GET /blogs/categories and GET /blogs/authors to sync with Award Force catalogs.
Test in a sandbox or using test data. Validate that triggers fire correctly and that data flows to emails/builder and emails/schedule.
You do not need to write code to get started. The integration is built around standard REST endpoints and webhooks.
The API key scope for this page is emails/builder.readonly, and you can request additional scopes if your workflow requires write access.
Sample payloads and docs are available in the developer portal or in this guide. Look for example payloads for BLOG posts, categories, and authors.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
