API Reference — Standard (PTERI)

This is the reference most readers want. Use it unless you are an Enterprise customer running against dedicated nodes — in that case read the Enterprise reference instead.

The full request and response detail lives in the Postman documenter:

LiaaS - Pteri Postman Documentation

This page contains the standard PTERI API reference, intended for:

• Identity verification
• Authentication
• Signature verification
• Payments via shared infrastructure

All endpoints are:

• Deterministic
• Verification-only
• Stateless where possible

---

Notes on Security

• API keys only grant access to verification APIs
• Authority always comes from wallet signatures
• No private keys are ever transmitted

If a signature is valid, the request succeeds.
If not, it fails — deterministically.

Read the three bullets above against the spec

Needs verification

Those bullets describe the intended product posture. The published OpenAPI spec does not match all of them, and we cannot resolve the difference from the spec alone:

• "No private keys are ever transmitted" does not hold across the whole surface as published. GET /api/Address/address-private-key and GET /api/Address/address-private-key-v2 return an address private key, and POST /api/Address/sign-message and POST /api/Transactions/sign-transaction take one in the request body (addressPrivatKey and addressPrivateKey respectively). Whether those routes are deprecated, restricted, or intended only for self-hosted nodes is not documented.
• "Verification-only" does not describe every operation. The spec includes state-changing routes — creating wallets and addresses, sending funds, broadcasting transactions.
• "API keys only grant access to verification APIs" implies key scoping. Nothing in the spec describes a scope mechanism; there is one credential header, nodeUrlOrApiAccessKey, on 42 of 43 operations.

Confirm the intended posture with engineering before you design around any of it. In the meantime, treat the Endpoint Index as the accurate description of what the API accepts.

---

Next

AuthenticationWhat header every request carries, and where the key comes from.→EndpointsThe operations available, grouped by resource.→