Public API
Last updated
Last updated
Here, you'll find everything you need to know about accessing and interacting with our Public API endpoints. Our API allows you to seamlessly integrate our services into your applications. Below is an overview of the key endpoints available to you, along with detailed descriptions and usage instructions.
Base URL for all endpoints listed on this page
https://mainnet.api.perawallet.app/v1/public/
Swagger
To use Pera Wallet Public API you must comply with the following requirements:
Please note “Data provided by Pera“ & display the Pera logo
Display the Pera Verified and Suspicious badges next to each ASA
Link to the ASA's Pera Explorer page, with the Pera logo and "View on Pera Explorer" call to action clearly visible.
All brand assets are available at our media kit.
As part of this expansion, we are restructuring our existing public endpoints.
The current v1/
endpoints will be moved to the v1/public/
path.
There will not be any change in the response format of these APIs, but the requests will be redirected to the new path starting August 1st 2024. It is important for users to migrate their projects to the new path to ensure faster access to the API.
This is a simplified endpoint that returns all verified assets in a single response. The endpoint returns verified assets with asset verification label by excluding suspicious and unverified ones. If your business logic needs to know the verified asset ids, this is the endpoint you should use. It is lightweight and doesn't require pagination.
This public endpoint returns Asset
verification information about a specific ASA
on the Algorand blockchain. This is the recommended public API for fetching the
verification status of an ASA
from Pera. More details about the verification
program can be found here: https://explorer.perawallet.app/asa-verification/
This is a simplified endpoint that returns all labeled assets in a single response. The endpoint returns verified and suspicious assets with asset verification label by excluding unverified ones. If your business logic needs to know the labeled asset ids, this is the endpoint you should use. It is lightweight and doesn't require pagination.
This public endpoint returns all assets.
This public endpoint returns details of an asset.
The Algonode IPFS service is used for convenience in thumbnail_url and media.url. We recommend you to sign-up for a dedicated plan from Algonode.