Creates a new payment request in TokenJay
A documented TokenJay operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Creates a new payment request.
- POSTChanges data · paymentPortal
api.tokenjay.app/payment/addrequest
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which TokenJay operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other TokenJay operations
- Lists known peers sorted by block heightGET · reads data
- Returns the state of a payment requestGET · reads data
- Returns state of AgeUSD at this momentGET · reads data
- Lists price and available volume for SigmaRSVGET · reads data
- Lists price and available volume for SigmaUSDGET · reads data
- Builds ErgoPayRequest for SigRSV exchangeGET · reads data
- Builds ErgoPayRequest for SigUSD exchangeGET · reads data
- Lists all blocked tokensGET · reads data
Questions
- Can HumDay creates a new payment request in TokenJay?
- Yes. This operation is published in TokenJay's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my TokenJay data?
- Yes — this is a POST operation, so it changes something in TokenJay. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your TokenJay account.
Where this came from
Read from a published API description for TokenJay at api.tokenjay.app/api-docs. The description above is the provider’s own wording, not ours. Last published 2023-03-24.