Automate ApiDapp
HumDay reads ApiDapp’s own published API description and derives 30 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What HumDay can do in ApiDapp
13 documented operations change something in ApiDapp.
- POSTCreate new account
/account - POSTCreate a new smart contract
/contract - POSTCreate a new transaction.
/transaction - POSTCreate personal wallet
/wallet - POSTSend payment from the account held within the wallet
/wallet/account/{id}/pay - POSTCall the contract
/contract/{id} - POSTTransfer tokens to another account
/erc20/{address} - POSTUpdate key
/key - POSTUpdate erc20
/erc20 - POSTUpdate account
/wallet/account - DELETEDelete key
/key/{key} - POSTUpdate erc20
/wallet/account/{id}/erc20 - POSTUpdate contract
/wallet/account/{id}/contract
What HumDay can read from ApiDapp
These are the operations a schedule or a trigger can watch.
- GETGet a list of supported blockchains
/blockchain - GETAccess detailed block information
/block - GETGet token information such as name, total amount in circulation, etc
/erc20 - GETGet current account balance
/wallet - GETGet API version info
/version - GETGet information about particular block
/block/{id} - GETGet account balance
/account/{id} - GETGet contract balance
/contract/{id} - GETGet information about blockchain woth given id
/blockchain/{id} - GETGet information amout token balance in the account
/erc20/{address} - GETGet information about transaction by the transaction hash value
/transaction/{hash} - GETGet account balance
/wallet/account/{id} - GETGet transaction count within block
/block/{id}/transaction - GETGet receipt detail information
/transaction/{hash}/receipt - GETGet information about particular transaction within block
/block/{id}/transaction/{index} - GETRead key
/key - GETRead account
/wallet/account
How automating ApiDapp works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live ApiDapp account.
- Grant access, then go live. You approve the specific ApiDapp operations it may use — and only those.
Automate ApiDapp with these
- Stripe442 operations
- Zuora Reference Billing428 operations
- bunq421 operations
- PayRun.IO389 operations
- Sinao272 operations
- Xero Accounting224 operations
- The Plaid191 operations
- Biapi Budgea Documentation167 operations
- Naviplancentral Advicent.FactFinderService151 operations
- Bigredcloud Big Red Cloud111 operations
- Codat Accounting105 operations
- Portfoliooptimizer Portfolio Optimizer83 operations
Categories
Questions about ApiDapp automation
- Can HumDay connect to ApiDapp?
- Yes. HumDay reads ApiDapp's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 30 operations are documented.
- Do I need to write code to automate ApiDapp?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your ApiDapp account.
- What can HumDay do in ApiDapp?
- 13 of the 30 documented operations change something in ApiDapp, and 17 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my ApiDapp account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to ApiDapp is held behind that approval.
Where this came from
The operations above are read from a published API description for ApiDapp at apidapp.s3.amazonaws.com/ApiDapp-Start-swagger-7/ApiDapp-Start-swagger+(7).json. Descriptions are the provider’s own words, not ours. Last published 2021-07-19.