OPUSWatch is a wearable-based labor registration and task-tracking system for the horticulture industry, letting greenhouse and nursery workers log tasks, crops, and time directly from a smartwatch. This connector uses the OPUSWatch REST API to ingest workers, tasks, sessions, registrations, and related reference data into Nexla.
Power end-to-end data operations for your OPUSWatch API with Nexla. Our bi-directional OPUSWatch connector is purpose-built for OPUSWatch, 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 OPUSWatch or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your OPUSWatch 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
Before creating an OPUSWatch credential, you need an API key for your OPUSWatch account. The OPUSWatch API is served from https://api.opuswatch.nl/ext, and requests are authenticated with an API key sent as a bearer token in the Authorization header (Authorization: Bearer <api_key>).
To obtain your API key:
Sign in to your OPUSWatch account with an administrator user.
Request or generate an API key for external API access. API key provisioning is managed by OPUSWatch; if you do not see an option to create one, contact OPUSWatch support or your account administrator to have a key issued for your organization.
Copy the API key and store it securely. You will provide this value when creating your Nexla credential.
For more information about OPUSWatch and its API access, see the OPUSWatch website.
After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your OPUSWatch API key in the API Key field. This key is sent as a bearer token in the Authorization header for all API requests and must be kept confidential.
If your API key is compromised, revoke it and issue a new one through OPUSWatch, then update your Nexla credential with the new value.
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 creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the OPUSWatch connector tile, then select the credential that will be used to connect to OPUSWatch, and click Next; or, create a new OPUSWatch credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common OPUSWatch 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 Users
This endpoint template retrieves users from your OPUSWatch account. Use this template when you need to ingest user records for analysis, reporting, or integration purposes.
This endpoint issues a GET request to the OPUSWatch /users endpoint and reads records from the data array in the response.
[Rest API] List Client
This endpoint template retrieves client information from your OPUSWatch account. Use this template when you need to ingest client records for analysis, reporting, or integration purposes.
This endpoint issues a GET request to the OPUSWatch /client endpoint and reads records from the data array in the response.
[Rest API] List Worker Groups
This endpoint template retrieves worker groups from your OPUSWatch account. Use this template when you need to ingest worker group records for analysis, reporting, or integration purposes.
This endpoint issues a GET request to the OPUSWatch /worker-groups endpoint and reads records from the data array in the response.
[Rest API] List Task Groups
This endpoint template retrieves task groups from your OPUSWatch account. Use this template when you need to ingest task group records for analysis, reporting, or integration purposes.
This endpoint issues a GET request to the OPUSWatch /task-groups endpoint and reads records from the data array in the response.
[Rest API] List Sessions Initial
This endpoint template retrieves sessions from your OPUSWatch account for an initial, full load. Use this template for the first ingestion of session data before switching to the incremental template for ongoing updates.
This endpoint issues a GET request to the OPUSWatch /sessions endpoint and reads records from the data array in the response. The endpoint is paginated, and Nexla automatically fetches subsequent pages until no further data is returned.
[Rest API] List Sessions Incremental
This endpoint template retrieves recently updated sessions from your OPUSWatch account. Use this template for ongoing ingestion after the initial load to capture new and changed session records.
This endpoint issues a GET request to the OPUSWatch /transactional/sessions endpoint with parameters that return breaks, leaves, and archived records filtered by update date, and reads records from the data array in the response.
[Rest API] List Locations
This endpoint template retrieves locations from your OPUSWatch account. Use this template when you need to ingest location records for analysis, reporting, or integration purposes.
This endpoint issues a GET request to the OPUSWatch /locations endpoint and reads records from the data array in the response.
[Rest API] List Rows
This endpoint template retrieves rows from your OPUSWatch account. Use this template when you need to ingest row records for analysis, reporting, or integration purposes.
This endpoint issues a GET request to the OPUSWatch /rows endpoint and reads records from the data array in the response.
[Rest API] List Workers
This endpoint template retrieves workers from your OPUSWatch account. Use this template when you need to ingest worker records for analysis, reporting, or integration purposes.
This endpoint issues a GET request to the OPUSWatch /workers endpoint and reads records from the data array in the response.
[Rest API] List Tasks
This endpoint template retrieves tasks from your OPUSWatch account. Use this template when you need to ingest task records for analysis, reporting, or integration purposes.
This endpoint issues a GET request to the OPUSWatch /tasks endpoint and reads records from the data array in the response.
[Rest API] List Labels
This endpoint template retrieves labels from your OPUSWatch account. Use this template when you need to ingest label records for analysis, reporting, or integration purposes.
This endpoint issues a GET request to the OPUSWatch /labels endpoint and reads records from the data array in the response.
[Rest API] List Varieties
This endpoint template retrieves varieties from your OPUSWatch account. Use this template when you need to ingest crop variety records for analysis, reporting, or integration purposes.
This endpoint issues a GET request to the OPUSWatch /varieties endpoint and reads records from the data array in the response.
[Rest API] List Registrations Initial
This endpoint template retrieves registrations from your OPUSWatch account for an initial, full load. Use this template for the first ingestion of registration data before switching to the incremental template for ongoing updates.
This endpoint issues a GET request to the OPUSWatch /registrations endpoint and reads records from the data array in the response. The endpoint is paginated, and Nexla automatically fetches subsequent pages until no further data is returned.
[Rest API] List Registrations Incremental
This endpoint template retrieves recently updated registrations from your OPUSWatch account. Use this template for ongoing ingestion after the initial load to capture new and changed registration records.
This endpoint issues a GET request to the OPUSWatch /transactional/registrations endpoint with parameters that return breaks, leaves, and archived records filtered by update date, and reads records from the data array in the response.
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.
OPUSWatch data sources can also be manually configured to ingest data from any valid OPUSWatch 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 OPUSWatch 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.
