GET /date/{date}
Pass a date any way it was written. Get one clean answer.
Try it
date
The date as ISO YYYY-MM-DD, or the input echoed when it does not parse
valid
Resolves to one real calendar day. Ambiguous numeric dates answer false without ?format=
weekday_name
English weekday name
week
ISO 8601 week number
day_of_year
Day of year, 1 to 366
quarter
Quarter, 1 to 4
leap
Whether the year is a leap year
unix
Unix time at midnight UTC of that date, seconds
1
March 29, 2026, 3/29/2026, 29 Aug 2026, or 20260829. A weekday and a time tail are ignored.
2
ISO date, weekday, ISO week, day of year, quarter, leap year, unix time.
3
03/04/2026 is two real days. Without ?format= it answers valid: false, never a guess.
Days between dates with ?to=. Every plan.
Pass a date the way a spreadsheet, a form, or a log wrote it. ISO, March 29, 2026, 29 Aug 2026, 3/29/2026, and 20260829 all come back as one clean answer: the ISO date, weekday, ISO week and week-year, day of year, quarter, leap year, days in the month, and unix time. A leading weekday and an ISO time tail are ignored.
We never guess a reading. 3/29/2026 resolves on its own, since 29 cannot be a month. 03/04/2026 could be two real days, so it answers valid: false until you pass ?format=mdy or ?format=dmy. Add ?to= for the signed days between two dates, and bare /date?to= counts from today.
RESPONSE
$ curl "https://api.parseapi.com/date/March%2029,%202026" \ -H "X-API-Key: YOUR_API_KEY" // 200 · ~27ms US · ~122ms worldwide { "date": "2026-03-29", "valid": true, "year": 2026, "month": 3, "month_name": "March", "day": 29, "weekday": 7, "weekday_name": "Sunday", "week": 13, "week_year": 2026, "day_of_year": 88, "quarter": 1, "leap": false, "days_in_month": 31, "unix": 1774742400 }
Response fields
QUESTIONS
SPEED
US
27ms
EU
50ms
APAC
144ms
LatAm
21ms
ME
122ms