What this deployment is running

Tells you which deployment answered your call, what timezone its clock
is set to, the time on that clock, and a short version number for the
software it is running. It reads no data of yours, checks nothing
against your company, and returns no business information.

You need a credential for this call. That changed on 2026-10-19:
this path used to work without one, and it also used to return the full
commit identifier, the branch name and the install time. Those three
together told anyone who could reach the server exactly which code it
was running and how long it had been running unchanged, which is not
something an API should hand to a stranger. If you had a monitor calling
this path anonymously, point it at GET /api/v4/ping instead — that
path still needs no credential and still reports reachability.

Why the time comes back twice

serverTime gives you the same moment twice: appZone on the server's
own clock, with its UTC offset attached, and utc in UTC. That is
deliberate, and the pair is the useful part.

Either value on its own tells you very little. utc is the same
instant everywhere in the world, so it says nothing about how this
server is set up. And timestamp in the meta block of every reply
from this API carries the US Eastern offset by design, whatever zone the
server happens to run in — a stamp alone cannot tell you whether that
offset was measured or assumed. Reading the two halves of serverTime
together, against the zone named in timeZone, is what actually
settles the question.

What version tells you, and what a null does not mean

version is a short label for the build this deployment installed —
enough to tell two deployments apart and to quote in a bug report, and
deliberately not enough to identify the exact source. Quote it as you
received it; do not try to expand it.

A null here means "not recorded", never "no build". Some
environments have never had this stamp written, so version comes back
empty even though the service is plainly running and answering you.
Treat an empty value as unknown — it is not a statement that anything
is missing or wrong, and it says nothing about whether the deployment is
current.

source is there so you do not have to guess which case you are in.
unknown means nothing was ever recorded here. deploy means this
deployment did record its build, so an empty version is a gap in that
record rather than an absence of one. Read source first.

If you read build.source, move to source — by 19 January 2027

source used to live inside a build object. It is now at the top
level, and build.source is still sent beside it so that nothing you
already have stops working. build is removed on 19 January 2027.

The two always agree — they are rendered from one value, not copied — so
switching is a one-line change and you can make it whenever you like
before that date. Nothing else is moving, and build will not grow back:
the full commit identifier, the branch name and the install time that
object also used to carry were removed on 19 October 2026 for the reasons
below, and they are not part of this migration.

What is deliberately not here

This reply is a fixed, short list of fields, and it is meant to stay
that way. It carries nothing about how the service is put together
internally — no infrastructure, no database details, no file locations,
no software versions, and nothing about credentials.

It also no longer carries the full commit identifier, the branch or tag
name, or the time the deployment was installed. All three were removed
on 2026-10-19 and are not coming back: a branch name leaks internal
naming, an install time measures how long a given build has been running
without a patch, and the full commit identifies the exact source. These
are omitted on purpose rather than by oversight, so please do not ask
for them to be added.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Responses

Language
Credentials
Bearer
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json