Use a secured access token with the correct scope (emails/builder.readonly) to access endpoints like emails/builder and blogs endpoints.
Authenticate EnergySage with a service account or OAuth flow to obtain an access token for the Blogs API.
This section lists the primary endpoints involved in connecting EnergySage with the Blogs API, including email templates, scheduling, and blog posts.
Trigger: Load existing templates to reuse in EnergySage blog newsletters.
Actions: fetch, create, or update email templates.
GET emails/builder
Key fields: locationId, templateId, content, subject
Trigger: Review scheduled newsletters to align with blog publishing.
Actions: list schedules, update times, enable/disable.
GET emails/schedule
Key fields: scheduleId, time, status
Trigger: Publish new EnergySage blog posts via the Blogs API.
Actions: POST /blogs/posts, optionally update with PUT /blogs/posts/:postId.
POST /blogs/posts
Key fields: postId, title, slug, content
Automate content workflows without writing code.
Reduce manual steps with templates and schedules.
Keep branding consistent across emails and blog posts.
Understand the core elements: endpoints, authentication, data fields, and typical workflows used when connecting EnergySage with the Blogs API.
A specific URL path in the API used to perform a task (for example, GET emails/builder).
The process of validating identity to grant access to API resources (OAuth token or API key).
An HTTP method used to create a new resource on the server.
An HTTP method used to retrieve data from the server.
Automatically publish blog posts when energy market data updates, using templates.
Send regular digests of new blog content to subscribers via the Emails Builder.
Automatically generate summaries and SEO-friendly snippets for each post.
Create an API key or OAuth token with emails/builder.readonly scope to start.
Map blog fields (title, content, slug) to EnergySage blog posts and email templates.
Run tests, verify responses, and set up alerts for failures.
No coding is required for many common tasks. EnergySage can connect to the Blogs API using no-code builders, templates, and workflows to automate publishing and email distribution. For advanced automation, you can still extend with custom rules.
Start with core endpoints like GET emails/builder and GET emails/schedule to access templates and schedules. Then add POST blogs/posts to publish new content from EnergySage and keep a live blog synced.
Authentication typically uses an access token with the correct scope. Store credentials securely and rotate tokens periodically. Use the provided OAuth flow or API key mechanism as dictated by the Blogs API.
Yes. You can schedule both email campaigns and blog posts. Use the scheduling endpoints to automate publication times and reminders.
Expect standard HTTP error codes. Implement retries with exponential backoff and log failures for diagnostics. Use idempotent requests where possible.
API usage limits vary by plan. Monitor your quota and set alerts to prevent disruptions during campaigns.
Documentation is available in the developer portal for the Blogs API. Look for sections on authentication, endpoints, and data models.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
