Skip to main content

Core API Version v1

Released September 15th, 2023 | Supported until To be defined

Changelog

Core API: New Properties: useGasEstimation and priorityFee

April 16th, 2024

Two new properties have been added to Deploy Smart Contract and Send Transaction endpoints:

  • useGasEstimation: If this property is set to false in the json body, then the platform will not estimate the gas before sending the transaction or deploying the smart contract. Sometimes the error returned by the API comes from this gas estimation and does not clarify what is happening. Setting this property to false will give a better description of the error in some cases. However, if we do not add this estimate, it will not protect us from possible low gas errors and we may pay gas for an erroneous transaction.

  • priorityFee: If gasPrice ownership is not reported and we use the price suggested by the blockchain, we may want to add a priority fee to speed up the transaction process. This is also useful on Arbitrum networks, where the suggested price is often lower than the estimated price for the next block.

Core API: New Endpoint and improvements

April 9th, 2024

  • New endpoint that allows to query address to know if it is a smart contract. This call can be used, for example, when we receive a transaction from a transfer but we do not know if it is native or from an ERC20 token. If we execute this call with the address we receive in the "to" we will know if it represents a Smart Contract, which would indicate that it is an ERC20 or not, which would indicate a possible native transfer. See Query Address to Know if it is an Smart Contract

  • Previously, when requesting transaction information, the input data and log decoding could only be performed if the transaction was executed on a smart contract deployed through our platform. Now a new query parameter has been added to the call that allows the contractSpecsId to be set. As you know from other queries, this id contains all the contract information including the ABI and BIN. For example, if we want information about a transaction that was executed on an ERC20 that was not deployed on our platform, we just have to specify that the contractSpecsId is 20 (our ERC-20 based on openzeppelin) and it will be able to give us the input data as well as the correct decoding of the logs. See Get Transaction Information

  • Best of all, we can now perform transactions against smart contracts that are not deployed on our platform. All you need to do is provide the contract address and the contractSpecsId of a deployed contract that meets the same standards as the one you are calling, and you can make those calls. You do not need anything else!

Core API: Get Gas Estimations

February 12th, 2024

Added 3 new endpoints to request a gas estimate for contract deployment, transaction call and native asset transfer.

All the transactions sent (deploy, transaction and native transfer) to the platform will be gas validated against this estimation. If the gas limit is informed and is lower than the estimated one, an http status 400 and ERROR_GAS_UNDER_ESTIMATED error is returned

Custodied Wallet: Get Custodied Wallet Address

January 28th, 2024

Added strategyas integer value to the json response. It returns the wallet strategy (2 for 2FA and 3 for mail otp)

Get Custodied Wallet Address

ERC API: Updated several end points to meet HTTP/1.1 specification

January 23rd, 2024

The following endpoints have been updated to accept both GET and POST method requests to meet HTTP/1.1 specification:

Core API: Updates on Query Smart Contract information

January 23rd, 2024

In order to meet HTTP/1.1 specification, the endpoint accepts requests with both GET and POST methods. The field sender has been removed from the request json because it is not used anymore.

see Query Smart Contract Information

Core API: Get Available Contract Specs

January 18th, 2024

The field audited has been added to the response json. If the contract is audited this flag is set to true. If the contract is not audited it can pose various risks and potential problems. We recommend use these contracts only for testing purposes in testnet environments. Use it in mainnet networks at your own risk.

see Get Available Contract Specs

Custodied Wallet: Transfer Native Assets

December 28th, 2023

A new endpoint has been released that allows to transfer native network assets (ETH, MATIC, RBTC...) to another address account.

see Transfer native assets from custodied wallet

Custodied Wallet: Create Signature Email OTP

December 21st, 2023

It has been created a new endpoint to request a single use only OTP for a custodied wallet. The endpoint allows you to ask for an OTP to be sent by mail to your user to be used in a mutable transaction requiring signature

See Create Signature Email OTP

Web3 Core: Get Transaction Information response updated

December 19th, 2023

The response json, specifically the structure containing the transaction receipt, has been modified. The fields tokenId, from and to have been deprecated, the fields will be returned as null (tokenId) or empty string (from and to).

On the other hand, a new structure has been added with the transaction logs information.

See Get Transaction Information