Gumball draw status
A draw mallow pays for answers with a pendingId instead of a transaction id: that id is auth's own signature, and releasing it while the draw is still pending would let the buyer resend the draw in a slot of its choosing. Poll here, about every two seconds, until each id resolves. No request ever waits on the chain. An id is readable for five minutes, and only for the machine it was issued for.
Authorization
ApiKeyAuth In: header
Path Parameters
Address of the gumball machine (base58).
1 <= lengthRequest Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/v1/sendDrawGumballTxs/string/status" \ -H "Content-Type: application/json" \ -d '{ "pendingIds": [ "string" ] }'{ "result": { "results": [ { "pending": true, "txId": "string", "error": { "message": "string" } } ] }}Send signed gumball draws POST
The second half of a draw. Sign the transactions from /v1/getDrawGumballTxs/{gumballKey} with the buyer's wallet and post them here — do not send them yourself: they need mallow's co-signature, which is only ever added here. Mallow co-signs each transaction, after a short random delay, sends it and rebroadcasts it until it confirms or expires. The delay keeps the buyer from choosing the slot a draw lands in, which decides the item drawn. Mallow never returns a co-signed transaction, so the buyer cannot send a draw on its own. Each transaction is sent at most once and must still have a live blockhash. A draw mallow pays for answers with a pendingId instead of a txId: poll /v1/sendDrawGumballTxs/{gumballKey}/status for its outcome.
Draw a Jellybean POST
Normally returns the draw transactions in txs. They are unsigned by mallow: have the buyer sign them, then post them to /v1/sendDrawJellybeanTxs/{jellybeanKey}, which co-signs and sends them. When a swapQuote is supplied and the swap cannot be bundled with the draw, the response is a two-call protocol instead: txs is empty and swapTx holds the swap alone. Sign it, send it, wait for confirmed, then call this endpoint again with swapQuote omitted — the buyer now holds the tokens, so the second call returns the draw transactions.