Daylight Duration Calculator computes sunrise, sunset times, and total daylight hours for any geographic location and date using astronomical algorithms.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// Daylight Duration Calculator response payload
}
}
About the Daylight Duration Calculator API
Returns detailed information including day of year, sunrise/sunset times, and formatted daylight duration, perfect for solar energy, agriculture, and travel applications.
What people use it for
- Solar Optimization
- Calculate daylight hours for solar panel optimization and energy production forecasting based on geographic location
- Activity Planning
- Plan outdoor activities and events based on accurate sunset and sunrise times for any location and date
- Weather Apps
- Build weather and astronomy applications with precise daylight duration calculations and solar position data
- Photography Scheduling
- Schedule photography sessions based on golden hour timing, blue hour, and optimal natural lighting conditions
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Daylight Duration Calculator
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Daylight Duration Calculator API do?
How do I authenticate Daylight Duration Calculator API requests?
How much does the Daylight Duration Calculator API cost?
How fast is the Daylight Duration Calculator API?
What response formats does the Daylight Duration Calculator API support?
What HTTP method does the Daylight Duration Calculator API use?
Request parameters — GET /v1/daylightduration
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
latitudeRequired | number | 40.7128 | Latitude of the location range -90-90 |
longitudeRequired | number | -74.006 | Longitude of the location range -180-180 |
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
dateOptionalPremium | string | 2024-06-21 | Date in YYYY-MM-DD format (defaults to today) date |
curl "https://api.apiverve.com/v1/daylightduration?latitude=40.7128&longitude=-74.0060&date=2024-06-21" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — GET /v1/daylightduration
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"date": "2024-06-21",
"location": {
"latitude": 40.7128,
"longitude": -74.006
},
"condition": "Normal",
"description": "Standard sunrise and sunset",
"sunrise": "09:25:09",
"sunset": "24:30:44",
"daylight_duration": {
"total_minutes": 905.58,
"hours": 15,
"minutes": 5,
"formatted": "15:05:00"
},
"day_of_year": 173,
"is_valid": true
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
date | string | "2024-06-21" | The requested date for daylight calculation |
location | object | {...} | |
latitude | number | 40.7128 | Location latitude coordinate used for calculation |
longitude | number | -74.006 | Location longitude coordinate used for calculation |
conditionPremium | string | "Normal" | Special solar condition at location, e.g., polar day |
description | string | "Standard sunrise and sunset" | Human-readable description of solar conditions |
sunrise | string | "09:25:09" | Sunrise time in HH:MM:SS format |
sunset | string | "24:30:44" | Sunset time in HH:MM:SS format |
daylight_duration | object | {...} | |
total_minutesPremium | number | 905.58 | Total daylight duration in minutes with decimal precision |
hours | number | 15 | Daylight hours component as integer |
minutes | number | 5 | Remaining daylight minutes component after hours |
formatted | string | "15:05:00" | Formatted daylight duration as HH:MM:SS string |
day_of_year | number | 173 | Julian day number of the year, one to 366 |
is_valid | boolean | true | Indicates whether calculation is valid for location |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 2 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Daylight Duration Calculator calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 100 | Free |
| Starter | $29.99 | 200,000 | 100,000 | $0.30 |
| Pro | $99.99 | 1,000,000 | 500,000 | $0.20 |
| Mega | $299.99 | 4,000,000 | 2,000,000 | $0.15 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/daylightduration
No SDK to install — this is a plain HTTPS call to /v1/daylightduration with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/daylightduration" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/daylightduration
Install the Node.js SDK, then call the Daylight Duration Calculator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/daylightdurationconst res = await fetch("https://api.apiverve.com/v1/daylightduration", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/daylightduration
No SDK to install — this is a plain HTTPS call to /v1/daylightduration with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/daylightduration",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/daylightduration
Install the C# / .NET SDK, then call the Daylight Duration Calculator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.DaylightDurationCalculatorusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/daylightduration");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/daylightduration
No SDK to install — this is a plain HTTPS call to /v1/daylightduration with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/daylightduration", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/daylightduration
No SDK to install — this is a plain HTTPS call to /v1/daylightduration with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/daylightduration");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/daylightduration
No SDK to install — this is a plain HTTPS call to /v1/daylightduration with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/daylightduration")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Daylight Duration Calculator form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Daylight Duration Calculator API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Daylight Duration Calculator API.
Math/Calculations
- Color Similarity Calculator
- Daylight Duration Calculator
- Fibonacci Generator
- Permutation & Combination Calculator
- Roman Numeral Math
- Tip Calculator
- Truth Table Generator
- UTM Coordinate Converter
Related articles
All articles →
Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read
Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read
Business Day Math Is Harder Than You ThinkWeekends, holidays, and country-specific rules make working day calculations surprisingly tricky. Here's what to watch for.Read