如何使用Coingecko和Python构建加密价格警报系统

加密货币市场迅速发展，新硬币和新兴趋势不断变化。在本文中，我们将学习如何构建加密价格警报系统

This tutorial will guide you through building a crypto price alert system that provides regular email updates on the latest trending coins and categories on CoinGecko, on-chain categories on GeckoTerminal, and sudden surges in trading volume. These insights can be valuable for informing your investment strategy or keeping you up to date with the latest market trends.

本教程将指导您构建一个加密价格警报系统，该系统可定期提供有关Coingecko，壁虎的链链类别以及交易量突然激增的最新趋势硬币和类别的电子邮件更新。这些见解对于告知您的投资策略或使您了解最新市场趋势可能很有价值。

As usual, you’ll find a link to the GitHub repository at the end of the article. Let's dive in!

像往常一样，您会在文章末尾找到指向GitHub存储库的链接。让我们潜入！

Pre-requisites

先决条件

To obtain a CoinGecko API key, head over to the Developer’s Dashboard and click on +Add New Key in the top right corner. For detailed instructions on generating and setting up your key, refer to this guide.

要获取CoingeCko API键，请转到开发人员的仪表板，然后单击右上角的新键 +添加新键。有关生成和设置密钥的详细说明，请参阅本指南。

For this project, we’ll be using the Categories List and Search Queries endpoints in the CoinGecko API. The Categories List endpoint is exclusively available only on the CoinGecko API Analyst tier and higher. As a free alternative, you can comment out the call to this endpoint and rely solely on the Search Queries data.

对于此项目，我们将使用Coingecko API中的类别列表和搜索查询端点。类别列表端点仅在Coingecko API分析师等级和更高的Coingecko API分析师中可用。作为免费替代方案，您可以评论到此端点的调用，并仅依靠搜索查询数据。

Step 1. Initializing the project

步骤1。初始化项目

To start, we’ll initialize our project, install package requirements, and safely load our API credentials. First, we'll create an empty directory, which will serve as the root of our project.

首先，我们将初始化我们的项目，安装包装要求并安全加载我们的API凭据。首先，我们将创建一个空目录，该目录将作为我们项目的根源。

Installing Dependencies

安装依赖项

Let’s initialize a local Python environment. This will keep the global Python scope clean of any potential library versioning issues:

让我们初始化当地的Python环境。这将使全球Python范围清除任何潜在的库版本问题：

With the virtual environment now activated, copy the requirements below and paste them inside a new file called requirements.txt at the root of your project.

现在激活了虚拟环境，请在下面复制要求，然后将它们粘贴到一个名为unignts.txt的新文件中。

```

````````

click==8.1.3

单击== 8.1.3

dataclasses-json==0.6.1

dataclasses-json == 0.6.1

google-auth==2.16.0

Google-auth == 2.16.0

google-auth-oauthlib==0.13.0

Google-Auth-Oauthlib == 0.13.0

google-api-core==2.16.0

Google-api-core == 2.16.0

google-api-client==2.46.0

Google-api-client == 2.46.0

google-api-python-client==2.56.0

Google-api-python-client == 2.56.0

google-auth-httplib2==0.1.1

Google-auth-httplib2 == 0.1.1

google-oauth2==5.3.0

Google-Oauth2 == 5.3.0

google-oauth2-client==4.19.3

Google-oauth2-client == 4.19.3

google-cloud-storage==2.5.0

Google-Cloud-Storage == 2.5.0

google-cloud-bigquery==3.36.0

Google-cloud-bigquery == 3.36.0

google-cloud-bigquery-storage==3.36.0

Google-cloud-bigquery-Storage == 3.36.0

google-cloud-bigquery-datatransfer==3.36.0

Google-cloud-bigquery-datatransfer == 3.36.0

google-cloud-bigquery-connection==3.36.0

Google-cloud-bigquery-connection == 3.36.0

google-cloud-bigquery-logging==3.36.0

Google-cloud-bigquery-loging == 3.36.0

google-cloud-bigquery-admin==3.36.0

Google-cloud-bigquery-admin == 3.36.0

google-cloud-bigquery-analyticshub==3.36.0

Google-cloud-bigquery-analyticsHub == 3.36.0

google-cloud-bigquery-migration==3.36.0

Google-cloud-bigquery迁移== 3.36.0

google-cloud-bigquery-pandas==3.36.0

Google-cloud-bigquery-pandas == 3.36.0

google-cloud-bigquery-storage-transfer==3.36.0

Google-cloud-bigquery-storage-Transfer == 3.36.0

google-cloud-bigquery-datapolicies==3.36.0

Google-cloud-bigquery-datapolicies == 3.36.0

google-cloud-bigquery-datatransfer-service==3.36.0

Google-cloud-bigquery-datatransfer-Service == 3.36.0

google-cloud-bigquery-reservation==3.36.0

Google-cloud-bigquery-保留== 3.36.0

google-cloud-bigquery-rpb==3.36.0

Google-cloud-bigquery-rpb == 3.36.0

google-cloud-bigquery-updater==3.36.0

Google-cloud-bigquery-updater == 3.36.0

google-cloud-bigquery-audit==3.36.0

Google-cloud-bigquery-audit == 3.36.0

google-cloud-bigquery-dwh-audit==3.36.0

Google-cloud-bigquery-dwh-audit == 3.36.0

google-cloud-bigquery-connection-audit==3.36.0

Google-cloud-bigquery-connection-audit == 3.36.0

google-cloud-bigquery-analyticshub-audit==3.36.0

Google-cloud-bigquery-analyticsHub-audit == 3.36.0

google-cloud-bigquery-migration-audit==3.36.0

Google-cloud-bigquery-migration-audit == 3.36.0

google-cloud-bigquery-pandas-audit==3.36.0

Google-cloud-bigquery-pandas-audit == 3.36.0

google-cloud-bigquery-storage-transfer-audit==3.36.0

Google-cloud-bigquery-storage-transfer-audit == 3.36.0

google-cloud-bigquery-datapolicies-audit==3.36.0

Google-cloud-bigquery-datapolicies-audit == 3.36.0

google-cloud-bigquery-datatransfer-service-audit==3.36.0

Google-cloud-bigquery-datatransfer-service-audit == 3.36.0

google-cloud-bigquery-reservation-audit==3.36.0

Google-cloud-bigquery-bigquery-ofert-audit == 3.36.0

google-cloud-bigquery-rpb-audit==3.36.0

google-cloud-bigquery-rpb-audit == 3.36.0

google-cloud-bigquery-updater-audit==3.36.0

Google-cloud-bigquery-updater-audit == 3.36.0

google-cloud-bigquery-audit-admin==3.36.0

Google-cloud-bigquery-audit-admin == 3.36.0

google-cloud-bigquery-dwh-audit-admin==3.36.0

Google-cloud-bigquery-dwh-audit-admin == 3.36.0

google-cloud-bigquery-connection-audit-admin==3.36.0

Google-cloud-bigquery-connection-audit-admin == 3.36.0

google-cloud-bigquery-analyticshub-audit-admin==3.36.0

Google-cloud-bigquery-analyticsHub-audit-admin == 3.36.0

google-cloud-bigquery-migration-audit-admin

Google-cloud-bigquery-migration-audit-admin