Developer: API Requests, bugs, etc

I feel like a Zapier would be by far the most valuable integration, since it basically would allow us to connect to any other software. Just 1 of many ideas: When a holder of a coin goes above or below a threshold, fire a zap with their email address that will tell my membership software to grant or remove access.

One thing we've noticed during the oauth process is that if you don't have a Rally account, the process is a bit cumbersome. The process includes: 1) User goes to third party dev site 2) User doesn't have a rally account and gets directed to rally to create an account 3) User creates account with email and password 4) User verifies their email and the UI indicates that they successfully created an account 5) User logs back into Rally 6) User is prompted to complete their profile with name and username 7) Users go back to Bonfire and connect their Rally account We're seeing that if you don't complete steps 5 and 6, then fetching the user info from https://api.rally.io/v1/oauth/userinfo will fail. Is it possible to make the process for a new Rally user more streamlined for 3rd party apps? We have some users who get pretty confused since they don't know that they need to sign in again and fill out their profile. Possible solutions * Allow account creation during auth - this is probably the most holistic solution and allows the user to stay in the context of the third party site * Remove steps 5 and 6 as a requirement for fetching user info - this would remove some steps but the user still needs to leave the third party site experience * Tell users in step 4 that they need to sign in in order to complete their account - this is probably the lowest hanging fruit though doesn't solve all of the pain points. Open to any other solutions as well!

Currently we can get paginated transactions for a given coin, but we can't get them for a given wallet. So if a user wanted to see a list of all their transactions, we'd have to ping every coin and build a list, which swiftly becomes unwieldy.

There are a growing number of use cases where it is desirable to automate the process of turning RLY to Creator Coin. Doing conversions manually becomes especially cumbersome in wallets which contain a high number of Creator Coins. Examples: Rewards management for game purposes, running predefined economy processes on DAO/App accounts, automatically convert $RLY rewards back into the Creator Coin which generated them in a precise manner. This ability is already possible via unauthorized means, can we now have it for purposes of good?

Right now you can only see transactions for a specific coin. It would be great to be able to get all transactions for an account that has oauthed with your app, similar to how this is possible in Ethereum.

Right now, the apis only return 100 entries. It would be great to have pagination so we can get all the NFT holders for a creator

There is no way to view my own personal pending rewards for this week except to go into each individual one of my coins on Rally's website and see them/add them up there one by one. It would be nice to have an API end point where I could fetch all of these counts at once. Adding it to the portfolio API could also work.

Upon logging into Rally Auth and then clicking on the Authorize button, the Authorize button should be disabled until Rally confirms. Currently, a user can press the Authorize button multiple buttons while Rally confirms. If the user presses the Authorize button again, they will get an error and need to attempt the process again.

Similar to the existing endpoint, but with a timestamp passed in as a querystring param. If historical user data does not exist, we can continue to use polling and storage, but it would be less data/API load to be able to query historical data for a user. To build graphs and snapshots.

Use case: currently there's no way to test transferring creator coins without buying a real creator coin Ideally there's a sandbox environment with test user and creator accounts that you can seed with coins. It would also be nice to allow any callback urls for oauth in development. This is ideal for development environments where the url may change based on the git hash.