api3dao · dcroote · Mar 7, 2023 · Mar 5, 2023
diff --git a/.changeset/silver-parents-design.md b/.changeset/silver-parents-design.md
@@ -0,0 +1,5 @@
+---
+'@api3/airnode-examples': minor
+---
+
+Combine http gateway integrations into a single integration
diff --git a/packages/airnode-examples/README.md b/packages/airnode-examples/README.md
@@ -42,13 +42,11 @@ reserved parameters. The following list orders integrations alphabetically:
   demonstration of the [post-processing](https://docs.api3.org/ois/latest/processing.html) feature.
 - [coingecko-pre-processing](https://github.com/api3dao/airnode/tree/master/packages/airnode-examples/integrations/coingecko-pre-processing) -
   demonstration of the [pre-processing](https://docs.api3.org/ois/latest/processing.html) feature.
-- [coingecko-signed-data](https://github.com/api3dao/airnode/tree/master/packages/airnode-examples/integrations/coingecko-signed-data) -
-  demonstration of signed data retrieval for beacon updates.
+- [coingecko-http-gateways](https://github.com/api3dao/airnode/tree/master/packages/airnode-examples/integrations/coingecko-http-gateways) -
+  demonstration of the
+  [HTTP gateway and HTTP signed data gateway](https://docs.api3.org/airnode/latest/grp-providers/guides/build-an-airnode/http-gateways.html).
 - [coingecko-template](https://github.com/api3dao/airnode/tree/master/packages/airnode-examples/integrations/coingecko-template) -
   demonstration of [template](https://docs.api3.org/airnode/latest/grp-developers/using-templates.html) requests.
-- [coingecko-testable](https://github.com/api3dao/airnode/tree/master/packages/airnode-examples/integrations/coingecko-testable) -
-  demonstration of how to test the endpoint using the
-  [HTTP gateway](https://docs.api3.org/airnode/latest/grp-providers/guides/build-an-airnode/http-gateways.html).
 - [failing-example](https://github.com/api3dao/airnode/tree/master/packages/airnode-examples/integrations/failing-example) -
   demonstration of Airnode error handling through an invalid request.
 - [relay-security-schemes](https://github.com/api3dao/airnode/tree/master/packages/airnode-examples/integrations/relay-security-schemes) -

diff --git a/...racts/coingecko-signed-data/Requester.sol → ...cts/coingecko-http-gateways/Requester.sol b/...racts/coingecko-signed-data/Requester.sol → ...cts/coingecko-http-gateways/Requester.sol
diff --git a/packages/airnode-examples/contracts/coingecko-testable/Requester.sol b/packages/airnode-examples/contracts/coingecko-testable/Requester.sol
diff --git a/...egrations/coingecko-signed-data/README.md → ...rations/coingecko-http-gateways/README.md b/...egrations/coingecko-signed-data/README.md → ...rations/coingecko-http-gateways/README.md
@@ -2,15 +2,51 @@
 
 This example contains the same API integration as `../coingecko`.
 
-The only difference is that this integration allows the endpoint to return signed data that can be then submitted on
-chain.
+The only difference is that this integration allows the endpoint to return either unsigned or signed data via the HTTP
+gateway or HTTP signed data gateway, respectively.
 
-See the documentation for the
-[signed data gateway](https://docs.api3.org/airnode/latest/grp-providers/guides/build-an-airnode/http-gateways.html#http-signed-data-gateway).
+For more details, see the documentation for the
+[HTTP gateways](https://docs.api3.org/airnode/latest/grp-providers/guides/build-an-airnode/http-gateways.html).
 
-## Encode parameters
+## HTTP gateway
 
-The coingecko requests expects a parameter `coinId` which needs to be passed to the gateway encoded using
+### Trigger a request
+
+You can trigger the API call with a POST request. For example, you can use `curl` in the terminal:
+
+```sh
+curl -X POST -H 'Content-Type: application/json' -d '{"parameters": {"coinId": "bitcoin"}}' '<HTTP_GATEWAY_URL>/<ENDPOINT_ID>'
+```
+
+#### When deployed on cloud
+
+Before making the request, you need to replace the example values:
+
+- `<HTTP_GATEWAY_URL>` - You can find this value as part of the terminal output of the `yarn deploy-airnode` command
+- `<ENDPOINT_ID>` - You can find this value in `config.json` under `triggers.rrp[0].endpointId` path
+
+The correct command may look like this:
+
+```sh
+curl -X POST -H 'Content-Type: application/json' -d '{"parameters": {"coinId": "bitcoin"}}' 'https://x9sidy9ln0.execute-api.us-east-1.amazonaws.com/v1/d6ed7e8b-40fa-1392-3e4a-37e225ccda20/0xfb87102cdabadf905321521ba0b3cbf74ad09c5d400ac2eccdbef8d6143e78c4'
+```
+
+#### When running Airnode locally
+
+When Airnode is run locally, the HTTP gateway endpoint is always
+`http://localhost:<PORT>/http-data/01234567-abcd-abcd-abcd-012345678abc/<ENDPOINT_ID>`.
+
+For example:
+
+```sh
+curl -X POST -H 'Content-Type: application/json' -d '{"parameters": {"coinId": "bitcoin"}}' 'http://localhost:3000/http-data/01234567-abcd-abcd-abcd-012345678abc/0xfb87102cdabadf905321521ba0b3cbf74ad09c5d400ac2eccdbef8d6143e78c4'
+```
+
+## HTTP signed data gateway
+
+### Encode parameters
+
+The coingecko endpoint expects a parameter `coinId` which needs to be passed to the signed data gateway encoded using
 [Airnode ABI](https://docs.api3.org/airnode/latest/reference/specifications/airnode-abi-specifications.html).
 
 We have encoded two basic parameter types:
@@ -22,15 +58,15 @@ We have encoded two basic parameter types:
 
 Feel free to encode a different parameter type to make a different request.
 
-## Trigger a request
+### Trigger a request
 
 You can trigger the API call with a POST request. For example, you can use `curl` in the terminal:
 
 ```sh
 curl -X POST -H 'Content-Type: application/json' -d '{"encodedParameters": "0x3173000000000000000000000000000000000000000000000000000000000000636f696e49640000000000000000000000000000000000000000000000000000626974636f696e00000000000000000000000000000000000000000000000000"}' '<HTTP_SIGNED_DATA_GATEWAY_URL>/<ENDPOINT_ID>'
 ```
 
-### When deployed on cloud
+#### When deployed on cloud
 
 Before making the request, you need to replace the following placeholders:
 
@@ -46,7 +82,7 @@ The correct command may look like this:
 curl -X POST -H 'Content-Type: application/json' -d '{"encodedParameters": "0x3173000000000000000000000000000000000000000000000000000000000000636f696e49640000000000000000000000000000000000000000000000000000626974636f696e00000000000000000000000000000000000000000000000000"}' 'https://am6ncplkx4.execute-api.us-east-1.amazonaws.com/v1/d6ed7e8b-40fa-1392-3e4a-37e225ccda20/0xfb87102cdabadf905321521ba0b3cbf74ad09c5d400ac2eccdbef8d6143e78c4'
 ```
 
-### When running Airnode locally
+#### When running Airnode locally
 
 When Airnode is run locally, the HTTP signed data gateway endpoint is always
 `http://localhost:<PORT>/http-signed-data/01234567-abcd-abcd-abcd-012345678abc/<ENDPOINT_ID>`. For now, `PORT` number is
@@ -58,7 +94,7 @@ For example:
 curl -X POST -H 'Content-Type: application/json' -d '{"encodedParameters": "0x3173000000000000000000000000000000000000000000000000000000000000636f696e49640000000000000000000000000000000000000000000000000000626974636f696e00000000000000000000000000000000000000000000000000"}' 'http://localhost:3000/http-signed-data/01234567-abcd-abcd-abcd-012345678abc/0xfb87102cdabadf905321521ba0b3cbf74ad09c5d400ac2eccdbef8d6143e78c4'
 ```
 
-## Output
+### Output
 
 The example output might look like this:
 

diff --git a/...coingecko-signed-data/config.example.json → ...ingecko-http-gateways/config.example.json b/...coingecko-signed-data/config.example.json → ...ingecko-http-gateways/config.example.json
@@ -53,7 +53,9 @@
       "enabled": false
     },
     "httpGateway": {
-      "enabled": false
+      "enabled": true,
+      "maxConcurrency": 20,
+      "corsOrigins": []
     },
     "httpSignedDataGateway": {
       "enabled": true,
@@ -74,7 +76,13 @@
         "cacheResponses": false
       }
     ],
-    "http": [],
+    "http": [
+      {
+        "endpointId": "0xfb87102cdabadf905321521ba0b3cbf74ad09c5d400ac2eccdbef8d6143e78c4",
+        "oisTitle": "CoinGecko basic request",
+        "endpointName": "coinMarketData"
+      }
+    ],
     "httpSignedData": [
       {
         "endpointId": "0xfb87102cdabadf905321521ba0b3cbf74ad09c5d400ac2eccdbef8d6143e78c4",

diff --git a/...ns/coingecko-signed-data/create-config.ts → .../coingecko-http-gateways/create-config.ts b/...ns/coingecko-signed-data/create-config.ts → .../coingecko-http-gateways/create-config.ts
@@ -60,7 +60,9 @@ const createConfig = async (generateExampleFile: boolean): Promise<Config> => ({
       enabled: false,
     },
     httpGateway: {
-      enabled: false,
+      enabled: true,
+      maxConcurrency: 20,
+      corsOrigins: [],
     },
     httpSignedDataGateway: {
       enabled: true,
@@ -81,7 +83,13 @@ const createConfig = async (generateExampleFile: boolean): Promise<Config> => ({
         cacheResponses: false,
       },
     ],
-    http: [],
+    http: [
+      {
+        endpointId: '0xfb87102cdabadf905321521ba0b3cbf74ad09c5d400ac2eccdbef8d6143e78c4',
+        oisTitle: 'CoinGecko basic request',
+        endpointName: 'coinMarketData',
+      },
+    ],
     httpSignedData: [
       {
         endpointId: '0xfb87102cdabadf905321521ba0b3cbf74ad09c5d400ac2eccdbef8d6143e78c4',

diff --git a/...s/coingecko-signed-data/create-secrets.ts → ...coingecko-http-gateways/create-secrets.ts b/...s/coingecko-signed-data/create-secrets.ts → ...coingecko-http-gateways/create-secrets.ts
diff --git a/...ns/coingecko-signed-data/request-utils.ts → .../coingecko-http-gateways/request-utils.ts b/...ns/coingecko-signed-data/request-utils.ts → .../coingecko-http-gateways/request-utils.ts
diff --git a/...coingecko-signed-data/secrets.example.env → ...ingecko-http-gateways/secrets.example.env b/...coingecko-signed-data/secrets.example.env → ...ingecko-http-gateways/secrets.example.env
diff --git a/packages/airnode-examples/integrations/coingecko-testable/README.md b/packages/airnode-examples/integrations/coingecko-testable/README.md