ISO 8601 Timestamp Converter

Convert timestamps between ISO 8601, Unix epoch (seconds & milliseconds), and human-readable formats. Free API endpoint for AI agents and developers. No auth required.

What Is ISO 8601?

ISO 8601 is the international standard for representing dates and times. It eliminates ambiguity by using a fixed format: YYYY-MM-DDTHH:mm:ssZ. The trailing Z indicates UTC. Agents exchanging messages across time zones rely on ISO 8601 to avoid misinterpretation. Every major API -- from GitHub to Stripe to OpenAI -- uses this format.

How to Use the Converter

Send a POST request to the REST API with any timestamp format. The endpoint returns all representations at once.

REST API (curl)

curl -X POST https://api.delx.ai/api/v1/utils/timestamp \
  -H "Content-Type: application/json" \
  -d '{"input": "2026-03-14T12:00:00Z"}'

# Response:
# {
#   "iso8601": "2026-03-14T12:00:00Z",
#   "unix_seconds": 1773532800,
#   "unix_ms": 1773532800000,
#   "human": "Saturday, March 14, 2026 12:00:00 PM UTC"
# }

Common Timestamp Formats

Converting in Code

Python

from datetime import datetime, timezone

# ISO 8601 to Unix
dt = datetime.fromisoformat("2026-03-14T12:00:00+00:00")
unix_ts = int(dt.timestamp())  # 1773532800

# Unix to ISO 8601
dt = datetime.fromtimestamp(1773532800, tz=timezone.utc)
iso = dt.isoformat()  # "2026-03-14T12:00:00+00:00"

JavaScript

// ISO 8601 to Unix (ms)
const ms = new Date("2026-03-14T12:00:00Z").getTime(); // 1773532800000

// Unix (ms) to ISO 8601
const iso = new Date(1773532800000).toISOString();
// "2026-03-14T12:00:00.000Z"

curl (Delx API)

# Convert "now" to all formats
curl -s -X POST https://api.delx.ai/api/v1/utils/timestamp \
  -H "Content-Type: application/json" \
  -d '{"input": "now"}' | jq .

# Convert Unix epoch
curl -s -X POST https://api.delx.ai/api/v1/utils/timestamp \
  -H "Content-Type: application/json" \
  -d '{"input": "1773532800"}'

Why Agents Need Timestamp Conversion

AI agents operate across APIs that use different timestamp formats. A Stripe webhook sends Unix seconds, a GitHub event uses ISO 8601, and a database might store RFC 2822. Agents need to normalize these into a single format for logging, comparisons, and scheduling. Following agent best practices means every log entry and inter-agent message uses ISO 8601 UTC.

• Log correlation: match events across services with a single timestamp format
• Scheduling: cron jobs and heartbeat intervals require precise epoch math
• Audit trails: compliance demands unambiguous, timezone-aware timestamps
• Rate-limit headers: X-RateLimit-Reset is often a Unix epoch

FAQ

Related Tools

Related Articles

• What Is Delx?
• OpenClaw Best Practices