Sunrise Sunset is a simple tool for getting the sunrise and sunset times. It returns the sunrise and sunset times for a given location and date.
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": {
// Sunrise Sunset response payload
}
}
About the Sunrise Sunset API
Sunrise Sunset works by calculating the sunrise and sunset times based on the location and date provided. It returns the sunrise and sunset times in a structured format.
What people use it for
- Photography
- Use the Sunrise Sunset API to get sunrise and sunset times for photography. Use the data to plan shoots, capture golden hours, and optimize lighting
- Outdoor Activities
- Plan outdoor activities by using the Sunrise Sunset API to get sunrise and sunset times. Use the data to schedule events, organize trips, and optimize experiences
- Gardening
- Get sunrise and sunset times by using the Sunrise Sunset API for gardening. Use the data to plan planting, schedule harvests, and optimize crop growth
- Weather App
- Use the Sunrise Sunset API to get sunrise and sunset times for a weather app. Use the data to display weather information, provide forecasts, and offer alerts
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 Sunrise Sunset
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Sunrise Sunset API do?
How do I authenticate Sunrise Sunset API requests?
How much does the Sunrise Sunset API cost?
How fast is the Sunrise Sunset API?
What response formats does the Sunrise Sunset API support?
What HTTP method does the Sunrise Sunset API use?
Request parameters — GET /v1/sunrisesunset
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 |
|---|---|---|---|
latRequired | number | 36.72016 | The latitude of the location range -90-90 |
lonRequired | number | -4.42034 | The longitude of the location range -180-180 |
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
dateOptionalPremium | string | 01-16-2026 | The date for which you want to get the sunrise and sunset times (e.g., MM-DD-YYYY : 01-01-2022) date |
curl "https://api.apiverve.com/v1/sunrisesunset?lat=36.7201600&lon=-4.4203400&date=01-16-2026" \
-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/sunrisesunset
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": {
"solarNoon": "2025-12-16T12:14:40.51Z",
"sunrise": "2025-12-16T07:24:56.165Z",
"sunset": "2025-12-16T17:04:24.854Z",
"sunriseEnd": "2025-12-16T07:27:58.828Z",
"sunsetStart": "2025-12-16T17:01:22.192Z",
"dawn": "2025-12-16T06:56:02.774Z",
"dusk": "2025-12-16T17:33:18.245Z",
"nauticalDawn": "2025-12-16T06:23:38.134Z",
"nauticalDusk": "2025-12-16T18:05:42.886Z",
"nightEnd": "2025-12-16T05:52:07.048Z",
"night": "2025-12-16T18:37:13.971Z",
"goldenHourEnd": "2025-12-16T08:05:08.406Z",
"goldenHour": "2025-12-16T16:24:12.613Z"
}
}
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 |
|---|---|---|---|
solarNoonPremium | string | "2025-12-16T12:14:40.51Z" | Solar noon time |
sunrise | string | "2025-12-16T07:24:56.165Z" | Sunrise time in ISO 8601 format |
sunset | string | "2025-12-16T17:04:24.854Z" | Sunset time in ISO 8601 format |
sunriseEnd | string | "2025-12-16T07:27:58.828Z" | Moment the sun's disc has fully cleared the horizon, in UTC |
sunsetStart | string | "2025-12-16T17:01:22.192Z" | Moment the sun's disc first touches the horizon at sunset, in UTC |
dawn | string | "2025-12-16T06:56:02.774Z" | Start of civil twilight, when the sun is 6 degrees below the horizon |
dusk | string | "2025-12-16T17:33:18.245Z" | End of civil twilight, when the sun drops 6 degrees below the horizon |
nauticalDawn | string | "2025-12-16T06:23:38.134Z" | Start of nautical twilight, when the sun is 12 degrees below the horizon |
nauticalDusk | string | "2025-12-16T18:05:42.886Z" | End of nautical twilight, when the sun drops 12 degrees below the horizon |
nightEnd | string | "2025-12-16T05:52:07.048Z" | End of astronomical night, when the sun rises above 18 degrees below the horizon |
night | string | "2025-12-16T18:37:13.971Z" | Start of astronomical night, when the sun drops 18 degrees below the horizon |
goldenHourEnd | string | "2025-12-16T08:05:08.406Z" | End of the morning golden hour, when soft low-angle light gives way to daylight |
goldenHour | string | "2025-12-16T16:24:12.613Z" | Start of the evening golden hour, when the light turns soft and low-angle |
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 | Sunrise Sunset 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/sunrisesunset
No SDK to install — this is a plain HTTPS call to /v1/sunrisesunset 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/sunrisesunset" \
-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/sunrisesunset
Install the Node.js SDK, then call the Sunrise Sunset API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/sunrisesunsetconst res = await fetch("https://api.apiverve.com/v1/sunrisesunset", {
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/sunrisesunset
Install the Python SDK, then call the Sunrise Sunset API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-sunrisesunsetimport requests
res = requests.get(
"https://api.apiverve.com/v1/sunrisesunset",
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/sunrisesunset
Install the C# / .NET SDK, then call the Sunrise Sunset 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.SunriseSunsetusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/sunrisesunset");
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/sunrisesunset
No SDK to install — this is a plain HTTPS call to /v1/sunrisesunset 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/sunrisesunset", 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/sunrisesunset
No SDK to install — this is a plain HTTPS call to /v1/sunrisesunset 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/sunrisesunset");
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/sunrisesunset
No SDK to install — this is a plain HTTPS call to /v1/sunrisesunset 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/sunrisesunset")
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 Sunrise Sunset 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 — Sunrise Sunset 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 Sunrise Sunset API.
Weather
- Air Quality
- Marine Weather
- Moonrise Moonset
- Solar Potential
- Sunrise Sunset
- Weather
- Weather Seasons
- Worldwide Earthquakes
Related articles
All articles →
Weather APIs: Build a Dashboard That's Actually UsefulCurrent conditions, forecasts, air quality, sunrise times—here's how to build a weather dashboard users will love.Read
Building Health-Conscious Apps With Air Quality DataAir quality affects millions of users. Here's how to integrate environmental health data meaningfully.Read
API Caching: The Cheapest Performance WinEvery duplicate API call is wasted money. Here's how to cache responses properly—and when not to.Read