What this deployment is running (no credential needed)

GET https://api.lendingwise.com/api/v4/platform/runtime

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

You do not need a credential for this call. It is one of two paths
in this API that work without one — GET /api/v4/ping is the other.

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 is always in UTC by design, so it reads the same whatever
the server's timezone is — you cannot work the timezone out from it.
Reading the two halves of serverTime together, against the zone named
in timezone, is what actually settles the question.

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

build is what the deployment recorded about itself when it was last
installed: the commit it checked out, the branch or tag that commit came
from, and when that happened.

A null here means "not recorded", never "no build". Some
environments have never had this stamp written, so all three fields come
back empty even though the service is plainly running and answering you.
Treat empty values as unknown — they are not a statement that anything
is missing or wrong, and they say nothing about whether the deployment
is current.

build.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 field is a gap in that
record rather than an absence of one. Read source before you read the
other three.

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. Those are omitted
on purpose rather than by oversight, so please do not ask for them to
be added: the value of this endpoint being safe to call without signing
in depends on it staying this narrow.