Ubidots

Ubidots is an IoT platform for device management, data collection, and real-time monitoring. Connect the Ubidots REST API to Nexla to ingest devices, variables, events, and the latest sensor values, or to push new devices, variables, events, and data points into your Ubidots account.

Power end-to-end data operations for your Ubidots API with Nexla. Our bi-directional Ubidots connector is purpose-built for Ubidots, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Ubidots or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Ubidots workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Ubidots credential, you need a Ubidots account and an API Token. Ubidots authenticates every REST API request with a token sent in the X-Auth-Token header.

To obtain your Ubidots token, follow these steps:

1. Sign in to your Ubidots account.

2. Click your profile avatar in the top-right corner and select API Credentials.

3. Copy the Default Token shown on the API Credentials page, or generate a new token using your account's API Key. This token is the value Nexla sends in the X-Auth-Token header.

4. Note your account's API base URL. Industrial accounts use https://industrial.api.ubidots.com (the default), while other plans may use a different host. Use the base URL that matches your account.

Ubidots distinguishes between an API Key (your immutable master key, used only to generate tokens) and a Token (the revocable key used in API requests). Use the token, not the API Key, for the Nexla credential. For more detail, see the Ubidots API authentication documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key Value	Yes	Yes	An encoded string value used as a secret token to authenticate API requests
Base URL	Yes	No	The base URL for the Ubidots API.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Ubidots token in the API Key Value field. This is the token you obtained in Prerequisites, and Nexla sends it in the X-Auth-Token header for every API request.

4. Enter your account's API host in the Base URL field. The default is https://industrial.api.ubidots.com; use the base URL that matches your Ubidots plan.

   Your token grants access to the resources permitted by its role. If a token is compromised, revoke it and generate a new one from the Ubidots API Credentials page. For details on token permissions, see the Ubidots API authentication documentation.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Ubidots connector tile, then select the credential that will be used to connect to Ubidots, and click Next; or, create a new Ubidots credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Ubidots endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] List Devices

Returns a list of all devices in the Ubidots account.

• This endpoint retrieves every device accessible to your token. Results are paginated automatically; Nexla follows the API's next-page links to fetch all records.

For detailed information about the device object and its fields, see the Ubidots API documentation.

[Rest API] List Events

Returns a list of all events in the Ubidots account.

• This endpoint retrieves every event accessible to your token. Results are paginated automatically; Nexla follows the API's next-page links to fetch all records.

For detailed information about the event object and its fields, see the Ubidots API documentation.

[Rest API] List Dashboards

Returns a list of all dashboards in the Ubidots account.

• This endpoint retrieves every dashboard accessible to your token. Results are paginated automatically; Nexla follows the API's next-page links to fetch all records.

For detailed information about the dashboard object and its fields, see the Ubidots API documentation.

[Rest API] List Variables

Returns a list of all variables in the Ubidots account.

• This endpoint retrieves every variable accessible to your token. Results are paginated automatically; Nexla follows the API's next-page links to fetch all records.

For detailed information about the variable object and its fields, see the Ubidots API documentation.

[Rest API] List Device Groups

Returns a list of all device groups in the Ubidots account.

• This endpoint retrieves every device group accessible to your token. Results are paginated automatically; Nexla follows the API's next-page links to fetch all records.

For detailed information about the device group object and its fields, see the Ubidots API documentation.

[Rest API] List Device Types

Returns a list of all device types in the Ubidots account.

• This endpoint retrieves every device type accessible to your token. Results are paginated automatically; Nexla follows the API's next-page links to fetch all records.

For detailed information about the device type object and its fields, see the Ubidots API documentation.

[Rest API] List Organizations

Returns a paginated list of all organizations in the Ubidots account.

• This endpoint retrieves every organization accessible to your token. Results are paginated automatically; Nexla follows the API's next-page links to fetch all records.

For detailed information about the organization object and its fields, see the Ubidots API documentation.

[Rest API] List Users

Returns a paginated list of all users in the Ubidots account.

• This endpoint retrieves every user accessible to your token. Results are paginated automatically; Nexla follows the API's next-page links to fetch all records.

For detailed information about the user object and its fields, see the Ubidots API documentation.

[Rest API] Get Device Last Values

Returns the last reported sensor values for all variables of a specified device.

• Provide the Device Key — the ID or label of the device. When using a label, prefix it with a tilde (for example, use a leading ~ before the label).

For detailed information about last values and the response structure, see the Ubidots API documentation.

[Rest API] Get Variable

Retrieves details of a specific variable by its unique identifier.

• Provide the Variable ID — the unique identifier of the variable to retrieve.

For detailed information about the variable object and its fields, see the Ubidots API documentation.

[Rest API] Get User

Retrieves details of a specific user by their ID or username.

• Provide the User Key — the ID or username of the user. When using a username, prefix it with a tilde (for example, use a leading ~ before the username).

For detailed information about the user object and its fields, see the Ubidots API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Ubidots data sources can also be manually configured to ingest data from any valid Ubidots REST API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Ubidots data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Ubidots destination, and select the Send to Destination option from the menu. Select the Ubidots connector from the list of available destination connectors, then select the credential that will be used to connect to Ubidots, and click Next; or, create a new Ubidots credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Ubidots endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Create Device

Creates a new IoT device in the Ubidots account.

• Each record from your Nexset is sent as a JSON request body to create a new device. The record fields must match the format expected by the Ubidots device API.

For detailed information about device creation and request body fields, see the Ubidots API documentation.

[Rest API] Send Data to Device

Sends sensor data values to a device in Ubidots.

• Provide the Device Label — the API label of the device that will receive the data. Each record from your Nexset is sent as a JSON request body containing the variable values to post.

For detailed information about sending values to a device, see the Ubidots API documentation.

[Rest API] Update Device

Updates properties of an existing Ubidots device.

• Provide the Device ID — the unique identifier of the device to update. Each record from your Nexset is sent as a JSON request body containing the fields to change.

For detailed information about updating devices and request body fields, see the Ubidots API documentation.

[Rest API] Delete Device

Deletes a device from the Ubidots account.

• Provide the Device ID — the unique identifier of the device to delete. This operation is permanent, so verify the identifier before activating the destination.

For detailed information about deleting devices, see the Ubidots API documentation.

[Rest API] Create Variable

Creates a new variable associated with a device in the Ubidots account.

• Each record from your Nexset is sent as a JSON request body to create a new variable. The record fields must match the format expected by the Ubidots variable API.

For detailed information about variable creation and request body fields, see the Ubidots API documentation.

[Rest API] Create Event

Creates a new event with triggers and actions in the Ubidots account.

• Each record from your Nexset is sent as a JSON request body to create a new event. The record fields must match the format expected by the Ubidots event API.

For detailed information about event creation and request body fields, see the Ubidots API documentation.

[Rest API] Update Event

Partially updates one or more fields of an existing Ubidots event.

• Provide the Event Key — the ID or label of the event to update. When using a label, prefix it with a tilde (for example, use a leading ~ before the label). Each record from your Nexset is sent as a JSON request body containing the fields to change.

For detailed information about updating event fields, see the Ubidots API documentation.

[Rest API] Create Device Group

Creates a new device group in the Ubidots account.

• Each record from your Nexset is sent as a JSON request body to create a new device group. The record fields must match the format expected by the Ubidots device group API.

For detailed information about device group creation and request body fields, see the Ubidots API documentation.

[Rest API] Create Organization

Creates a new organization in the Ubidots account.

• Each record from your Nexset is sent as a JSON request body to create a new organization. The record fields must match the format expected by the Ubidots organization API.

For detailed information about organization creation and request body fields, see the Ubidots API documentation.

Manual configuration

Ubidots destinations can also be manually configured to send data to any valid Ubidots REST API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Ubidots APIs expect JSON format for write operations. For update operations, include the ID or label of the object to be updated in the endpoint URL.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Ubidots endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Ubidots endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.