Easter Sunday date calculator
This Easter Sunday date calculator takes a single Gregorian calendar year and returns the date of Western Easter Sunday for that year using the classic Anonymous Gregorian computus, also known as the Meeus–Jones–Butcher integer algorithm.
Run — free
Easter is a movable feast: it falls on the first Sunday after the ecclesiastical full moon that occurs on or after 21 March, which in practice lands between 22 March and 25 April inclusive. Small checks you may already know include year 2024 mapping to 31 March, year 2025 mapping to 20 April, and year 2000 mapping to 23 April. The engine uses only finite integer divisions and remainders with no network calls, no random sampling, and no host-clock Date objects, so the same year always produces the same month and day. Use it free in the browser for planning, teaching, and liturgy worksheets, or call the API at $0.002 per successful request when you need reproducible Easter fixtures in CI, holiday calendars, or product features.
How to use it
Enter your values in the form above. The tool checks them before calculating and shows the result on the same page.
Check your inputs
Use the labels and units shown next to each field. If something is missing or outside the allowed range, the page points to the field to fix.
Use it again or automate it
Use the browser tool for individual checks and the API when you need the same capability in an automated workflow.
What you can do with it
Get an answer now
Enter one set of values and see the result without building a spreadsheet or script.
Compare scenarios
Change one value at a time and rerun the calculation to understand what affects the result.
Automate repeated work
Use the API when the same calculation needs to run inside your product or workflow.
FAQ
How do I use this capability?
Complete the fields above and run it on this page. The form highlights anything that needs attention.
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/date/easter-sunday \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"year":2024}'const res = await fetch("https://api.kit.forhosting.com/date/easter-sunday", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"year": 2024
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/date/easter-sunday",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"year": 2024
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/date/easter-sunday", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"year":2024}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"year":2024}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/date/easter-sunday", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"year": 2024
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "date.easter_sunday",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Limits
year_min | 1 |
year_max | 9999 |
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |