FAQs & Troubleshooting
How do I get started with your Litecoin as a Service (LiaaS) API ?
Getting started is simple. Sign up on pteri.org, create an account, and generate your API key. You can then use this key to authenticate your requests to our API. Detailed documentation is available to guide you through the integration process
How do I generate a Litecoin address using your API?
You can generate a Litecoin address by making a POST request to the /api/Address/create endpoint of our API. Per the published spec, the request carries three headers — nodeUrlOrApiAccessKey, walletName, and encryptedPassphrase — and a CreateAddressdto body with two optional properties, label and type.
An older version of this answer mentioned a Usev2 parameter taking true or yes. No such parameter appears in the published spec, and the spec defines no response schema, so what the response body contains is not documented either. Needs verification
How do I check the balance of a Litecoin address?
To check the balance of a Litecoin address, make a GET request to the /api/Address/address-balance endpoint with the address as a parameter. The response will include the current balance of the specified address.
How do I check the balance of a Litecoin wallet?
To check the balance of a Litecoin wallet, make a GET request to the /api/Wallet/balance endpoint. The wallet is identified by the walletName header, alongside nodeUrlOrApiAccessKey. The response will include the current balance of the specified wallet.
Can I integrate LiaaS API with my existing software?
Absolutely! Our API is designed to be easily integrated with existing software. We provide detailed documentation and example code to help you get started quickly.
What programming languages are supported?
Our API can be accessed using any programming language that can make HTTP requests, such as Python, JavaScript, Java, Ruby, and many others. We also provide SDKs and libraries for JavaScript developers to simplify integration.
Why do i need to reload wallets after restarting node?
When you restart your Blockchain node, the wallet is not loaded automatically for security and resource management reasons. This ensures that only explicitly requested wallets are loaded, reducing the risk of unauthorized access and resource consumption.
This answer used to point at a /api/Wallet/load-wallet endpoint taking the wallet name as a filename value. That route does not exist. It is absent from the published OpenAPI spec, and requesting it against the live API returns 404 — the same response as a made-up path. It is presumably a node-level RPC rather than a LiaaS API call. Do not build against it; see the Endpoint Index for the 43 operations the API does serve.
Does the API support multi-signature transactions?
Yes, The multi-signature process necessitates the signing of a signature, a task that can be efficiently completed by multiple addresses from distinct wallets using their respective private keys. The resulting response will encompass the signature, which can be employed to verify the transaction by all addresses participating in the signature process before it is broadcasted on the blockchain.
How do I handle errors returned by the API?
Match on the error message text. The Developer FAQs and Error Handling page lists the messages we have documented from the field, with the cause and the fix for each.
Watch the status code carefully: a failed request usually still returns 200. The API wraps responses in {"successful": …, "message": …, "data": …}, and an operation that ran and failed comes back with "successful": false and the reason in message. Branch on that field, not on the status code. A missing required header is the exception — that returns 400 with a problem+json body.
These shapes were observed against the live API rather than published in the spec, so treat them as accurate-today, not contractual. Needs verification The error reference has all three shapes side by side.