Developer: API Requests, bugs, etc

Google login and Rally signup on the Oauth screen do not work. These should be removed so that users don't get confused and try to login through them.

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.

Increase the security of accounts by offering users the ability to enable 2FA.

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. :)

CONVERT will show converts from CC to RLY, but not from RLY to CC.

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.

We need to be able to know the context of an oAuth call to be able to make widgets and such which can be used across domains. Right now there is no way to tie a finished oAuth call to the original context. There is a 'state' variable which is part of the original redirect which Rally provides ( https://rallyio-prod.auth.us-west-2.amazoncognito.com/login?client_id=someclientid&response_type=code&scope=aws.cognito.signin.user.admin+email+openid+phone+profile&redirect_uri=https://api.rally.io/v1/oauth/callback/&state=13cd5c86dab4829ba4fc72399ab13caa0e489f0f ) But it does not persist through the login, and only a 'code' variable is returned, which isn't tied to anything in the past. State variable is often used in oAuth for this purpose. So.. can we either persist the 'state' variable through the return oauth callback, or have another passthrough param?

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.