An inbound source is a mechanism for receiving information from IoT devices—such as sensor data—from a separate, non-obniz system, and handling it within obniz Now.
In addition to data sent from a single sensor, inbound sources can also receive "information from multiple LoRa sensors sent by a LoRa gateway."
Using this feature requires a dedicated plan contract.
Adding a Source
You can add one from the inbound source addition screen.
For an inbound source, you can register it by adding the type and format of the data sender as well as authentication information.
Once created, an endpoint for sending data is generated.
When data is actually received, the information of the receiving device is displayed. In the case of a gateway, the information of the multiple sensors that were sent is displayed.
When you actually register it as a device (machine) on obniz Now to store data or perform automation, you carry out the registration from the screen.
Configuration on the IoT Sensor or Gateway Side
Set the sending URL issued when the inbound source is created on the IoT device side.
An API Key is required for sending.
From API Keys, issue a key with write permission to the inbound source as shown below, and set it as the access token.
How to set the token in an HTTP request (higher priority from the top)
| Type | Key | Example |
| Request header (recommended) | authorization or Authorization | {"authorization": "Bearer xxxx"} |
| Request query | token | https://now.obniz.com/xxxx?token=xxxx |
| Body | token | {"token": "xxxxx"} |
Please configure it using the method your IoT device supports.
For more about API Keys, please refer to the API Key page.