Authentication

Every call to the LiaaS API carries a credential. There is one credential header, and almost every operation expects it.

Get a key

1. Create an account

   Register at https://www.pteri.org/register. If you already have one, sign in at https://www.pteri.org/.

2. Generate the key in the dashboard

   API keys are generated from your pteri.org account dashboard. Copy the key when it is shown and store it somewhere your application can read it as a secret.

3. Put it in your environment

   Keep the key out of source control. The examples below read it from PTERI_API_KEY.

   export PTERI_API_KEY="your-key-here"

The header

The credential header is nodeUrlOrApiAccessKey.

In the published OpenAPI spec there are 43 operations. nodeUrlOrApiAccessKey appears as a request header on 42 of them. The one exception is GET /api/Wallet/details, which declares no headers at all and takes nodeUrlOrApiAccessKey as a query parameter instead, alongside walletName.

So the rule is: send nodeUrlOrApiAccessKey as a header everywhere, except on /api/Wallet/details, where you send it in the query string.

Example request

curl -X GET "$BASE_URL/api/Blocks/blockchain-info" \
  -H "nodeUrlOrApiAccessKey: $PTERI_API_KEY"

And the one operation that takes it as a query parameter:

curl -X GET "$BASE_URL/api/Wallet/details?nodeUrlOrApiAccessKey=$PTERI_API_KEY&walletName=my-wallet"

What the header value is

The name is literal: the header takes either an API access key or a Litecoin node URL. The SDK repository's own README shows both forms in the same argument position:

"eyJhbGciOi...bA  OR  https://liaasnode.com"

eyJhbGciOi is the base64url encoding of {"alg, so the access key is a JWT. Two consequences:

• Send the raw key. No Bearer prefix, no other scheme. The header value is the token itself.
• A JWT carries an expiry. Plan for the key to age out rather than assuming it is permanent.

Passing a node URL instead points the operation at that node — which is how self-hosted and Enterprise dedicated-node setups are addressed.

The base URL

export BASE_URL="https://liaas-sdk-919521117286.europe-west1.run.app"

That host does serve the live API. An unauthenticated GET /api/Blocks/blockchain-info against it returns a validation error naming nodeUrlOrApiAccessKey, which is the API responding, not a static file server.

Confirm this host before you hard-code it

Needs verification

It works, but it is a raw Cloud Run URL and the spec declares no servers block, so nothing marks it as the intended public endpoint. Treat it as the host that currently answers, not as a stable address. Before you bake it into a client, confirm with engineering:

• Whether this is the intended public host, or whether a branded domain is planned.
• Whether Standard and Enterprise share it. Enterprise dedicated nodes are addressed by passing the node URL in the credential header, so the base URL may differ per tenant.
• Whether a separate sandbox host exists.
• Key lifecycle: rotation, revocation, expiry, and how many keys can be active at once.
• Key scoping: whether one key reaches every operation or is limited to endpoint groups or wallets.

Other request headers

Beyond the credential, the spec uses five more request headers. They are not authentication — they identify the wallet the operation acts on, or unlock the key material it needs.

Header	Appears on	What it is for
walletName	16 operations	Names the wallet the operation targets — creating an address in it, reading its balance, addresses, or transactions, or signing with it.
encryptedPassphrase	6 operations	Unlocks an encrypted wallet for operations that touch key material: creating addresses, sending funds from a wallet, reading an address private key, and setting wallet mnemonics.
mnemonics	4 operations	The recovery phrase. Used as the alternative to encryptedPassphrase on /api/Address/address-private-key-v2, and to derive a wallet's default address.
wallet	3 operations	Appears in place of walletName on the private-key and address-screening operations. Inferred: it identifies the wallet, same as walletName; the spec does not say why the two names differ.
signature	1 operation	The signature of a signed message, passed to /api/Utilities/get-blockchain-otp to obtain a blockchain OTP.

The "what it is for" column is drawn from the endpoint summaries in the spec. Anything marked Inferred is our reading, not a statement from the spec — confirm it before relying on it.

Next

◈EndpointsThe 43 operations, grouped by resource, with the headers each one takes.→▶QuickstartGo from a fresh key to your first successful call.→