You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
External services are slowly closing down their APIs with API Keys. Even though that makes sense from their perspective, it presents a very difficult problem for an application like Rotki because it will require each user to maintain their own set of API keys for external services.
For the ethereum blockchain if the user is not connecting to his own node or to Infura we are heavily relying on Etherscan. With etherscan enforcing API key usage from 15/02/2020 the ability for Rotki users to manage their own API keys becomes paramount.
Task
The available external API services for now will be ["etherscan", "cryptocompare"]
Frontend
In the settings page of the user create a UI element that will allow addition of API keys for all available external API services.
Backend
Either add a new table external_service_credentials
CREATE TABLE IF NOT EXISTS external_service_credentials (
name VARCHAR[24] NOT NULL PRIMARY KEY,
api_key TEXT
);
or just add them in the existing DB settings.
For each service that there is a possibility for an API key:
Query the DB to see if it exists
If it does, use it in the query.
If it does not and the API allows queries without a key, proceed.
If it does not and the API requires an API key let the user know.
This will require new errors in some of the API endpoints.
The text was updated successfully, but these errors were encountered:
Problem Definition
External services are slowly closing down their APIs with API Keys. Even though that makes sense from their perspective, it presents a very difficult problem for an application like Rotki because it will require each user to maintain their own set of API keys for external services.
For the ethereum blockchain if the user is not connecting to his own node or to Infura we are heavily relying on Etherscan. With etherscan enforcing API key usage from 15/02/2020 the ability for Rotki users to manage their own API keys becomes paramount.
Task
The available external API services for now will be
["etherscan", "cryptocompare"]
Frontend
In the settings page of the user create a UI element that will allow addition of API keys for all available external API services.
Backend
Either add a new table
external_service_credentials
or just add them in the existing DB settings.
For each service that there is a possibility for an API key:
This will require new errors in some of the API endpoints.
The text was updated successfully, but these errors were encountered: