Lookup KTL identity
const url = 'https://localhost:3001/api/api/v1/ktl/lookup/example';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://localhost:3001/api/api/v1/ktl/lookup/examplePublic: look up the Key Transparency Log records for a wallet address. The newest entry carries an inclusion proof against the latest published root. Roots are unsigned in this deployment, so a proof that verifies shows consistency with the log this server publishes and is not by itself evidence that the key is genuine. No authentication is required, and that is deliberate: a log only credentialed callers can read is not a transparency log, and a credential would make each query an attributable (authenticated reader x named subject x time) record on a route that already carries the subject address in the path. An unknown wallet returns 200 with an empty entries array, never 404. Returns 400 when the address fails normalization, and 503 unless the operator set ZENTALK_KTL_PUBLIC_READ=true - the deployment default is off, which clients type as disabled rather than as a failure.
Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Wallet address to look up
Responses
Section titled “Responses”OK
object
Examplegenerated
{}Bad Request
object
Examplegenerated
{ "error": "example", "success": true}Internal Server Error
object
Examplegenerated
{ "error": "example", "success": true}Service Unavailable
object
Examplegenerated
{ "error": "example", "success": true}