Moon Phases is a simple tool for getting the moon phases. It returns the moon phase for a given 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": {
// Moon Phases response payload
}
}
About the Moon Phases API
Moon Phases works by calculating the moon phase based on the date provided. It returns the moon phase in a structured format.
What people use it for
- Astrology
- Use the Moon Phases API to get moon phases for astrology. Use the data to study lunar cycles, track celestial events, and explore astrology
- Gardening
- Get moon phases by using the Moon Phases API for gardening. Use the data to plan planting, schedule harvests, and optimize crop growth
- Outdoor Activities
- Plan outdoor activities by using the Moon Phases API to get moon phases. Use the data to schedule events, organize trips, and optimize experiences
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 Moon Phases
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Moon Phases API do?
How do I authenticate Moon Phases API requests?
How much does the Moon Phases API cost?
How fast is the Moon Phases API?
What response formats does the Moon Phases API support?
What HTTP method does the Moon Phases API use?
Request parameters — GET /v1/moonphases
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 |
|---|---|---|---|
todayOptional | boolean | true | Get the moon phase for today default true |
curl "https://api.apiverve.com/v1/moonphases?today=true" \
-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/moonphases
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": {
"phase": "Waning Crescent",
"phaseEmoji": "🌘",
"illumination": 9.9,
"waxing": false,
"waning": true,
"lunarAge": 26.61193415670738,
"lunarAgePercent": 0.9011650706672754,
"lunationNumber": 1274,
"lunarDistance": 63.77810628163608,
"nextFullMoon": "2026-01-16T00:00:00Z",
"lastFullMoon": "2025-11-17T00:00:00Z",
"daysToFullMoon": 28,
"daysSinceFullMoon": 2
}
}
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 |
|---|---|---|---|
phase | string | "Waning Crescent" | |
phaseEmoji | string | "🌘" | |
illumination | number | 9.9 | |
waxing | boolean | false | |
waning | boolean | true | |
lunarAge | number | 26.61193415670738 | |
lunarAgePercent | number | 0.9011650706672754 | |
lunationNumber | number | 1274 | |
lunarDistance | number | 63.77810628163608 | |
nextFullMoon | string | "2026-01-16T00:00:00Z" | |
lastFullMoon | string | "2025-11-17T00:00:00Z" | |
daysToFullMoon | number | 28 | |
daysSinceFullMoon | number | 2 |
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 cycle's allowance |
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 | Moon Phases 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/moonphases
No SDK to install — this is a plain HTTPS call to /v1/moonphases 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/moonphases" \
-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/moonphases
Install the Node.js SDK, then call the Moon Phases API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/moonphasesconst res = await fetch("https://api.apiverve.com/v1/moonphases", {
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/moonphases
Install the Python SDK, then call the Moon Phases API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-moonphasesimport requests
res = requests.get(
"https://api.apiverve.com/v1/moonphases",
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/moonphases
Install the C# / .NET SDK, then call the Moon Phases 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.MoonPhasesusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/moonphases");
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/moonphases
No SDK to install — this is a plain HTTPS call to /v1/moonphases 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/moonphases", 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/moonphases
No SDK to install — this is a plain HTTPS call to /v1/moonphases 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/moonphases");
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/moonphases
No SDK to install — this is a plain HTTPS call to /v1/moonphases 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/moonphases")
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 Moon Phases 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 — Moon Phases 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.
Astrology
Related articles
All articles →
Add Daily Horoscopes to Your App in 5 MinutesBuild a horoscope feature your users will actually check daily. Working code included.Read
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