Understand a written date
'Next Tuesday' or '3rd Mar 24' turned into a proper ISO 8601 timestamp.
Anything from 3rd March 2024 to next tuesday.
Needs Date.
What it does
Also called: understand a written date · parse a date string · turn a human date into iso 8601.
Use it from your own code
The same endpoint this page calls — no daily cap, 1 credit a call either way.
POST /v1/core/date-parse
curl -X POST "$DOATHING_API/v1/core/date-parse" \
-H "x-api-key: $DOATHING_KEY" \
-H "content-type: application/json" \
-d '{"date": "next tuesday", "reference": "2026-01-01T00:00:00Z"}'
'Next Tuesday' or '3rd Mar 24' turned into a proper ISO 8601 timestamp.
Parse loosely formatted or relative dates into ISO 8601, with an explicit reference time.
Response
The result carries your remaining balance alongside it, so you can track spend without a second call.
{
"iso": "2026-01-06T00:00:00+00:00",
"weekday": "Tuesday",
"unix": 1767657600,
"request_id": "37f01edb-0163-42a1-ac51-0acaef979800",
"credits_remaining": 96
}
Cost
1 credit per call, whether it is run from the site or from the API — the credential differs, the price does not. A new account starts with 20 credits.
A rejected request still costs a credit: the authorizer decrements before the tool validates. A call rejected for a missing or invalid key is free.
Parameters
Generated from the endpoint’s own validation, so this is exactly what it accepts. A body field goes at the top level; an option goes inside options.
| Name | In | Type | Default | Notes |
|---|---|---|---|---|
| date * | body | string | — | Anything from 3rd March 2024 to next tuesday. |
| reference | body | string (ISO 8601) | — | |
| day_first | options | boolean | true | Read 01/02 as 1 February rather than 2 January. |
| fuzzy | options | boolean | false | Ignore unrecognised words around the date. |