Skip to main content
The Connect feature provides programmatic access to ingested data and a single interface to access user-facing hosted apps on the NexusOne platform.

​
Key features

Connect has the following key features:
  • Create, view, or manage data APIs and API keys.
  • User access to the following applications hosted on the NexusOne platform:
    • Apache Airflow
    • Apache NiFi
    • DataHub
    • JupyterHub
    • Metabase
    • Ranger
    • Trino

​
What are data APIs?

Data APIs are RESTful API endpoints used to interact with ingested data within the NexusOne platform. This interaction uses the Ask or Engineer feature. Fundamentally, the Ask or Engineer feature generates an SQL query from natural language. This query becomes a rule you can schedule in Apache Airflow to interact with your ingested data. However, if you want to programmatically interact with the rule so you can retrieve the latest processed data, you do that using the data API endpoint. Here’s an example describing the use of data APIs:
  1. Using the NexusOne Ask feature, you’ve defined a data insight rule that outputs the top product sold every Friday.
  2. After you create the Ask API for this rule, your app sends an HTTP request to the endpoint, and the API returns a structured data insight response.
  3. Your app consumes the response to feed it into a dashboard.

​
Data-plane vs control-plane APIs

When you create an Ask API or Engineer API, NexusOne generates a data API and API key you can use to consume data insights or transformation results that already exist. This data API is data-facing:
  • It’s tied to the specific rule you defined earlier.
  • You call it to fetch data insights via Ask or execute data transformation via Engineer.
  • It’s meant for consumption, not for creating or modifying new rules.
On the other hand, the control-plane APIs are configuration APIs:
  • You can find them in the API reference page.
  • They let you programmatically create, modify, or delete rules. These are the same actions you’d do in the NexusOne portal.

​
Use cases

These use-cases are the same as the ones described in the Ask and Engineer overview pages. However, the added feature here is that you implement these use cases within your app, so that you can consume and publish the API response where you see fit. For example, to create your own self-hosted dashboard.

​
Additional resources