Epochify exposes a conversion API you can call from your own code.
/api/v1/convert
60 req/min
POST /api/v1/convert
Content-Type: application/json
{
"direction": "epoch_to_date",
"value": "1700000000",
"timezone": "Asia/Kolkata",
"unit": "seconds"
}
// Click "Send Request" to see the response
curl -X POST https://epochify.dev/api/v1/convert \
-H "Content-Type: application/json" \
-d '{
"direction": "epoch_to_date",
"value": "1700000000",
"timezone": "Asia/Kolkata",
"unit": "seconds"
}'
Use epoch_to_date when logs, queue payloads, or webhooks store timestamps as integers and you need readable output for dashboards or alerts. Use date_to_epoch when user-facing date inputs must be normalized before writing to a database or sending to another API.
Always pass an explicit timezone for user-entered dates. This avoids ambiguous conversions when clients in different regions submit the same clock time.
epoch_to_date fails validation.For resilient clients, retry only transient failures and surface validation messages directly to users.