Unix Timestamp Converter API
Overview
To use Unix Timestamp Converter, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/unixtimestampExample
How to call the Unix Timestamp Converter API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/unixtimestamp?timestamp=1609459200&format=seconds" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/unixtimestamp?timestamp=1609459200&format=seconds', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/unixtimestamp?timestamp=1609459200&format=seconds', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/unixtimestamp?timestamp=1609459200&format=seconds", nil)
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"status": "ok",
"error": null,
"data": {
"timestamp": 1609459200,
"timestamp_format": "seconds",
"iso_8601": "2021-01-01T00:00:00Z",
"rfc_2822": "Fri, 01 Jan 2021 00:00:00 GMT",
"date": "1/1/2021",
"time": "12:00:00 AM",
"unix_seconds": 1609459200,
"unix_milliseconds": 1609459200000,
"year": 2021,
"month": 1,
"day": 1,
"hour": 0,
"minute": 0,
"second": 0,
"day_of_week": "Friday",
"timezone": "UTC"
}
}Authentication
The Unix Timestamp Converter API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Unix Timestamp Converter API directly in your browser with live requests and responses.
Parameters
The Unix Timestamp Converter API supports multiple query options. Use one of the following:
Option 1: Timestamp to Date
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
timestamp | string | required | Unix timestamp to convert Format: timestamp (e.g., 1609459200) | - | |
format | string | optional | Timestamp format Supported values: secondsmillisecondssms |
Option 2: Date to Timestamp
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
date | string | required | Date string to convert (ISO 8601 format) | - | |
format | string | optional | Output timestamp format Supported values: secondsmillisecondssms |
Response
The Unix Timestamp Converter API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<timestamp>1609459200</timestamp>
<timestamp_format>seconds</timestamp_format>
<iso_8601>2021-01-01T00:00:00Z</iso_8601>
<rfc_2822>Fri, 01 Jan 2021 00:00:00 GMT</rfc_2822>
<date>1/1/2021</date>
<time>12:00:00 AM</time>
<unix_seconds>1609459200</unix_seconds>
<unix_milliseconds>1609459200000</unix_milliseconds>
<year>2021</year>
<month>1</month>
<day>1</day>
<hour>0</hour>
<minute>0</minute>
<second>0</second>
<day_of_week>Friday</day_of_week>
<timezone>UTC</timezone>
</data>
</response>
status: ok
error: null
data:
timestamp: 1609459200
timestamp_format: seconds
iso_8601: '2021-01-01T00:00:00Z'
rfc_2822: Fri, 01 Jan 2021 00:00:00 GMT
date: 1/1/2021
time: 12:00:00 AM
unix_seconds: 1609459200
unix_milliseconds: 1609459200000
year: 2021
month: 1
day: 1
hour: 0
minute: 0
second: 0
day_of_week: Friday
timezone: UTC
| key | value |
|---|---|
| timestamp | 1609459200 |
| timestamp_format | seconds |
| iso_8601 | 2021-01-01T00:00:00Z |
| rfc_2822 | Fri, 01 Jan 2021 00:00:00 GMT |
| date | 1/1/2021 |
| time | 12:00:00 AM |
| unix_seconds | 1609459200 |
| unix_milliseconds | 1609459200000 |
| year | 2021 |
| month | 1 |
| day | 1 |
| hour | 0 |
| minute | 0 |
| second | 0 |
| day_of_week | Friday |
| timezone | UTC |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
timestamp | number | - | |
timestamp_format | string | - | |
iso_8601 | string | - | |
rfc_2822 | string | - | |
date | string | - | |
time | string | - | |
unix_seconds | number | - | |
unix_milliseconds | number | - | |
year | number | - | |
month | number | - | |
day | number | - | |
hour | number | - | |
minute | number | - | |
second | number | - | |
day_of_week | string | - | |
timezone | string | - |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access Unix Timestamp Converter through GraphQL to combine it with other API calls in a single request. Query only the unix timestamp converter data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
unixtimestamp(
input: {
timestamp: "1609459200"
format: "seconds"
}
) {
timestamp
timestamp_format
iso_8601
rfc_2822
date
time
unix_seconds
unix_milliseconds
year
month
day
hour
minute
second
day_of_week
timezone
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Unix Timestamp Converter API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
Unix Timestamp Converter requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The Unix Timestamp Converter API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for Unix Timestamp Converter
Official Unix Timestamp Converter packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Unix Timestamp Converter works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Unix Timestamp Converter?
How many credits does Unix Timestamp Converter cost?
Each successful Unix Timestamp Converter API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful unix timestamp converter lookups.
Can I use Unix Timestamp Converter in production?
The free plan is for testing and development only. For production use of Unix Timestamp Converter, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Unix Timestamp Converter from a browser?
What happens if I exceed my Unix Timestamp Converter credit limit?
When you reach your monthly credit limit, Unix Timestamp Converter API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








