---
title: "Liveness probe"
description: "Process only, no dependency checks."
canonical_url: "https://twominutebilling.com/help/developers/api-reference/organization/liveness-probe"
---
# Liveness probe

> Process only, no dependency checks.

<api-operation method="GET" path="/healthz">
<template v-slot:docs="">

Always 200 while the process can answer. Point your orchestrator’s LIVENESS probe here, never at /health or /readyz: those check Postgres, so a database blip would be read as every API process being wedged and restart the whole fleet at once.

## Response

<table>
<thead>
  <tr>
    <th>
      Field
    </th>
    
    <th>
      Type
    </th>
    
    <th>
      Description
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        status
      </code>
    </td>
    
    <td>
      <code>
        string
      </code>
    </td>
    
    <td>
      Always <code>
        ok
      </code>
      
      .
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        service
      </code>
    </td>
    
    <td>
      <code>
        string
      </code>
    </td>
    
    <td>
      The service name.
    </td>
  </tr>
  
  <tr>
    <td>
      <code>
        env
      </code>
    </td>
    
    <td>
      <code>
        string
      </code>
    </td>
    
    <td>
      The runtime environment.
    </td>
  </tr>
</tbody>
</table>

## Status codes

<table>
<thead>
  <tr>
    <th>
      Status
    </th>
    
    <th>
      Meaning
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <code>
        200
      </code>
    </td>
    
    <td>
      Process is alive
    </td>
  </tr>
</tbody>
</table>
</template>

<template v-slot:request="">

```bash [Request]
curl "$TMBILLING_URL/healthz"
```

</template>

<template v-slot:response="">

```json [200 OK]
{
  "status": "ok",
  "service": "tmbilling-api",
  "env": "production"
}
```

</template>
</api-operation>


## Sitemap

See the full [sitemap](https://twominutebilling.com/sitemap.md) for all pages.