kpay api alias

An edge alias. It forwards /hapi/<path> and /api/<path> to the backend and adds nothing of its own — no auth, no rate limiting, no opinion. What answers is the KPAY backend.

Surfaces

`/hapi/<path>`	the backend, verbatim. Method, body and query are forwarded.
`/api/<path>`	the same, under a second name.
`/hapi/ws`	the backend WebSocket (Upgrade). Used by signers to subscribe to the pool.

Try one

`/hapi/kpool/signers?network=testnet`	who is signing right now
`/hapi/kpool/txList?network=testnet&since=600`	what is waiting for signatures
`/hapi/kpool/txRead?network=testnet&txid=<txid>&pch=<pch>&detail=1`	one pooled transaction, with signatures and verdicts
`/hapi/kpool/verdicts?network=testnet&txid=<txid>&pch=<pch>`	what each signer decided about it

Worth knowing

Every response is whatever the backend returned, including its status.
These are public reads. Writing (a signature, an announcement, a verdict) is possible without a login but every write is signed by a key and verified, so nothing can be posted in another key's name.
A signer reaches this host for both the pool and the doorbell — see the docs link for the two lines of config that name it.

Machine readable

/?format=json — or send Accept: application/json.

Documentation

https://labs.katomia.com/future/v3/help/