ForHosting KIT · Dates & time

Juneteenth date calculator

Enter a year and get Juneteenth, June 19, plus the day US federal offices observe it: in 2026 June 19 is a Friday, so both dates match. A Saturday moves to the Friday before, a Sunday to the Monday after. Free in your browser.

Free
Runs in your browser
No sign-up
Your data stays on your device

Run — free How it works & API

Use it from WebAPIEmailTelegramApp soon

Worked example

If you enter

Year: 2,026

You get

Date: 2026-06-19
Observed: 2026-06-19
Name: Juneteenth
Weekday: Friday

Juneteenth is the United States federal holiday commemorating June 19. When that calendar day falls on a Saturday or Sunday, federal offices and many employers use an observed weekday instead. HR systems, school calendars, banks, and delivery SLAs need both the fixed date and the observed day without maintaining a holiday spreadsheet. This capability takes one civil year and returns June 19, the federal observed date, weekdays, and a stable English name—pure calendar math, no network.

What Juneteenth is and how federal observance works

Juneteenth marks June 19 as a United States federal holiday. The civil anniversary is always the nineteenth of June. Federal payroll and many private employers additionally apply a weekend-shift rule when that date lands on Saturday or Sunday: Saturday observances move to the preceding Friday, and Sunday observances move to the following Monday.

Weekday Juneteenth dates are observed on the same day. Product teams that schedule leave, market hours, school closures, or parcel cutoffs therefore need two answers for some years and one for others. Encoding both the fixed date and the observed date in one deterministic function keeps HR, banking, and logistics clients aligned without scraping public calendars that change format or go offline.

That dual answer is what leave systems and market calendars actually need when they plan a full year ahead.

When to call this and what stays out of scope

Use this capability when you need US federal Juneteenth for a planning year, including the observed weekday for weekend collisions. It does not list state-only renames, does not combine multi-country holiday packs, and does not invent employer-specific substitutes. Pair it with MLK Day, Presidents Day, and Columbus Day calculators for a compact domestic federal set.

Logistics tools can flag delayed SLA days; HR can block leave; municipal apps can label service changes. Field names year and date follow the standard vocabulary so free-web labels hydrate cleanly after Nitro translates. Always confirm with your organization if it substitutes a different local day.

Layer your own policy if your organization substitutes a different local day or treats the Monday as optional.

FAQ

What is the fixed date of Juneteenth?

June 19 every year. This capability always returns that civil date as date.

When does observed differ from date?

When June 19 is a Saturday (observed moves to Friday) or a Sunday (observed moves to Monday).

Does time zone change the result?

No. Both date and observed are whole civil calendar days computed without the server wall clock.

Is this the federal rule only?

Yes. It encodes the US federal weekend-shift rule, not every state or employer variant.

Can I plan several years ahead?

Yes. Enter any year and you get its fixed date and its observed day, so leave calendars, school closures or delivery cutoffs can be set for the whole year in advance.

Related tools

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

POSThttps://api.kit.forhosting.com/date/juneteenth-observed

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/juneteenth-observed \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"year":2026}'

const res = await fetch("https://api.kit.forhosting.com/date/juneteenth-observed", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "year": 2026
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/date/juneteenth-observed",
    headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
    json={
    "year": 2026
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/date/juneteenth-observed", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => '{"year":2026}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"year":2026}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/date/juneteenth-observed", 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": 2026
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "date.juneteenth_observed",
  "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

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

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.

Technical notes

Use the free browser form for a quick check, or the API at $0.002 per successful request in payroll and logistics code.

How the calculation works and what fields you get

After validating year as an integer in the supported band, the solver builds June 19 in the proleptic Gregorian calendar using UTC civil arithmetic. When June 19 is already a weekday, date and observed are identical; the keys still appear so forms and goldens stay stable. There is no wall-clock dependence and no null fields. It records the weekday of that date, then applies the federal weekend rule to produce observed and observed_weekday. Output always includes year, date as YYYY-MM-DD, observed as YYYY-MM-DD, name Juneteenth, weekday, and observed_weekday. Empty input, non-integers, and out-of-range years raise invalid_input with a clear English message.

Integration use cases

Technical questions

Which years are accepted?

Integers from 1900 through 2200 inclusive. Outside that band you get invalid_input.

Read the full KIT documentation →

Run — free