Developer: API Requests, bugs, etc

Currently it is possible to use math to determine a user's rewards for the current/pending week, but if there's an error with an API call, it can skew the results. Therefore it would be better if we could get this information directly from Rally with a JIT call instead; ideally one that basically just took a coinsymbol and wallet_id and returned all the data from the Rewards tab on the website. Also there is currently no way to get the Avg. Balance this week nor the Avg. Balance last 4 weeks. Really as it stands the existing Rewards APIs aren't as useful with v2 of rewards and could probably use a thorough rework.

I was just thinking that it'd be pretty useful to know if they'd just created the user account today. Then we could build some kind of benefit system for new users. It would also be cool if it came with like, 5 most recent transactions. For instance, WALLS just did a match of up to 10 COINs with new USD purchases. With these two additions, they'd be able to automate extra benefits for new accounts on top of the USD BUYs.

Please add a Twitch Link/Connection for all users, and then please return the Twitch 'user_id' to the 'UserInfo' API call.

Problem: Since we're currently forced to use the username, if users change their Discord Username, any connections will break. (This also presents a security risk... if an authed user changes their username, an attacker could change to that old username and act as the old user.) Solution: Return the discord 'UserID' which does not ever change. This should be a fairly easy fix, just adding the 'UserID' to the 'UserInfo' API call. :)

Use case: creator creates an offering of 10 limited edition grab bags of exclusive merchandise. Would be nice to have an API that a bot could call to find out how may are left. I.e., rather than having fans constantly ask "Are the X all gone?" they could type a bot command to see how many were left.

Webhooks will sometimes show the toRbnUserID, and sometimes will not, depending on which action. It would be really convenient to have as consistent information as possible; especially always having the transaction id in case we need to look up more information.

It would be useful to have, in addition to the TRANSFER event, a TRANSFER_TO_ME event. This would be similar to the DONATE event, except that it would be usable by non-creators. (Alternately - the DONATE event could be used, but allowed for non-creators.) The information included would be the same as for DONATE and TRANSFER, but would always include the "creator approved" data - so the recipient would always be able to determine who has sent the coin. It is important to note that this would provide no more data than is already available in a user's portfolio transactions. It would just provide an automated way to do so. Use cases for this allow for a "Vending machine" (or "Jukebox" or "Arcade game") model, where a person could deposit coin first and then take some action based on how much has been deposited. The advantage of this over an OAuth "initiate transfer" is that it does not need to be initiated through a website or a web interface - it could be initiated from the Rally website or through something like the discord bot.

When checking to see if a user has enough of a certain CC, I can only check their portfolio. But due to flow-control, they might not have access to all of that at that moment in time.