Skip to main content

Create a Marketplace listing

This page describes how to create shares and Databricks Marketplace listings for your data products.

Prerequisites

You or your Databricks administrator has completed the Databricks Marketplace provider setup process:

  • Sign up to become a Databricks Marketplace provider, public or private
  • Create a Marketplace provider profile
  • Have the Marketplace admin role assigned to you

For more information, see Become a Databricks Marketplace provider.

Create shares

note

To list a data product that is free and instantly available to consumers, you must include a share when you create the listing. Listings that require you to approve a consumer request, on the other hand, don't require that you include a share in the listing. You can create the share later, after any business agreements are complete and you've approved the consumer's request. If that's what you want to do, skip ahead to Create a listing.

After you have a Databricks account enabled for Delta Sharing and a Databricks workspace enabled for Unity Catalog, you can create the shares that you use to share your data in the Marketplace.

A share is a Delta Sharing object. It's a collection of tables, views, volumes, and AI models that are shareable and securable as a unit. Tables can be shared with any consumer. Volumes, AI models, and notebooks can only be shared with consumers who have access to a Databricks workspace that is enabled for Unity Catalog.

  1. Add data tables, views, or volumes to your Unity Catalog metastore.

    To learn how to create these data assets in Unity Catalog, see:

  2. Create a share and add these data assets to the share.

    To learn how to create and update shares, including permissions required, see Create and manage shares for Delta Sharing.

After your share is created, you can create or update a Marketplace listing that references it.

Notebook example: Sample notebook

In addition to tables, volumes, and views, Databricks recommends sharing Databricks notebooks. Notebooks can help demonstrate example use cases and visualize table properties. Your listing can include sample notebook previews that consumers can import into their workspaces.

Notebook preview on a listing

For more information about creating notebooks, see Databricks notebooks. If you need help creating an effective sample notebook, contact dataproviders@databricks.com.

note

The Sample notebooks display and preview in the listings UI do not work in Chrome Incognito mode.

The following example shows how to create an effective sample notebook. It includes guidance for creating sample notebooks for your listings.

Marketplace starter notebook for data providers

Open notebook in new tab

Create a listing

Marketplace listings enable consumers to browse, select, and access your data products. All dataset listings are automatically shareable with both consumers on Databricks workspaces and consumers on third-party platforms like Power BI, pandas, and Apache Spark.

note

Some data assets, like Unity Catalog volumes, can only be shared with consumers who have access to a Unity Catalog-enabled Databricks workspace. Tables, however, are shareable with all consumers. If you include both tables and volumes in a share, consumers who don't have access to a Unity Catalog-enabled workspace can only access the tabular data.

Permissions required: Marketplace admin role. If you are creating and managing personalized listings (those that require provider approval before they're fulfilled), you must also have the CREATE RECIPIENT and USE RECIPIENT privileges. See Unity Catalog privileges reference.

To create a listing:

  1. Log in to your Databricks workspace.
  2. In the sidebar, click Marketplace icon Marketplace.
  3. In the upper-right corner of the Marketplace page, click Provider console.
  4. On the Provider console page Listings tab, click Create listing.
  5. On the New listing page, enter your listing information. Each page in the listing wizard is described in Fill out listing fields and options.

Fill out listing fields and options

The listing wizard guides you through publishing a Marketplace listing. This section describes the fields and options on each page, along with recommendations for creating an effective listing. During each step, you can save your progress as a draft and view a preview before you publish.

After you fill out all the fields, click Publish.

Step 1: General

Specify the basic information about your listing, such as the name and the provider profile to publish the listing under.

Field name

Description

Listing name

Each listing should have a unique name that helps consumers understand what it offers.

Recommendations:

  • Fewer than 100 characters.
  • Title case (capitalize primary words).

Provider profile

Your organization or company name. Select from the drop-down menu. Databricks creates your profile as part of the partner organization approval process.

How can consumers access data assets in the listing?

This field cannot be changed after the listing is saved as a draft or published. Choose how your consumers gain access to the listing:

  • Data assets are instantly accessible: Allow consumers to gain access to the shared data directly from the Marketplace, without requiring your approval (but requiring acceptance of terms of service).

  • Consumers must request access to the listing: Select this option to require your approval before a consumer can access the shared data. Use this option if you require a business agreement before you make the data product available to consumers. You must manage the business agreement with consumers outside of Databricks Marketplace. You can initiate communications using the consumer email address.

    View and handle consumer requests on the Provider Console > Consumer requests tab. See Manage requests for your data product in Databricks Marketplace.

Publish to

Choose one of the following:

  • Public Marketplace
    • All consumers can browse and view the listing in the public Databricks Marketplace.
  • Private exchange

Step 2: Data assets

Select which types of data assets to include in your listing.

Field name

Description

Tables

Include structured tabular data from your share.

Files

Volumes that contain a variety of data, such as images, audio, video, and more.

Models

AI models that consumers can deploy for inference.

Notebooks

Interactive notebooks for data science and machine learning workflows. For more information, see Notebook example: Sample notebook.

Solution accelerators

Prebuilt solution templates hosted in a Git repository that consumers can clone.

MCP server (Public Preview)

Model Context Protocol (MCP) servers are tools and APIs that AI agents can use to interact with external systems. Only other users using Databricks can install MCP servers listed on the Marketplace. For more details on the setup process, see MCP server listing fields.

When you select this option, fill in the required fields, and advance to the next step, the listing is saved automatically.

Select share

If you selected to include tables, files, models, or notebooks in your listing, select the share that contains the data assets for your listing. You can create a new share if needed. For more information, see Create shares.

Step 3: Attributes

Add attributes and categories to make your listing more discoverable.

Field name

Description

Categories

Select the categories that consumers can use to filter listings. Categories also appear as tags on listing tiles and detail pages.

Update frequency (optional)

Specify how often the data asset in your listing is updated on Databricks.

Advanced attributes

Advanced data attributes are optional. They include fields such as geographic coverage, collection granularity, and time range. Adding attributes helps consumers understand more about your data product. Select as many attributes as you like.

Step 4: Details

Provide a short description and a detailed description to help consumers understand what data assets are included in your listing. You can also add resources such as sample notebooks, documentation links, and policy URLs.

Field name

Description

Short description

A short, informative explanation of the dataset that expands on the listing name. This field appears in listing tiles and consumer search results.

Recommendations:

  • Fewer than 100 characters. Cannot exceed 160 characters.
  • Sentence case (capitalize only the first word and any proper nouns or acronyms).

Description

The detailed description of your data should include a summary of the data and assets being offered in the listing.

Basic rich text formatting is supported (that is, bold, italics, bullets, and numbered lists), using Markdown syntax.

Recommendations:

  • Include benefits and use cases.
  • Provide brief guidance about how to use the data and sample use cases.
  • Include sample datasets and field names.
  • Specify schemas, tables, and columns.
  • Use consistent punctuation and syntax.
  • Add an extra line break between paragraphs.
  • Don't repeat the attributes that you defined under Add Attribute.

Add notebook

Databricks recommends that you share sample notebooks to demonstrate how best to use the data and to increase listing downloads. Add up to 10 notebooks. For more information about creating notebooks, see Notebook example: Sample notebook and Databricks notebooks.

Clicking Add notebook automatically saves the listing.

Documentation

A URL that links to documentation that can help consumers use or understand your dataset (for example, a dataset dictionary).

Privacy policy

A URL that links to your privacy policy. The privacy policy must be publicly accessible and require no login.

License

A URL that links to your license.

Terms of service

A URL that links to your terms of service for the appropriate use of the shared data assets. Terms of service must be publicly accessible and require no login.

MCP server listing fields

Preview

This feature is in Public Preview.

Model Context Protocol (MCP) servers are tools and APIs that AI agents can use to interact with external systems. You can list MCP servers under the "AI" product category in Marketplace to make them discoverable to AI engineers who are building agents.

When creating an MCP server listing, complete the same basic listing fields as for dataset listings, plus the following MCP-specific fields:

Field name

Description

Authentication type

Specify the authentication method your MCP server requires:

  • OAuth User to Machine Per User: For OAuth 2.0 authentication flows, requires you to specify a token and authorization endpoint
  • Bearer Token: For API key or token-based authentication

Host

The hostname or domain where your MCP server is accessible.

Port

The network port number that your MCP server listens on.

Base path (Optional)

The URL path prefix for your MCP server's API endpoints. Leave blank if your MCP server is hosted at the root path.

Tag (Optional)

A version identifier or release tag for your MCP server.

Token endpoint (OAuth User to Machine Per User only)

The OAuth 2.0 authorization server endpoint used to obtain access tokens. The authorization code is exchanged for an access token using this endpoint when consumers install this MCP server.

Authorization endpoint (OAuth User to Machine Per User only)

The OAuth 2.0 authorization server endpoint used to get authorization codes. Consumers are redirected to this endpoint to authenticate and authorize access to your MCP server.

OAuth scope (OAuth User to Machine Per User only, optional)

The OAuth 2.0 permissions scope that defines what resources and operations consumers can access.

OAuth credential exchange method (OAuth User to Machine Per User only)

How OAuth 2.0 credentials are exchanged.

Analyze consumer activity using system tables (Public Preview) and dashboards

If you have system tables enabled in your account, you can use the Marketplace system tables to analyze consumer activity on your listings. For more information, see Marketplace system tables reference.

You can also use the Provider Analytics Dashboard to monitor listing views, requests, and installs. The dashboard pulls data from the system tables. See Monitor listing usage metrics using dashboards.

Resource quotas

Unity Catalog enforces resource quotas on all securable objects, including Marketplace listings per metastore and providers per account. These quotas are listed in Resource limits. If you expect to exceed these resource limits, contact your Databricks account team.

You can monitor your quota usage using the Unity Catalog resource quotas APIs. See Monitor your usage of Unity Catalog resource quotas.

Next steps