The existing auction info endpoint returns all of the auction info (including rewards) for a given era. As this contains all validators and all of their respective delegators, the returned data can be arbitrarily large. For consumers (such as the requesting party, BitGo) who are only concerned with a specific validator or delegator, this is inconvenient and inefficient. The new endpoint should support a request for reward info for a specific era, and specific PublicKey. The backing logic would filter the full set of rewards data for the imputed data, including records matching the imputed PublicKey and excluding all other records.
The existing auction info endpoint returns all of the auction info (including rewards) for a given era. As this contains all validators and all of their respective delegators, the returned data can be arbitrarily large. For consumers (such as the requesting party, BitGo) who are only concerned with a specific validator or delegator, this is inconvenient and inefficient. The new endpoint should support a request for reward info for a specific era, and specific PublicKey. The backing logic would filter the full set of rewards data for the imputed data, including records matching the imputed PublicKey and excluding all other records.