Saved Inputs
Optional shortcuts for your development workflow. Save reusable request inputs and event-search criteria—not calculation results. Your application manages its own users and their data.
Your saved inputs
Loading…
Add a saved input Optional birth-data profile
Save a chart profile
Birth data may identify a person. Save it only with an appropriate reason and delete it when no longer needed.
Choose a result to fill coordinates and the modern IANA timezone. Historical UT1 offsets must be entered explicitly. City centers are approximate; verify the birth location.
Place data: GeoNames, CC BY 4.0. Self-hosted lookup; no third-party geocoding request.
Save event-search criteria
Store up to 25 reusable records across the event-calendar and event-rule-search operations.
This form creates and edits event-calendar criteria. API-created event-rule-search records are available here for copy, export, scheduling, and deletion; create or edit those rule records through the protected API. Dates and results are not stored. To run a search, submit copied criteria to its matching authenticated operation with an explicit UTC interval.
Your saved event searches
Loading…
Scheduled event searches
Run saved criteria as globally serial durable jobs and deliver completion through existing signed webhooks.
Loading…
Schedules use UTC and the selected key's scopes, environment controls, budget, and quota. A fold, retry, or queue delay never creates parallel calculation work.