In this article, we will focus on Hashport APIs which allows dApps to integrate with the Hashport infrastructure and let users port their assets across the ecosystems.
Hashport is an interoperability solution that facilitates the movement of supported digital assets across supported networks in a quick, secure and cost-effective way. We currently support 5 networks — Hedera Hashgraph, Ethereum, Polygon, Avalanche, & BNB Chain — and have added support for 15 different tokens and their wrapped versions to the platform.
(EDIT: 34 tokens supported as of December 2022)
Although users can access Hashport resources via the front end, the addition of an API empowers developers to integrate the backend HP swarm services on their terms. Full documentation of the Hashport API can be found at https://docs.hashport.network.
Hashport increases interoperability between DLT networks by enabling movement of liquidity between chains. This allows siloed networks to connect, explore different use cases and leverage innovations of each other. The Hashport platform uses a lock, mint, and burn process to provide cross-chain interoperability between these networks. We recently did a deep dive on how fungible tokens get ported across Hedera, Ethereum, & Polygon where we broke down each step to understand how porting fungible tokens on Hashport works.
The Hashport API is based on Representational State Transfer (REST) architecture and has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.
BASE URL: https://mainnet.api.hashport.network
By default, the Hashport API Docs uses curl to interact with the API over HTTPS. Although more complete documentation of the Hashport API can be found in the docs linked above, we have included a brief rundown here to help you familiarise yourself with its capabilities (and limitations):
The hashport API is meant as a curation mechanism such that a developer can ‘plan’ out a course of bridging and implement listeners to synchronise their system. We recommend using the API in conjunction with the Hedera SDK. This means that Hashport API does not cover:
- wallet management
- signing methods and contract calls
- transactional methods and other means by which Hashport submits transactions on your (and your user’s) behalf.
Hence, dApps need to have the following prerequisites to successfully integrate with the Hashport API:
- an EVM Wallet Interface (e.g. MetaMask)
- an HBAR Wallet Interface (e.g. HashPack)
- users ability to navigate and interact with the above interfaces
Visit the documentations page to know more about the Hashport APIs, reach out via our contact form or slide into our Twitter DMs if you're interested in learning more.
Hashport API Series:
1. Introducing the Hashport API
2. Integrating the Hashport API into dApps
3. Using the Hashport API to Port Assets
About Hashport
hashport is the enterprise-grade public utility that facilitates the movement of digital assets between distributed networks, extending their functionality in a quick, secure, and cost-effective way. In order to remain platform-neutral, hashport functions without the use of a proprietary token. The network is built on a robust and performant architecture, secured and operated by a group of industry-leading validator partners from around the world. hashport has passed a rigorous security audit and follows industry best practices; regularly performing comprehensive network tests to ensure the integrity of the network.
Website | Twitter | Reddit | Telegram | LinkedIn | YouTube | GitHub
Disclaimer: The information provided on hashport’s website does not constitute investment advice, financial advice, trading advice, or any other sort of advice. You should not treat any site content as advice.
