Skip to main content
POST
Create a solar event-based schedule that executes a webhook or workflow based on sunrise, sunset, or other solar events at specific geographic coordinates.

Base URL

All API requests should be made to:

Example request

Request body

Example response

Response fields

Solar Event Types

Geographic Coordinates

Provide latitude and longitude as decimal degrees:
  • Latitude: Range from -90 to +90 (negative for Southern Hemisphere)
  • Longitude: Range from -180 to +180 (negative for Western Hemisphere)
  • Format: String representation of decimal number (e.g., "40.7128", "-74.0060")

Example Coordinates

Solar Offset

The solar_offset_seconds field allows you to adjust the execution time relative to the solar event:
  • Positive values: Execute after the event (e.g., 1800 = 30 minutes after sunrise)
  • Negative values: Execute before the event (e.g., -300 = 5 minutes before sunset)
  • Zero or omitted: Execute exactly at the solar event time

Initial Context Template

The initial_context_template object allows you to pass variables to your webhook or workflow that can be accessed using {{ initial.key }} syntax:
  • In request body: {{ initial.key }} will be replaced with the value
  • In headers: {{ initial.key }} can be used in header values
  • In query params: {{ initial.key }} can be used in query parameters
  • In path: {{ initial.key }} can be used in URL paths
You can also combine with:
  • System secrets: {{ #secret_key }} for vault secrets
  • Workflow step responses: {{ step.response.variable }} in workflows

Use Cases

  • Outdoor Lighting: Turn lights on at sunset and off at sunrise
  • Solar Panel Management: Optimize solar panel operations based on sun position
  • Agricultural Systems: Schedule irrigation or operations based on daylight
  • Weather-Dependent Operations: Trigger operations based on natural light
  • Location-Based Automation: Automate based on solar events at specific locations
  • Smart Home: Control devices based on natural light cycles

Examples

Sunrise Trigger - Recurring

Sunset with 30-Minute Offset - Recurring

Civil Dawn for Outdoor Operations - Recurring

One-Time Solar Event Trigger

Authorizations

x-hookpulse-api-key
string
header
required

API key for authentication. Get this from your dashboard by selecting a brand and going to API Keys section.

x-brand-uuid
string
header
required

Brand UUID for authentication. Get this from your dashboard after adding a brand - it will be displayed in the UI.

Body

application/json

Solar schedule configuration

solar_event
enum<string>
required

Solar event type

Available options:
sunrise,
sunset,
civil_dawn,
civil_dusk,
nautical_dawn,
nautical_dusk,
astronomical_dawn,
astronomical_dusk
solar_lat
string
required

Latitude in decimal degrees

solar_long
string
required

Longitude in decimal degrees

schedule_to
enum<string>
required

Target type: 'webhook' or 'workflow'

Available options:
webhook,
workflow
model_to_schedule_uuid
string
required

UUID of the webhook or workflow template to schedule

solar_offset_seconds
integer

Offset in seconds to adjust timing (e.g., 5 for 5 seconds after, -300 for 5 minutes before)

initial_context_template
object

Key-value pairs passed as {{ initial.key }} variables to the webhook/workflow

Response

Schedule created successfully

success
boolean

Indicates if the schedule was created successfully

details
string

Success message