Weather Seasons API GET

Weather Seasons is a simple tool for getting the dates of the solstice and equinox. It returns the dates of the solstice and equinox for a given year.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/weatherseasons

Verification

Format

No key required to try it. Get a key to use it in your app.

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // Weather Seasons response payload
  }
}

About the Weather Seasons API

Weather Seasons works by calculating the dates of the solstice and equinox for a given year. It uses advanced algorithms to determine the dates of the solstice and equinox and returns the dates.

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

View all integrations →

Other ways to use Weather Seasons

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the Weather Seasons API.

Read the docs →

What does the Weather Seasons API do?

Weather Seasons is a simple tool for getting the dates of the solstice and equinox. It returns the dates of the solstice and equinox for a given year.

How do I authenticate Weather Seasons API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the Weather Seasons API cost?

Each call spends 2 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the Weather Seasons API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the Weather Seasons API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the Weather Seasons API use?

GET over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

Request parameters — GET /v1/weatherseasons

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.

Optional

Parameter	Type	Example	Description
`year`Optional	integer	`2024`	The year to get the dates of the solstice and equinox default 2025 · range 1900-2100

Example request

1
2

curl "https://api.apiverve.com/v1/weatherseasons?year=2024" \
  -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-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

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/weatherseasons

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.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "year": 2024,
    "timezone": "UTC",
    "march_equinox": "2024-03-20 03:06:24",
    "june_solstice": "2024-06-20 20:50:58",
    "september_equinox": "2024-09-22 12:43:55",
    "december_solstice": "2024-12-21 09:20:18"
  }
}

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
`year`	number	`2024`	The year for solstice and equinox dates requested
`timezone`	string	`"UTC"`	Timezone reference for all seasonal date calculations
`march_equinox`	string	`"2024-03-20 03:06:24"`	Spring equinox date and time for northern hemisphere
`june_solstice`	string	`"2024-06-20 20:50:58"`	Summer solstice date and time for northern hemisphere
`september_equinox`	string	`"2024-09-22 12:43:55"`	Fall equinox date and time for northern hemisphere
`december_solstice`	string	`"2024-12-21 09:20:18"`	Winter solstice date and time for northern hemisphere

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	Weather Seasons 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.

Compare all pricing tiers →

Call it from cURL — GET /v1/weatherseasons

No SDK to install — this is a plain HTTPS call to /v1/weatherseasons with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/weatherseasons" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/weatherseasons-apiSource, issues and the examples this page is built from.ReferenceWeather Seasons API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/weatherseasonsnpm apiverve-weatherseasonsPyPI APIVerve.API.WeatherSeasonsNuGet

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/weatherseasons

Install the Node.js SDK, then call the Weather Seasons API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/weatherseasons

Node.js

const res = await fetch("https://api.apiverve.com/v1/weatherseasons", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/weatherseasonsThe published Node.js client, versioned and signed.GitHubapiverve/weatherseasons-apiSource, issues and the examples this page is built from.ReferenceWeather Seasons API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

apiverve-weatherseasonsPyPI APIVerve.API.WeatherSeasonsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/weatherseasons

Install the Python SDK, then call the Weather Seasons API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — PyPI

pip install apiverve-weatherseasons

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/weatherseasons",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

PyPIapiverve-weatherseasonsThe published Python client, versioned and signed.GitHubapiverve/weatherseasons-apiSource, issues and the examples this page is built from.ReferenceWeather Seasons API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/weatherseasonsnpm APIVerve.API.WeatherSeasonsNuGet

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/weatherseasons

Install the C# / .NET SDK, then call the Weather Seasons API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.WeatherSeasons

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/weatherseasons");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.WeatherSeasonsThe published C# / .NET client, versioned and signed.GitHubapiverve/weatherseasons-apiSource, issues and the examples this page is built from.ReferenceWeather Seasons API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/weatherseasonsnpm apiverve-weatherseasonsPyPI

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/weatherseasons

No SDK to install — this is a plain HTTPS call to /v1/weatherseasons 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/weatherseasons", 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

@apiverve/weatherseasonsnpm apiverve-weatherseasonsPyPI APIVerve.API.WeatherSeasonsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/weatherseasons

No SDK to install — this is a plain HTTPS call to /v1/weatherseasons with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/weatherseasons");
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

@apiverve/weatherseasonsnpm apiverve-weatherseasonsPyPI APIVerve.API.WeatherSeasonsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/weatherseasons

No SDK to install — this is a plain HTTPS call to /v1/weatherseasons with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/weatherseasons")
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.body

Resources

Also published for

@apiverve/weatherseasonsnpm apiverve-weatherseasonsPyPI APIVerve.API.WeatherSeasonsNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

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

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

Weather Seasons API GET

Try it — live request, no key required

About the Weather Seasons API

Ways to call it

Other ways to use Weather Seasons

Questions.

Request parameters — GET /v1/weatherseasons

Optional

Authentication

Response — GET /v1/weatherseasons

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/weatherseasons

Resources

Also published for

Call it from Node.js — GET /v1/weatherseasons

Resources

Also published for

Call it from Python — GET /v1/weatherseasons

Resources

Also published for

Call it from C# / .NET — GET /v1/weatherseasons

Resources

Also published for

Call it from Go — GET /v1/weatherseasons

Resources

Also published for

Call it from PHP — GET /v1/weatherseasons

Resources

Also published for

Call it from Ruby — GET /v1/weatherseasons

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Weather Seasons API

Weather

Related articles

Ready to build with Weather Seasons? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog