Unix Timestamp ConverterUnix Timestamp Converter API

OnlineCredit Usage:1 per callRefreshed 1 month ago
avg: 127ms|p50: 122ms|p75: 130ms|p90: 139ms|p99: 157ms

Unix Timestamp Converter is a tool for converting between Unix timestamps and human-readable dates. It supports both seconds and milliseconds formats.

The Unix Timestamp Converter API provides reliable and fast access to unix timestamp converter data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.

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

URL
https://api.apiverve.com/v1/unixtimestamp

Code Examples

Here are examples of how to call the Unix Timestamp Converter API in different programming languages:

cURL Request
curl -X GET \
  "https://api.apiverve.com/v1/unixtimestamp?timestamp=1609459200&format=seconds" \
  -H "X-API-Key: your_api_key_here"
JavaScript (Fetch API)
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);
Python (Requests)
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)
Node.js (Native HTTPS)
const https = require('https');
const url = require('url');

const options = {
  method: 'GET',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  }
};

const req = https.request('https://api.apiverve.com/v1/unixtimestamp?timestamp=1609459200&format=seconds', options, (res) => {
  let data = '';
  res.on('data', (chunk) => data += chunk);
  res.on('end', () => console.log(JSON.parse(data)));
});

req.end();
PHP (cURL)
<?php

$ch = curl_init();

curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/unixtimestamp?timestamp=1609459200&format=seconds');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'GET');
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    'X-API-Key: your_api_key_here',
    'Content-Type: application/json'
]);

$response = curl_exec($ch);
curl_close($ch);

$data = json_decode($response, true);
print_r($data);

?>
Go (net/http)
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))
}
Ruby (Net::HTTP)
require 'net/http'
require 'json'

uri = URI('https://api.apiverve.com/v1/unixtimestamp?timestamp=1609459200&format=seconds')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true

request = Net::HTTP::Get.new(uri)
request['X-API-Key'] = 'your_api_key_here'
request['Content-Type'] = 'application/json'

response = http.request(request)
puts JSON.pretty_generate(JSON.parse(response.body))
C# (HttpClient)
using System;
using System.Net.Http;
using System.Text;
using System.Threading.Tasks;

class Program
{
    static async Task Main(string[] args)
    {
        using var client = new HttpClient();
        client.DefaultRequestHeaders.Add("X-API-Key", "your_api_key_here");

        var response = await client.GetAsync("https://api.apiverve.com/v1/unixtimestamp?timestamp=1609459200&format=seconds");
        response.EnsureSuccessStatusCode();

        var responseBody = await response.Content.ReadAsStringAsync();
        Console.WriteLine(responseBody);
    }
}

Authentication

The Unix Timestamp Converter API requires authentication via API key. Include your API key in the request header:

Required Header
X-API-Key: your_api_key_here

Learn more about authentication →

Interactive 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

ParameterTypeRequiredDescriptionDefaultExample
timestampstringrequired
Unix timestamp to convert
Format: timestamp (e.g., 1609459200)
-1609459200
formatstringoptional
Timestamp format
Supported values: secondsmillisecondssms
secondsseconds

Option 2: Date to Timestamp

ParameterTypeRequiredDescriptionDefaultExample
datestringrequired
Date string to convert (ISO 8601 format)
-2021-01-01T00:00:00Z
formatstringoptional
Output timestamp format
Supported values: secondsmillisecondssms
secondsseconds

Response

The Unix Timestamp Converter API returns responses in JSON, XML, YAML, and CSV formats:

Example Responses

JSON Response
200 OK
{
  "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"
  }
}
XML Response
200 OK
<?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>
YAML Response
200 OK
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
CSV Response
200 OK
keyvalue
timestamp1609459200
timestamp_formatseconds
iso_86012021-01-01T00:00:00Z
rfc_2822Fri, 01 Jan 2021 00:00:00 GMT
date1/1/2021
time12:00:00 AM
unix_seconds1609459200
unix_milliseconds1609459200000
year2021
month1
day1
hour0
minute0
second0
day_of_weekFriday
timezoneUTC

Response Structure

All API responses follow a consistent structure with the following fields:

FieldTypeDescriptionExample
statusstringIndicates whether the request was successful ("ok") or failed ("error")ok
errorstring | nullContains error message if status is "error", otherwise nullnull
dataobject | nullContains 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:

FieldTypeSample ValueDescription
timestampnumber1609459200-
timestamp_formatstring"seconds"-
iso_8601string"2021-01-01T00:00:00Z"-
rfc_2822string"Fri, 01 Jan 2021 00:00:00 GMT"-
datestring"1/1/2021"-
timestring"12:00:00 AM"-
unix_secondsnumber1609459200-
unix_millisecondsnumber1609459200000-
yearnumber2021-
monthnumber1-
daynumber1-
hournumber0-
minutenumber0-
secondnumber0-
day_of_weekstring"Friday"-
timezonestring"UTC"-

Headers

Required and optional headers for Unix Timestamp Converter API requests:

Header NameRequiredExample ValueDescription
X-API-Keyrequiredyour_api_key_hereYour APIVerve API key. Found in your dashboard under API Keys.
Acceptoptionalapplication/jsonSpecify response format: application/json (default), application/xml, or application/yaml
User-AgentoptionalMyApp/1.0Identifies your application for analytics and debugging purposes
X-Request-IDoptionalreq_123456789Custom request identifier for tracking and debugging requests
Cache-Controloptionalno-cacheControl caching behavior for the request and response

Learn more about 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.

Test Unix Timestamp Converter in the GraphQL Explorer to confirm availability and experiment with queries.

Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.

GraphQL Endpoint
POST https://api.apiverve.com/v1/graphql
GraphQL Query Example
query {
  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 supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call Unix Timestamp Converter directly from browser-based applications without proxy servers.

CORS HeaderValueDescription
Access-Control-Allow-Origin*Accepts requests from any origin
Access-Control-Allow-Methods*Accepts any HTTP method
Access-Control-Allow-Headers*Accepts any request headers

Browser Usage: You can call Unix Timestamp Converter directly from JavaScript running in the browser without encountering CORS errors. No proxy server or additional configuration needed.

Learn more about CORS support →

Rate Limiting

Unix Timestamp Converter API requests are subject to rate limiting based on your subscription plan. These limits ensure fair usage and maintain service quality for all Unix Timestamp Converter users.

PlanRate LimitDescription
Free5 requests/minHard rate limit enforced - exceeding will return 429 errors
StarterNo LimitProduction ready - standard traffic priority
ProNo LimitProduction ready - preferred traffic priority
MegaNo LimitProduction ready - highest traffic priority

Learn more about rate limiting →

Rate Limit Headers

When rate limits apply, each Unix Timestamp Converter response includes headers to help you track your usage:

HeaderDescription
X-RateLimit-LimitMaximum number of requests allowed per time window
X-RateLimit-RemainingNumber of requests remaining in the current window
X-RateLimit-ResetUnix timestamp when the rate limit window resets

Handling Rate Limits

Free Plan: When you exceed your rate limit, Unix Timestamp Converter returns a 429 Too Many Requests status code. Your application should implement appropriate backoff logic to handle this gracefully.

Paid Plans: No rate limiting or throttling applied. All paid plans (Starter, Pro, Mega) are production-ready.

Best Practices for Unix Timestamp Converter:

  • Monitor the rate limit headers to track your Unix Timestamp Converter usage (Free plan only)
  • Cache unix timestamp converter responses where appropriate to reduce API calls
  • Upgrade to Pro or Mega for guaranteed no-throttle Unix Timestamp Converter performance

Note: Unix Timestamp Converter rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits when using Unix Timestamp Converter on Free tier.

Error Codes

The Unix Timestamp Converter API uses standard HTTP status codes to indicate success or failure:

CodeMessageDescriptionSolution
200OKRequest successful, data returnedNo action needed - request was successful
400Bad RequestInvalid request parameters or malformed requestCheck required parameters and ensure values match expected formats
401UnauthorizedMissing or invalid API keyInclude x-api-key header with valid API key from dashboard
403ForbiddenAPI key lacks permission or insufficient creditsCheck credit balance in dashboard or upgrade plan
429Too Many RequestsRate limit exceeded (Free: 5 req/min)Implement request throttling or upgrade to paid plan
500Internal Server ErrorServer error occurredRetry request after a few seconds, contact support if persists
503Service UnavailableAPI temporarily unavailableWait and retry, check status page for maintenance updates

Learn more about error handling →

Need help? Contact support with your X-Request-ID for assistance.

Integrate Unix Timestamp Converter with SDKs

Get started quickly with official Unix Timestamp Converter SDKs for your preferred language. Each library handles authentication, request formatting, and error handling automatically.

Available for Node.js, Python, C#/.NET, and Android/Java. All SDKs are open source and regularly updated.

Integrate Unix Timestamp Converter with No-Code API Tools

Connect the Unix Timestamp Converter API to your favorite automation platform without writing code. Build workflows that leverage unix timestamp converter data across thousands of apps.

All platforms use your same API key to access Unix Timestamp Converter. Visit our integrations hub for step-by-step setup guides.

Frequently Asked Questions

How do I get an API key for Unix Timestamp Converter?
Sign up for a free account at dashboard.apiverve.com. Your API key will be automatically generated and available in your dashboard. The same key works for Unix Timestamp Converter and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.
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?
Yes! The Unix Timestamp Converter API supports CORS with wildcard configuration, so you can call it directly from browser-based JavaScript without needing a proxy server. See the CORS section above for details.
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.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?