Relative Time Formatter API GET

Relative Time Formatter is a tool for converting timestamps and dates to human-readable relative time formats like '2 hours ago' or 'in 3 days'. It supports multiple styles and custom reference times for flexible time representation.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/relativetimeformatter

Verification

Format

No key required to try it. Get a key to use it in your app.

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // Relative Time Formatter response payload
  }
}

About the Relative Time Formatter API

Relative Time Formatter works by calculating the time difference between dates and expressing it in the most appropriate unit (seconds, minutes, hours, days, weeks, months, years) with customizable formatting styles.

What people use it for

Social Media: Display post timestamps as relative times like '5 minutes ago' in feeds and timelines
Activity Logs: Show user activity and system events with human-readable time references
Notifications: Format notification timestamps for better user comprehension and engagement
Analytics: Present time-based data and metrics in accessible relative time formats

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use Relative Time Formatter

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the Relative Time Formatter API.

Read the docs →

What does the Relative Time Formatter API do?

How do I authenticate Relative Time Formatter API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the Relative Time Formatter API cost?

Each call spends 2 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the Relative Time Formatter API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the Relative Time Formatter API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the Relative Time Formatter API use?

GET over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

Request parameters — GET /v1/relativetimeformatter

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`timestamp`Required	string	`1609459200`	Unix timestamp in seconds or milliseconds timestamp

Optional

Parameter	Type	Example	Description
`reference`Optional	string	`2024-06-01T00:00:00Z`	Reference time to compare against (default: current time) date
`style`Optional	string	`short`	Output style `shortlongabbreviated` default short

Example request

1
2

curl "https://api.apiverve.com/v1/relativetimeformatter?timestamp=1609459200&reference=2024-06-01T00%3A00%3A00Z&style=short" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response — GET /v1/relativetimeformatter

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "target_date": "2021-01-01T00:00:00Z",
    "reference_date": "2025-12-16T22:28:24.459Z",
    "relative_time": "4 years ago",
    "is_past": true,
    "is_future": false,
    "difference_ms": -156464904459,
    "primary_unit": "year",
    "primary_value": 4,
    "all_units": {
      "years": 4,
      "months": 59,
      "weeks": 258,
      "days": 1810,
      "hours": 43462,
      "minutes": 2607748,
      "seconds": 156464904,
      "milliseconds": 156464904459
    },
    "style": "short"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`target_date`	string	`"2021-01-01T00:00:00Z"`	The date being described
`reference_date`	string	`"2025-12-16T22:28:24.459Z"`	The date it is described relative to
`relative_time`	string	`"4 years ago"`	Relative time formatted string (e.g., '2 hours ago')
`is_past`	boolean	`true`	Whether the target date falls before the reference date
`is_future`	boolean	`false`	Whether the target date falls after the reference date
`difference_ms`	number	`-156464904459`	Gap between the two dates in milliseconds
`primary_unit`	string	`"year"`	Primary time unit used in formatting
`primary_value`	number	`4`	Numeric value of the time unit
`all_units`	object	`{...}`	The same gap expressed in every unit
`years`	number	`4`	Gap in years
`months`	number	`59`	Gap in months
`weeks`	number	`258`	Gap in weeks
`days`	number	`1810`	Gap in days
`hours`	number	`43462`	Gap in hours
`minutes`	number	`2607748`	Gap in minutes
`seconds`	number	`156464904`	Gap in seconds
`milliseconds`	number	`156464904459`	Gap in milliseconds
`style`	string	`"short"`

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 2 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	Relative Time Formatter calls	Per 1,000 calls
Free	Free	200	100	Free
Starter	$29.99	200,000	100,000	$0.30
Pro	$99.99	1,000,000	500,000	$0.20
Mega	$299.99	4,000,000	2,000,000	$0.15

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — GET /v1/relativetimeformatter

No SDK to install — this is a plain HTTPS call to /v1/relativetimeformatter with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/relativetimeformatter" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/relativetimeformatter-apiSource, issues and the examples this page is built from.ReferenceRelative Time Formatter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/relativetimeformatternpm apiverve-relativetimeformatterPyPI APIVerve.API.RelativeTimeFormatterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — GET /v1/relativetimeformatter

Install the Node.js SDK, then call the Relative Time Formatter API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/relativetimeformatter

Node.js

const res = await fetch("https://api.apiverve.com/v1/relativetimeformatter", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/relativetimeformatterThe published Node.js client, versioned and signed.GitHubapiverve/relativetimeformatter-apiSource, issues and the examples this page is built from.ReferenceRelative Time Formatter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

apiverve-relativetimeformatterPyPI APIVerve.API.RelativeTimeFormatterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/relativetimeformatter

Install the Python SDK, then call the Relative Time Formatter API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — PyPI

pip install apiverve-relativetimeformatter

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/relativetimeformatter",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

PyPIapiverve-relativetimeformatterThe published Python client, versioned and signed.GitHubapiverve/relativetimeformatter-apiSource, issues and the examples this page is built from.ReferenceRelative Time Formatter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/relativetimeformatternpm APIVerve.API.RelativeTimeFormatterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — GET /v1/relativetimeformatter

Install the C# / .NET SDK, then call the Relative Time Formatter API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.RelativeTimeFormatter

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/relativetimeformatter");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.RelativeTimeFormatterThe published C# / .NET client, versioned and signed.GitHubapiverve/relativetimeformatter-apiSource, issues and the examples this page is built from.ReferenceRelative Time Formatter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/relativetimeformatternpm apiverve-relativetimeformatterPyPI

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/relativetimeformatter

No SDK to install — this is a plain HTTPS call to /v1/relativetimeformatter with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/relativetimeformatter", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/relativetimeformatternpm apiverve-relativetimeformatterPyPI APIVerve.API.RelativeTimeFormatterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/relativetimeformatter

No SDK to install — this is a plain HTTPS call to /v1/relativetimeformatter with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/relativetimeformatter");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

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

Resources

Also published for

@apiverve/relativetimeformatternpm apiverve-relativetimeformatterPyPI APIVerve.API.RelativeTimeFormatterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/relativetimeformatter

No SDK to install — this is a plain HTTPS call to /v1/relativetimeformatter with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/relativetimeformatter")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/relativetimeformatternpm apiverve-relativetimeformatterPyPI APIVerve.API.RelativeTimeFormatterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Data Conversion

View all 33 →

All articles →

Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read

Generate PDFs from HTML with an APIConvert HTML to PDF programmatically. Tutorial covering invoices, reports, receipts, and certificates with code examples.Read

Automating Visual Testing With ScreenshotsCatch visual bugs before users do. Here's how to add screenshot-based testing to your workflow.Read

Relative Time Formatter API GET

Try it — live request, no key required

About the Relative Time Formatter API

What people use it for

Ways to call it

Other ways to use Relative Time Formatter

Questions.

Request parameters — GET /v1/relativetimeformatter

Required

Optional

Authentication

Response — GET /v1/relativetimeformatter

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/relativetimeformatter

Resources

Also published for

Call it from Node.js — GET /v1/relativetimeformatter

Resources

Also published for

Call it from Python — GET /v1/relativetimeformatter

Resources

Also published for

Call it from C# / .NET — GET /v1/relativetimeformatter

Resources

Also published for

Call it from Go — GET /v1/relativetimeformatter

Resources

Also published for

Call it from PHP — GET /v1/relativetimeformatter

Resources

Also published for

Call it from Ruby — GET /v1/relativetimeformatter

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Relative Time Formatter API

Data Conversion

Related articles

Ready to build with Relative Time Formatter? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog