Automate TokenJay
HumDay reads TokenJay’s own published API description and derives 27 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 TokenJay is
Please see usage policies on tokenjay.app
API host: api.tokenjay.app
What HumDay can do in TokenJay
4 documented operations change something in TokenJay.
- POSTCreates a new payment request.
/payment/addrequest - POSTUpdate doit
/mosaik/babelfee/newoffer/doit - POSTUpdate new input
/mosaik/babelfee/newoffer/new-input - POSTUpdate prepare
/mosaik/tokenburn/prepare
What HumDay can read from TokenJay
These are the operations a schedule or a trigger can watch.
- GETLists known peers sorted by block height
/peers/list - GETReturns the state of a payment request.
/payment/state/{requestId} - GETReturns state of AgeUSD at this moment
/ageusd/info - GETLists price and available volume for SigmaRSV
/sigrsv/price - GETLists price and available volume for SigmaUSD
/sigusd/price - GETBuilds ErgoPayRequest for SigRSV exchange
/sigrsv/exchange/ - GETBuilds ErgoPayRequest for SigUSD exchange
/sigusd/exchange/ - GETLists all blocked tokens
/tokens/listBlocked - GETLists all genuine tokens known
/tokens/listGenuine - GETLists all token prices and available volume
/tokens/prices/all - GETLists price and available volume for a certain token
/tokens/prices/{tokenId} - GETCalculates SigRSV exchange
/sigrsv/exchange/{amount}/info - GETCalculates SigUSD exchange
/sigusd/exchange/{amount}/info - GETCheck a token verification
/tokens/check/{tokenId}/{tokenName} - GETRead address
/createbabel/{address} - GETRead newoffer
/mosaik/babelfee/newoffer - GETRead babelfee
/mosaik/babelfee/ - GETRead tokenburn
/mosaik/tokenburn - GETRead boxconsolidation
/mosaik/boxconsolidation/ - GETRead boxId
/cancelbabel/{boxId} - GETRead notificationcheck
/mosaik/babelfee/notificationcheck - GETRead uuid
/mosaik/tokenburn/get/{uuid} - GETRead p2pkaddress
/mosaik/boxconsolidation/consolidate/{p2pkaddress}
How automating TokenJay 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 TokenJay account.
- Grant access, then go live. You approve the specific TokenJay operations it may use — and only those.
Automate TokenJay 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 TokenJay automation
- Can HumDay connect to TokenJay?
- Yes. HumDay reads TokenJay's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 27 operations are documented.
- Do I need to write code to automate TokenJay?
- 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 TokenJay account.
- What can HumDay do in TokenJay?
- 4 of the 27 documented operations change something in TokenJay, and 23 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my TokenJay 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 TokenJay is held behind that approval.
Where this came from
The operations above are read from a published API description for TokenJay at api.tokenjay.app/api-docs. Descriptions are the provider’s own words, not ours. Last published 2023-03-24.