Transactions
HashGuild allows developers to access their APIs in order to interact with marketplace mechanics. Thus, developers can trust proven infrastructure for handling transactions, without the need to invest heavily in similar infrastructure to allow transactions on a highly secure and scalable method. The team has worked lots to come up with this infrastructure and it is more than battle-tested.
The following explains what the endpoints though and what needs to be accounted for, to have a seemless and reliable integration.
The Transaction API
All transactions on HashGuild consist of two API calls - one for composing a transaction, currently only Hashpack transactions are being supported, and a second to confirm the transaction after a success callback.
The HashGuild system starts listening for transaction success after a transaction was built - so, in theory, there is no need for the second confirmation endpoint. Nonetheless, to decrease waiting time for endusers as well as for better performance and usability, it is more than recommended to use the second endpoint.
No transactions without a HG User
All NFTs are associated with an account - thus, a user needs to be existing on HashGuild prior a transactions can be made. If no user is existing, the endpoint will report a missing user.
Properties - Signed Transaction Data
- Name
byteArray- Type
- string
- Description
The byte array of the transaction.
- Name
transactionMetadata- Type
- string
- Description
Metadata containing the account to sign and if the transaction should be returned.
Properties - Transaction Success
Coming soon.
Resources - Transactions
List NFTs
Learn about to how NFT listing on HashGuild works and how to list NFTs from outside.
Create Offers
Learn about the offering system and how to place orders via the HG endpoints.
Transact NFTs
Learn how to create buy orders, how transactions work and how to integrate seemingly.