data.world

data.world is a cloud-based data catalog platform that helps organizations discover, understand, and collaborate on data assets, providing data governance, metadata management, and data lineage tracking to enable better data-driven decision making.

Power end-to-end data operations for your data.world API with Nexla. Our bi-directional data.world connector is purpose-built for data.world, 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 data.world or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your data.world 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 data.world credential, you need to obtain a Service Account Token from your data.world account. The Service Account Token is required to authenticate with the data.world API.

To obtain your Service Account Token, you need to have a data.world account with API access enabled. Once you have access to your account, you can create a service account and generate a Service Account Token from your data.world account settings. The Service Account Token grants access to your data.world resources and is used to authenticate all API requests to the data.world API. The token is sent in the Authorization header with the Bearer prefix for all API requests. For detailed information about service account setup and authentication, refer to the data.world API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Service Account Token	Yes	Yes	Enter the data.world Service Account Token that should be used for updating your data.world account.

Create a credential in Nexla

1. To create a new data.world credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – data.world

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

   Resource descriptions are recommended but are not required. They should be used provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

3. Enter your data.world Service Account Token in the Service Account Token field. This is the Service Account Token you obtained from your data.world account settings. The Service Account Token is sent in the Authorization header with the Bearer prefix (e.g., Bearer {token}) for all API requests to the data.world API.

   Keep your Service Account Token secure and do not share it publicly. The Service Account Token provides access to your data.world resources and should be treated as sensitive information. The Service Account Token is sent in the Authorization header with the Bearer prefix for all API requests to the data.world API. For detailed information about creating service accounts and obtaining tokens, see the data.world API documentation.

4. Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential.

5. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button. Select the data.world connector tile from the list of available connectors. Then, select the credential that will be used to connect to the data.world instance, and click Next; or, create a new data.world 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 data.world 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.

List business glossary entries by owner

This endpoint lists business glossary resources by owner. Use this endpoint when you need to access business glossary entries, metadata, or glossary resources for a specific owner (user or organization) from your data.world account.

• Enter the user name and unique identifier of the user or organization a resource belongs to in the Owner field. This is the owner identifier for which you want to list business glossary entries. The owner can be either a user or an organization.

• The endpoint uses GET requests to https://api.data.world/v0/metadata/glossary/{owner}?from={from}&nextPageToken={nextPageToken} where {owner} is the owner identifier you provide, {from} is the pagination offset, and {nextPageToken} is the token for the next page. The endpoint URL is automatically constructed based on the data.world API base URL, the owner identifier, and pagination parameters.
• The endpoint uses token-based pagination, automatically fetching additional pages as needed. When a response includes a nextPageToken value, Nexla automatically uses it as the nextPageToken query parameter for the subsequent request to fetch the next page of results. The from parameter is used as the initial pagination offset.
• The endpoint will return all business glossary entries for the specified owner. The response data is extracted from the records array in the API response ($.records), with each glossary entry processed individually.

Owner identifiers should match the user name or organization identifier in your data.world account. The endpoint uses token-based pagination (iteration.type: paging.next.token) through the nextPageToken mechanism. When a response includes a nextPageToken value, Nexla automatically uses it as the nextPageToken query parameter for the subsequent request. The response data path is $.records, which extracts all items from the records array in the API response. For detailed information about listing business glossary entries, see the data.world 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

data.world data sources can be manually configured to ingest data from any valid data.world API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex data.world sources, such as sources that use chained API calls to fetch data from multiple endpoints or sources that require custom authentication headers or request parameters.

API Method

1. To manually configure this source, select the Advanced tab at the top of the configuration screen.

2. Select the API method that will be used for calls to the data.world API from the Method pulldown menu. The most common methods are:

   • GET: For retrieving data from the API
   • POST: For sending data to the API or triggering actions
   • PUT: For updating existing data
   • PATCH: For partial updates to existing data
   • DELETE: For removing data

API Endpoint URL

3. Enter the URL of the data.world API endpoint from which this source will fetch data in the Set API URL field. This should be the complete URL including the protocol (https://) and any required path parameters. data.world API endpoints typically follow the pattern https://api.data.world/v0/{endpoint_path}.

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL. The endpoint requires Service Account Token authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. For detailed information about data.world API endpoints and available APIs, see the data.world API documentation.

Path to Data

4. Enter the JSON path that identifies the location of the relevant data within the API response in the Path to Data field. JSON paths use dot notation to navigate through nested JSON structures.

   • For example, if your API response has the structure {"records": [...]}, you would enter $.records[*] to extract all items from the records array.
   • Use $[*] to extract all items from a root-level array.
   • Use $ to extract the entire root-level object.

JSON paths are case-sensitive and must match the exact structure of your API response. data.world API responses may use different structures like records arrays or root-level objects depending on the endpoint. Use the Test button to verify that your JSON path correctly extracts the desired data from the API response.

Save the Data Source

5. Once all configuration steps have been completed, click the Save button to save your data source configuration.

6. The data source will now be available in your data flow and will begin ingesting data according to the configured schedule and endpoint settings.