GITBOOK-293: Add API Key documentation

Author: simonerom

.gitbook/assets/image (1) (1) (1) (1) (1) (1).png

@@ -79,7 +79,7 @@ Any community member interested in operating a W3bstream node could provision a
 {% hint style="success" %}
 ### What's next?
 
-Checkout the [**Get Started**](client-device-sdks/introduction.md) section to learn how to run a W3bstream node.
+Checkout the [**Get Started**](sending-data-to-w3bstream/introduction-1/) section to learn how to run a W3bstream node.
 
 Learn about the fundamentals of [**programming** ](get-started/basic-concepts/)a W3bstream node.
 {% endhint %}

.gitbook/assets/image (1) (1) (1) (1) (1).png

@@ -15,7 +15,6 @@
   * [Event Triggers](get-started/basic-concepts/events.md)
   * [Event Routing Strategies](get-started/basic-concepts/event-strategies.md)
   * [Device Accounts](get-started/basic-concepts/publishers.md)
-  * [Message Protocol](get-started/basic-concepts/message-api.md)
 * [Access W3bstream](get-started/access-w3bstream.md)
 * [Deploy "Hello World"](get-started/deploying-an-applet.md)
 * [W3bstream Studio](get-started/w3bstream-studio/README.md)
@@ -27,6 +26,7 @@
     * [Sending Test Data](get-started/w3bstream-studio/triggering-events/testing-events.md)
   * [Routing Events](get-started/w3bstream-studio/creating-strategies.md)
   * [Create Database Tables](get-started/w3bstream-studio/create-database-tables.md)
+  * [Create API Keys](get-started/w3bstream-studio/create-api-keys.md)
 
 ## 👨💻 Applets Development
 
@@ -48,6 +48,26 @@
   * [Token Proofs](applets-development/advanced-concepts/token-proofs.md)
   * [Trusted IoT Data](applets-development/advanced-concepts/trusted-iot-data.md)
 
+## ⚙ Sending Data to W3bstream
+
+* [Introduction](sending-data-to-w3bstream/introduction.md)
+* [W3bstream Data API](sending-data-to-w3bstream/w3bstream-data-api/README.md)
+  * [HTTP API](sending-data-to-w3bstream/w3bstream-data-api/http-api.md)
+  * [MQTT Broker](sending-data-to-w3bstream/w3bstream-data-api/mqtt-broker.md)
+* [PC Client SDKs](sending-data-to-w3bstream/pc-client-sdks/README.md)
+  * [Node JS](sending-data-to-w3bstream/pc-client-sdks/node-js.md)
+  * [Python](sending-data-to-w3bstream/pc-client-sdks/python.md)
+  * [Go lang](sending-data-to-w3bstream/pc-client-sdks/go-lang.md)
+* [IoT Client SDKs](sending-data-to-w3bstream/introduction-1/README.md)
+  * [Technical goals](sending-data-to-w3bstream/introduction-1/technical-goals.md)
+  * [Business Goals](sending-data-to-w3bstream/introduction-1/business-goals.md)
+  * [Technical Framework](sending-data-to-w3bstream/introduction-1/technical-framework.md)
+  * [Linux Embedded](sending-data-to-w3bstream/introduction-1/embedded-sdks.md)
+  * [ESP32](sending-data-to-w3bstream/introduction-1/esp32.md)
+  * [Arduino](sending-data-to-w3bstream/introduction-1/arduino.md)
+  * [Pebble Tracker](sending-data-to-w3bstream/introduction-1/pebble-tracker.md)
+* [Mobile Client SDKs](sending-data-to-w3bstream/mobile-client-sdks.md)
+
 ## 📊 Trusted Metrics Service
 
 * [About Trusted Metrics](trusted-metrics-service/about-trusted-metrics.md)
@@ -61,22 +81,6 @@
   * [Integrating the Device Map](trusted-metrics-service/depinscan/integrating-the-device-map.md)
   * [Getting Verified](trusted-metrics-service/depinscan/getting-verified.md)
 
-## ⚙ Client SDKs
-
-* [Mobile SDKs](client-device-sdks/supported-platforms/mobile-devices.md)
-* [PC Client SDKs](client-sdks/pc-client-sdks/README.md)
-  * [Node JS](client-sdks/pc-client-sdks/node-js.md)
-  * [Python](client-sdks/pc-client-sdks/python.md)
-  * [Go lang](client-sdks/pc-client-sdks/go-lang.md)
-* [IoT Client SDKs](client-device-sdks/introduction.md)
-  * [Technical goals](client-device-sdks/embedded-sdks/technical-goals.md)
-  * [Business Goals](client-device-sdks/embedded-sdks/business-goals.md)
-  * [Technical Framework](client-device-sdks/embedded-sdks/technical-framework.md)
-  * [Linux Embedded](client-device-sdks/supported-platforms/embedded-sdks.md)
-  * [ESP32](client-device-sdks/supported-platforms/esp32.md)
-  * [Arduino](client-device-sdks/supported-platforms/arduino.md)
-  * [Pebble Tracker](client-device-sdks/supported-platforms/pebble-tracker.md)
-
 ## 📚 Additional Resources
 
 * [Landing Page](https://w3bstream.com/)

.gitbook/assets/image (1) (1) (1) (1).png

@@ -1,13 +1,19 @@
 # Configuring Devices
 
-Before your project can receive any data messages from a device, you will need to add a new device account in the _Devices_ tab of the Project Editor. See the quick video below to learn how to create a new Device Account:
+Before your project can receive any data messages from a device, you will need to add a new device account in the _Devices_ tab of the Project Editor. 
+
+## Creating Devices using W3bstream Studio
+
+See the quick video below to learn how to create a new Device Account:
 
 {% content-ref url="configuring-devices.md" %}
 [configuring-devices.md](configuring-devices.md)
 {% endcontent-ref %}
 
 Any client device intending to send data to your W3bstream project must include a valid authentication token within the message. 
 
-{% hint style="info" %}
-Depending on your use case, you can use one token for each device or for groups of devices.
+## Creating devices using the Publisher API
+
+{% hint style="warning" %}
+This section a work in progress and will be available soon.
 {% endhint %}

.gitbook/assets/image (1) (1) (1).png

@@ -6,14 +6,14 @@ Here's an overview of how it works.
 
 ## Using W3bstream Client SDKs
 
-In the previous section [message-api.md](../get-started/basic-concepts/message-api.md "mention") we discussed the messaging format specified by the W3bstream API. Each W3bstream message contains a payload string field, which is intended to hold the actual data sent by a smart device to our project and to be processed by a handler.
+In the previous section [http-api.md](../sending-data-to-w3bstream/w3bstream-data-api/http-api.md "mention") we discussed the messaging format specified by the W3bstream API. Each W3bstream message contains a payload string field, which is intended to hold the actual data sent by a smart device to our project and to be processed by a handler.
 
 To simplify the process of sending data to your W3bstream project, we recommend utilizing a W3bstream Client SDK tailored for your specific device. By doing so, you won't need to concern yourself with the intricacies of the W3bstream messaging protocol. Instead, you can focus on providing the relevant data for your application, including the target project name, event type, and device authentication token.
 
 If you're unsure which W3bstream Client SDK is suitable for your device, please refer to our documentation for additional guidance and information.
 
-{% content-ref url="../client-device-sdks/introduction.md" %}
-[introduction.md](../client-device-sdks/introduction.md)
+{% content-ref url="../sending-data-to-w3bstream/introduction-1/" %}
+[introduction-1](../sending-data-to-w3bstream/introduction-1/)
 {% endcontent-ref %}
 
 ## Example message

.gitbook/assets/image (1) (1).png

@@ -0,0 +1,2 @@
+# Create API Keys
+

.gitbook/assets/image (1).png

@@ -56,7 +56,7 @@ The development of W3bstream will span until Q2 2024. During this time, the “_
 {% hint style="success" %}
 ### What's next?
 
-Checkout the [**Get Started**](../client-device-sdks/introduction.md) section to learn how to run a W3bstream node.
+Checkout the [**Get Started**](../sending-data-to-w3bstream/introduction-1/) section to learn how to run a W3bstream node.
 
 Learn about the fundamentals of [**programming** ](../get-started/basic-concepts/)a W3bstream node.
 {% endhint %}

.gitbook/assets/image (45).png

@@ -0,0 +1,7 @@
+# IoT Client SDKs
+
+W3bstream aims to accommodate a wide range of IoT devices with different hardware components and capabilities, from legacy Web2-based products, over community-driven development boards, to emerging Web3-oriented devices and mobile phones.
+
+By using the W3bstream Client SDK, you can ensure that your data is sent securely and reliably to your W3bstream project. The SDK takes care of authentication, encryption, and other important details, so you can focus on building your project.
+
+<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Mobile</strong> <strong>Client SDK</strong></td><td>Send data to W3bstream from mobile devices.</td><td></td><td><a href="../../.gitbook/assets/Screen Shot 2023-05-23 at 8.56.44 PM.png">Screen Shot 2023-05-23 at 8.56.44 PM.png</a></td><td><a href="../mobile-client-sdks.md">mobile-client-sdks.md</a></td></tr><tr><td><strong>Pebble Client SDK</strong></td><td>Send verifiable data to W3bstream from your Pebble Tracker.</td><td></td><td><a href="../../.gitbook/assets/Screen Shot 2023-05-23 at 11.11.45 PM.png">Screen Shot 2023-05-23 at 11.11.45 PM.png</a></td><td><a href="broken-reference">Broken link</a></td></tr><tr><td><strong>Linux Embedded Client SDKs</strong></td><td>Send data to W3bstream from popular Linux-based boards.</td><td></td><td><a href="../../.gitbook/assets/embedded-header.jpg">embedded-header.jpg</a></td><td><a href="embedded-sdks.md">embedded-sdks.md</a></td></tr><tr><td><strong>ESP32 Client</strong> <strong>SDK</strong></td><td>Send data to W3bstream from an ESP32 Board.</td><td></td><td><a href="../../.gitbook/assets/Screen Shot 2023-05-23 at 10.54.45 PM.png">Screen Shot 2023-05-23 at 10.54.45 PM.png</a></td><td><a href="esp32.md">esp32.md</a></td></tr><tr><td><strong>Arduino Client</strong> <strong>SDK</strong></td><td>Send data to W3bstream from an Arduino Board.</td><td>🔜 </td><td><a href="../../.gitbook/assets/Screen Shot 2023-05-23 at 11.09.04 PM.png">Screen Shot 2023-05-23 at 11.09.04 PM.png</a></td><td><a href="arduino.md">arduino.md</a></td></tr></tbody></table>

.gitbook/assets/image.png

@@ -0,0 +1,7 @@
+# Arduino
+
+The W3bstream IoT SDK is available for Arduino-based boards.
+
+For installation, supported devices and usage guides, please check out the GitHub repository below:
+
+{% embed url="https://github.com/machinefi/w3bstream-client-arduino-ce" %}

README.md

@@ -1,6 +1,12 @@
 # Linux Embedded
 
-Set up the build environment
+{% hint style="info" %}
+**Notice**: The Linux Embedded Client SDK does not include a W3bstream Client object. To create API calls, you will need to utilize the HTTP/MQTT clients directly. Detailed examples can be located within the SDK repository for your reference.
+
+[Go to the examples folder...](https://github.com/machinefi/web3-iot-sdk/tree/main/examples)
+{% endhint %}
+
+## Set up the build environment
 
 Iotex SDK officially supports a limited set of build environments and setups. In this context, official support means that the environments listed below are actively used by team members and active developers, hence users should be able to recreate the same configurations by following the instructions described below.\
 In case of problems, the Iotex SDK team provides support only for these environments, but building in other environments can still be possible.
@@ -29,15 +35,15 @@ Install the following dependencies:
 * MinGW32: [https://sourceforge.net/projects/mingw-w64/files/](https://sourceforge.net/projects/mingw-w64/files/)
 * Python3 and pip (included by default): [https://www.python.org/downloads/](https://www.python.org/downloads/)
 
-### Get the source code
+## Get the source code
 
 Run the following command to clone the repository:
 
 ```bash
 git clone https://github.com/machinefi/web3-iot-sdk.git
 ```
 
-### Build
+## Build
 
 The build process is managed by CMake. The build can be customized by passing CMake options.\
 For a full list of CMake options see the main [CMakeLists.tx](https://github.com/machinefi/w3bstream-iot-sdk/blob/main/CMakeLists.txt). Below is a description of the most common ones:
@@ -92,6 +98,6 @@ TOTAL SKIPPED   : 2
 ******************************************
 ```
 
-### Examples
+## Examples
 
 Examples to demonstrate the usage of the SDK can be found in the [examples](https://github.com/machinefi/web3-iot-sdk/tree/main/examples) of the SDK. Each example contains a README file with usage instructions.