---
title: "Demo Web App API"
description: "Disclaimer: This document is an example only intended to show the format for the workflow. It is not real-world customer-ready API documentation."
url: "https://console.staging.9fin.com/apis/demo-webapp-staging/docs/demo-webapp"
image: "https://console.staging.9fin.com/_og/d/c_Ocean.takumi,title_Demo+Web+App+API,description_~RGlzY2xhaW1lcjogVGhpcyBkb2N1bWVudCBpcyBhbiBleGFtcGxlIG9ubHkgaW50ZW5kZWQgdG8gc2hvdyB0aGUgZm9ybWF0IGZvciB0aGUgd29ya2Zsb3cuIEl0IGlzIG5vdCByZWFsLXdvcmxkIGN1c3RvbWVyLXJlYWR5IEFQSSBkb2N1bWVudGF0aW9uLg,props_eyJ0aGVtZSI6eyJtb2RlIjoibGlnaHQiLCJjb2xvcnMiOnsicHJpbWFyeSI6IiMxNTVFRUYifX19,p_Ii9hcGlzL2RlbW8td2ViYXBwLXN0YWdpbmcvZG9jcy9kZW1vLXdlYmFwcCI,s_Ek8gSwLZizoe688E.png"
---

# Demo Web App API

**Disclaimer**: This document is an example only intended to show the format for the workflow. It is not real-world customer-ready API documentation.

This document is a usage guide for the `demo-webapp` service exposed through Kong under the `/demo` base path. It accompanies the [OpenAPI specification](https://api.staging.9fin.com/demo) and is intended for developers integrating with the demo-webapp API.

## [Base URL](#base-url)

```text
https://api.staging.9fin.com/demo
```

The proxy host varies by environment — replace `api.staging.9fin.com` with the host for the environment you're targeting. The `/demo` suffix is fixed and identifies the demo-webapp service in Kong.

## [Authentication](#authentication)

The API accepts:

-   **API key** in the `apikey` header:
    
    ```text
    apikey: <key>
    ```
    

## [Endpoints](#endpoints)

### [`GET /healthz` — health check](#get-healthz-health-check)

Returns `200 OK` with a `StatusMessage` payload when the upstream service is reachable.

```json
{ "status": "success", "msg": "OK" }
```

Use this for liveness probes and synthetic monitoring.

### [`GET /api/print-headers` — print incoming headers](#get-apiprint-headers-print-incoming-headers)

Logs the incoming request headers to the service's stdout and echoes them back in the response body. Useful for verifying which headers Kong is forwarding to the upstream service.

```json
{ "status": "success", "headers": { "host": "...", "user-agent": "..." } }
```

## [Support](#support)

Questions about the demo service belong in `#ddep-team-platform-engineering` on Slack. Issues with Kong routing or the release workflow itself go to `#ddep-team-platform-engineering` as well.