Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
To ensure Marketplace functions seamlessly with your Governance app, there are some setup requirements.
Users registered in Immuta to ensure users can log in to the Marketplace app, request access, and be provisioned access in the data platform.
If the configured identity manager (IAM) to Immuta is syncing attributes (groups don't matter) from it, the checkbox to allow Immuta attributes to be applied to the IAM's users and groups must be enabled. To enable this setting, edit the IAM from the Governance app settings page.
An integration configured and data sources registered in Immuta: Tables, views, and files registered as data sources in the Governance app can be used in data products from the Marketplace app. These registered data sources within the data products are provisioned to the data consumers in the data platform when approved for access. Additionally, users can request masking exceptions on supported columns from these data sources.
: Each data product is comprised of data sources from a single domain, and delegate permissions to specific users that are knowledgeable about the data.
Give your Marketplace app the custom look and feel of your company by supplying your own branding:
Add your logo (with light and dark mode options)
Select a primary and accent color
Customizing Marketplace adds appeal for your data consumers and makes the Marketplace app appear more proprietary to your business.
Requirement: Immuta permission APPLICATION_ADMIN
From the Governance app,
Navigate to the App Settings page and click on the Marketplace tab.
In the Logo section, click Upload. Upload both a light mode and dark mode version of the logo since the mode is specific to the client's preference. It can be the same image if visible in both modes.
In the pop-up, select your logo. Images should be transparent PNG or SVG and a maximum size of 1 MB. For best results, use a horizontally aligned image 100px by 800px or smaller.
Click Save.
You will need to refresh the Marketplace app in order to see your changes after saving.
From the Governance app,
Navigate to the App Settings page and click on the Marketplace tab.
In the Color section, click the dropdown and select the primary and accent colors.
You can see the preview of the colors in the preview section.
Click Save.
You will need to refresh the Marketplace app in order to see your changes after saving.
This section is for understanding Marketplace and data products.
Manage data products: Publish and manage new data products in Marketplace.
: Add your own logo and colors to the Marketplace app.
: This reference guide describes the setup requirements and prerequisites that must be completed in the Governance app to prepare for the Marketplace app.
: This reference guide describes data products and their features.
: This reference guide describes Immuta permissions and the actions users with those permissions can take in the Governance and Marketplace app.
: This reference guide describes your options for automated data source assignment when creating domains in the Governance app for seamless data product creation in the Marketplace app.
Data products are what are published to the Marketplace app by data product managers. They are typically highly curated and ready for consumption by the business.
They contain the following metadata:
Name
Description (optional)
Subject matter expert (optional)
Access requests, including access requests for the data product and masking exceptions
Members
Request forms work as templates that can be added to multiple data products and dictate the same access request process for any data product that uses it. Request forms provide consistent and reliable information from the requesters to the data stewards approving or denying access requests. One request form is applied to each data product and will be used for both data access and masking exception requests. Request forms contain the following content:
Form details: Details about the request form such as the name and request questions. Request questions are the questions a data consumer must answer, and the answers will be recorded in the access request for the data steward to review.
Review flow: The review flow configures if the access request requires approval or not, the data stewards who will approve the requests, or the ability for data product owners to select their own data stewards.
Data use agreement: A data use agreement can optionally be included. If it is, the data consumer must acknowledge it before they can request access, ensuring they agree to how the data should be used.
Linked data products: This is a list of all the data products in Marketplace that use this request form.
Data sources represent any type of data that could be provided by a data product and registered in Immuta. These are currently tables and views from your data platform and objects from S3 storage. What data sources are available for the data product manager to add are dependent on the domain specified when publishing the data product.
Every data product has a list of the columns in the data sources of the data product. The list is separated by data source and provides details about the column like the name, tags applied to the column, and if the column is impacted by a masking data policy. Data consumers can make masking exception requests on the masked columns, which allow approved users to see unmasked data.
Note that all data product settings and metadata are point-in-time of when the access request was made and approved. For example, if you change the data use agreement for a data product after access requests were approved for five users, those five users would remain approved under the previous data use agreement. Immuta only updates the data product with the changes for new requests, not approved or pending requests.
Integrating with existing catalogs: This reference guide describes how to connect data products in your existing catalogs with data products in Marketplace with automated deep links.
Typically, you would give a data product manager CREATE permission in a schema or database that they can use as their sandbox for generating new tables/views natively in their data platform using data engineering tools like dbt. Those newly generated tables/views (or even S3 objects) are what they can use as the data sources for their data products.
You must get these new data objects from the data platform as registered in Immuta and assigned to a domain so that they can be published in data products:
Immuta automatically registers objects through periodic polling (24 hours by default) to detect changes in the data platform and represent those changes in Immuta, as data sources. These checks can also be manually triggered.
Once the objects are registered in Immuta as data sources, they are assigned to a domain one of two ways:
Manually: The data source is assigned to the domain through the (or ) by a user with GOVERNANCE permission.
Dynamically (recommended): The data source is automatically assigned to the domain based on if it has a specific tag.
Tags can be applied directly to the tables/views in the data platform (Snowflake, Databricks Unity Catalog, and AWS Lake Formation only), imported from a , or applied through the Immuta UI.
See the examples in the tabs below to understand your options when dynamically assigning data sources to domains for data products.
As you can see in all the examples, the GOVERNANCE user was able to still limit what data sources land in the HR Domain by limiting the scope of power where the data engineer could apply tags. In the first two examples, they are limited to applying tags only in the schema where they have CREATE permission in the data platform. In the second example, they are limited to where they can apply tags by where they were made data owners.
If you would like data consumers to discover data products through your existing catalog rather than through the Immuta Marketplace app, you can redirect requests for access from your catalog to the Marketplace app. However, .
Integration is made possible through deep link URLs provided by the Marketplace app that direct the user to the correct request access screen for any given data product. At a high level the workflow looks like this:
A data product is published in your catalog that the same data product in the Marketplace app.
The consumer discovers the data product in your catalog.
User with USER_ADMIN permission provides the data engineers with permission Manage Data Products in that domain.
Data engineer creates 6 new tables in the schema business.hr-data-products and wants to now have them available as data sources for a data product.
When Immuta registers those objects, it will include the connection tag to represent the schema and database.
If Immuta hasn't yet found those new tables through periodic polling, the data engineer executes object sync over the Immuta API so that Immuta will find them.
Those 6 tables will appear as data sources within the domain and are now available for data products.
The consumer initiates a redirect from your catalog to the request access page for that mirrored data product in the Marketplace app.
From this point forward, the access request works the same.
In order to request access to a data product, your catalog must have a mirrored representation of the corresponding data product that exists in the Marketplace app. Depending how you configure the redirect, it's likely these need to be named exactly the same so that the redirect works correctly and you don't confuse your data consumers.
You can either separately publish the data product in your catalog, or you can use webhooks to listen and automate publishing in your catalog when published in the Marketplace app.
To support redirects, Marketplace exposes deep link URLs to the access request page for each data product or access request page for masking exceptions. The URL can be built using this format or copy the pre-built link to your clipboard by clicking Request access link on the data product's details tab:
{data product name} : This can be either the data product name or the data product ID for the specific data product. The data product ID can be found by examining the data product details page's URL here: https://app.immutacloud.com/marketplace/data-product/{data product id}/details
{access type}: This can be either data-access (providing access to the data product and its data sources) or masking-exception (providing unmasked access to the masked columns of the data sources in the data product).
{account identifier}: This is . This will ensure the user being redirected to request access does not need to know the accountId in order to log in
These URLs will direct the user to the data product's access request screen or, if they are not authenticated, to the Marketplace login screen with a redirect back to the access request screen.
The following are only recommendations for popular catalogs, you can do this however you feel appropriate and can reuse some of these approaches in different catalogs or custom marketplace applications you may have built yourselves.
The first thing to consider when linking a catalog is how you appropriately represent a domain, data product, and data source in that catalog should it not have those object types. The most common approach with Collibra is the following:
Domain (which contains the data product(s)) = Collibra Collection
Data product (which contains the data source(s)) = Collibra Data Set
Data source = Collibra Data Asset
A Collibra custom workflow can be leveraged to redirect to the Marketplace app to request access. Download a sample workflow below. This workflow was exported in a way that allows you to import it and see its workflow "code" in the Collibra Workflow designer should you want to make changes.
This workflow is intended to be an example you can use and is not part of the Immuta software product nor SLAs.
Once you are happy with the workflow "code", you must deploy it with the button at the top of the Collibra workflow designer. Then complete the setup:
Navigate to Settings, and then Workflows.
Find the newly deployed Request Access Through Immuta workflow and select it.
Uncheck "Show in global create"
This workflow "attaches" to a Data Set by configuring the "Applies To" in Collibra to a Data Set. You can change this to whatever object you represent data products with in Collibra.
Ensure the variables are empty
For the "Start Events" choose "Workflow Started"
Under "Other" ensure "Any user can start the workflow"
Save
Once complete, when you visit a Data Set in Collibra there should be a new action "Request Access through Immuta". When clicked, a modal will appear asking to request access, and when selected, will dynamically redirect to the appropriate data product in the Immuta Marketplace app using the data product ID URL option. Since it uses the ID to reference the data product in Immuta Marketplace, you must create the data product using the same ID as Collibra. It is possible to create data products with your own provided ID using the Immuta Marketplace API, but it must be a UUID, which is the case with Collibra IDs.
The Alation Marketplace has a seamless integration with the Immuta Marketplace app. Simply add Immuta as a delivery system within the Alation data products, which will redirect users to request access in Immuta. See the example delivery system configuration below and view the Alation documentation for additional details. Ensure the uri aligns with the specific link to the Immuta data product that represents to the Alation data product as described above.
The first thing to consider when linking a catalog is how you appropriately represent a domain, data product, and data source in that catalog should it not have those object types. There is not an obvious approach to this in Alation; the best we've seen is:
Domain (which contains the data product(s)) = Alation Glossary
Data product (which contains the data source(s)) = Alation Domain
Data source = Alation Data
Unlike with the Alation Marketplace, there is not a dynamic way to redirect to the Immuta Marketplace app to request access. Instead, you should include a Description in the Alation Domain which includes a hyperlink to request access using the data product ID URL option.
The first thing to consider when linking a catalog is how you appropriately represent a domain, data product, and data source in that catalog should it not have those object types. Atlan's object mapping is very close to the Marketplace app:
Domain (which contains the data product(s)) = Atlan Domain
Data product (which contains the data source(s)) = Atlan Data Product
Data source = Atlan Data Asset
Unlike Collibra, there is not a dynamic way to redirect to the Marketplace app to request access. Instead, we recommend that you include a READ ME in the Atlan data product which includes a hyperlink to request access using the data product ID URL option.
We hope to work closely with Atlan to make this smoother in the future - ask them about it!
While you are able to create request and approval flows in some catalogs and even other tools, it is not recommended. Doing data request and approval flows in Immuta has various benefits:
When approved, the access is automatically provisioned in the data platform.
Approvals can be temporary, and when that time limit expires, access will be de-provisioned automatically.
The person making a determination on a request is presented with details about the request, including existing data access, in order to make a meaningful access decision. Furthermore, users doing approvals to data are different from the users doing approvals to applications, and require a more specific process and workflow more coupled to the data platform and its metadata
Multiple approvers can be configured.
https://app.immutacloud.com/marketplace/data-product/{data product}/request-access?type={access type}?accountId={account identifier}deliverySystems:
Immuta:
type: SQL
uri: "https://app.immutacloud.com/marketplace/data-product/{data product name}/request-access?accountId={account identifier}"
accessRequestInstruction:
instruction: "Go [here](https://app.immutacloud.com/marketplace/data-product/{data product name}/request-access?type=data-access?accountId={account identifier}) to request access to this data product.
Go [here](https://app.immutacloud.com/marketplace/data-product/{data product name}/request-access?type=masking-exception?accountId={account identifier}) to request a masking exception for data in this data product."
type: textClick Publish product.
Select the Domain from the dropdown. You will only be able to include data sources from this domain in your data product. If you do not see a domain available, create one with at least one data source.
Click Next.
Select the data sources you want in the data product. If you do not see a data source you expected to see, it is not in the domain you selected.
Click Next.
Enter the following metadata for your new data product:
Name of the data product
Description of the data product (optional)
Enter the subject matter expert (optional). This should be a user that data consumers and stewards can reach out to for any questions about the data product.
Click Next.
Using the dropdown, select a request form or scroll down to Create new +. Any data consumer requesting access or making a masking exception request to your data product will need to complete the same request form:
Select an existing request form: Review the form details, review flow, data use agreement, and linked products.
Create new: This will create a new request form that will be used for this data product and can be used in data products published in the future.
Click Next.
If your request form has the review flow set to Delegate to data product you must set your data stewards:
Choose if you would like to require approval for requests on this data product:
Yes: When the user makes a request on a data product, in addition to acknowledging the data use agreement and answering the required question, they will need to be approved by the data stewards.
Click Publish data product.
Ensure you set the correct global segment and use a Marketplace-specific personal access token (PAT) when using the Marketplace API. See the Marketplace API docs for additional guidance or to download the OpenAPI YAML for your own client generation.
To revoke a member's access, you can remove them from the a data product,
Select the data product and navigate to the Members tab.
Click the more actions icon.
Select Revoke Access.
Ensure you set the correct global segment and use a Marketplace-specific personal access token (PAT) when using the Marketplace API. See the Marketplace API docs for additional guidance or to download the OpenAPI YAML for your own client generation.
Once a data product has been published, many components can be edited from different parts of the data product:
Details: Edit the name, description, or subject matter expert
Data sources: Add or remove data sources from the data product
Request form: Edit the request form assigned to the data product
Select the data product.
Navigate to the tab with the information you want to edit.
Click Edit.
Make your edits and click Save.
Ensure you set the correct global segment and use a Marketplace-specific personal access token (PAT) when using the Marketplace API. See the Marketplace API docs for additional guidance or to download the OpenAPI YAML for your own client generation.
To update the request form of a data product:
Run POST /api/request-form to create a new request form: Use the ID from the response in the next call.
Run PUT/api/data-product/{id} to add the new request form to the data product: The {id} in the request should be the data product ID and the request form ID from the previous call should be included in the payload.
Ensure you set the correct global segment and use a Marketplace-specific personal access token (PAT) when using the Marketplace API. See the Marketplace API docs for additional guidance or to download the OpenAPI YAML for your own client generation.
To update data sources associated with a data product:
Data products can be suspended. Suspending access revokes all access to data sources in the data product that was gained from the approvals in the Marketplace and all masking exceptions granted by approvals. However, the data product access can be resumed to grant the approvals again.
Select the data product.
Navigate to the Settings tab.
Select Suspend access and then click Suspend access on the modal.
Ensure you set the correct global segment and use a Marketplace-specific personal access token (PAT) when using the Marketplace API. See the Marketplace API docs for additional guidance or to download the OpenAPI YAML for your own client generation.
Update the suspended parameter using the endpoint below:
It is also possible to delete data products, which will remove all users' access to the data sources within the data product and any masking exceptions associated with the data product. Deleting a data product cannot be undone.
Select the data product.
Navigate to the Settings tab.
Click Delete data product.
Enter the name of your data product in the textbox and then click Delete again.
Ensure you set the correct global segment and use a Marketplace-specific personal access token (PAT) when using the Marketplace API. See the Marketplace API docs for additional guidance or to download the OpenAPI YAML for your own client generation.
Anything a Data Steward can do -> a Data Product Manager can do; anything a Data Product Manager can do -> a user with GOVERNANCE permission can do. However, both the Data Product Manager and GOVERNANCE users must be assigned as a Data Steward in order to approve or deny an access request.
And the scope of their permissions grow as you move up the layers:
See the table below for the full breakdown of what Marketplace actions require which Immuta permissions:
Yes
Manage a data product
Yes
Yes
Make access request determinations
Yes
Alter a data product
Yes
Yes
Yes (partial)
Create a request form
Yes
Yes
Create an access request
Yes
Yes
Yes
Yes
Revoke a member from a data product
Yes
Yes
Yes
Revoke a masking exception
Yes
Yes
Yes
Configure webhooks
Yes
Customize the Marketplace app
Yes
Install Immuta Slack app
Yes
Enable Slack and email notifications
Yes, all users
Yes, self
Can act in each data product they are assigned to
Can act in the domain they have the Manage Data Products permission in
Can act across all of Immuta, regardless of domain
Create a domain
Yes
Grant Manage Data Products in a domain
Enter the form name, which is how other data product owners can add the request form to their own data product.
Enter one or more request questions for the data consumer to answer:
Enter a question and select the answer format in the dropdown.
Use the switch to dictate if the question is required.
Click the + icon to add more questions.
Select how you want the review flow determined:
Delegate to data product: Data products that use this form will configure their own review flow.
In this request form: The review flow defined here will apply to all assigned data products.
Choose if you would like to require approval for requests on this data product:
Yes: When the user makes a request on a data product, in addition to acknowledging the data use agreement and answering the required question, they will need to be approved by the data stewards.
Assign the data stewards: Choose the Immuta source from the dropdowns that will dictate who is a data steward. If you select a domain permission, the data steward must have that domain-specific permission for the domain that the data product is built off of.
Choose if you would like to require all or any data stewards to approve:
Add a data use agreement (optional). Use the default data use agreement or Create new +. The data use agreement is what the data consumer must agree to when requesting access or a masking exception to your data product.
Assign the data stewards: Choose the Immuta source from the dropdowns that will dictate who is a data steward. If you select a domain permission, the data steward must have that domain-specific permission for the domain that the data product is built off of.
Choose if you would like to require all or any data stewards to approve:
All stewards: For every source you select, a data steward from that source must make a determination. If a data steward qualifies multiple sources, their determination will count for each of the sources they have. If any of the data stewards deny the request, it will be denied. If any of the data stewards temporarily approve the request, once the determination is made, the user will be approved for temporary access for the shortest time period given.
Any steward: A single determination is required for the request, and any data steward with any of the sources dictated can make the determination.
No: When the user makes a request on a data product, they will be automatically approved once they acknowledge the data use agreement and answer any question required for access:
Auto approve: Enter the reason users do not need approval.
Auto approve with expiration: Enter the reason users do not need approval and use the dropdown to select how long users will have access to the data before the access expires.
All stewards: For every source you select, a data steward from that source must make a determination. If a data steward qualifies multiple sources, their determination will count for each of the sources they have. If any of the data stewards deny the request, it will be denied. If any of the data stewards temporarily approve the request, once the determination is made, the user will be approved for temporary access for the shortest time period given.
Any steward: A single determination is required for the request, and any data steward with any of the sources dictated can make the determination.
No: When the user makes a request on a data product, they will be automatically approved once they acknowledge the data use agreement and answer any question required for access:
Auto approve: Enter the reason users do not need approval.
Auto approve with expiration: Enter the reason users do not need approval and use the dropdown to select how long users will have access to the data before the access expires.
Updates the specified access request to revoked and revokes access to data sources associated with the data product
Create a request form
Request form with name already exists.
Update the data sources associated with the data product. Any currently associated data sources not included in the payload will be removed.
Update an existing data product by ID
Data product name
^[a-zA-Z0-9)(\-_/\\\s]*$Data product description
Data product description
All sales records from the current fiscal year["4d004a3a-4568-4c1d-822e-30958ef898dc"]Data product ID
Whether access to the data product's data sources is suspended
falseData product name
^[a-zA-Z0-9)(\-_/\\\s]*$Data product description
Data product description
All sales records from the current fiscal year["4d004a3a-4568-4c1d-822e-30958ef898dc"]Data product ID
Data Product name in use.
No content
Data product name
^[a-zA-Z0-9)(\-_/\\\s]*$Data product description
Data product description
All sales records from the current fiscal year["4d004a3a-4568-4c1d-822e-30958ef898dc"]Data product ID
Whether access to the data product's data sources is suspended
falseNo content
POST /marketplace/api/data-product HTTP/1.1
Host: na.api.immutacloud.com
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 877
{
"name": "text",
"description": "All sales records from the current fiscal year",
"metadata": {
"subjectMatterExpert": {
"id": "123e4567-e89b-12d3-a456-426614174000",
"username": "text",
"name": "text"
}
},
"domains": [
"4d004a3a-4568-4c1d-822e-30958ef898dc"
],
"dataAccessPolicy": {
"version": "text",
"rules": [
{
"conditions": {
"all": []
},
"event": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
}
],
"defaultEvent": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
},
"maskingExceptionPolicy": {
"version": "text",
"rules": [
{
"conditions": {
"all": []
},
"event": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
}
],
"defaultEvent": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
},
"id": "123e4567-e89b-12d3-a456-426614174000",
"dataSources": [
{
"sourceId": "text"
}
],
"requestFormId": "text"
}{
"id": "text",
"name": "text",
"description": "All sales records from the current fiscal year",
"domains": [
"4d004a3a-4568-4c1d-822e-30958ef898dc"
],
"suspended": false,
"createdBy": "123e4567-e89b-12d3-a456-426614174000",
"createdAt": "2025-12-14T17:28:25.679Z",
"updatedAt": "2025-12-14T17:28:25.679Z",
"status": "PENDING",
"expiration": "2025-12-14T17:28:25.679Z",
"stats": {
"dataSourceCount": 1,
"pendingRequestCount": 1,
"approvedRequestCount": 1,
"revokedRequestCount": 1,
"canceledRequestCount": 1,
"deniedRequestCount": 1,
"totalRequestCount": 1
},
"requestId": "text",
"sourceTypes": [
"Databricks",
"Redshift",
"Snowflake"
],
"metadata": {
"subjectMatterExpert": {
"id": "123e4567-e89b-12d3-a456-426614174000",
"username": "text",
"name": "text"
}
},
"dataAccessPolicy": {
"version": "text",
"rules": [
{
"conditions": {
"all": []
},
"event": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
}
],
"defaultEvent": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
},
"maskingExceptionPolicy": {
"version": "text",
"rules": [
{
"conditions": {
"all": []
},
"event": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
}
],
"defaultEvent": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
}
}{
"id": "123e4567-e89b-12d3-a456-426614174000",
"name": "text",
"fields": [
{
"id": "123e4567-e89b-12d3-a456-426614174000",
"type": "DROPDOWN",
"label": "text",
"required": true,
"options": [
{
"value": "text"
}
]
}
],
"policy": {
"version": "text",
"rules": [
{
"conditions": {
"all": []
},
"event": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
}
],
"defaultEvent": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
},
"dataUseAgreements": [
{
"id": "123e4567-e89b-12d3-a456-426614174000",
"name": "text",
"body": "text"
}
],
"createdBy": {
"globalUserId": "123e4567-e89b-12d3-a456-426614174000",
"name": "text"
},
"createdAt": "2025-12-14T17:28:25.679Z",
"updatedBy": {
"globalUserId": "123e4567-e89b-12d3-a456-426614174000",
"name": "text"
},
"updatedAt": "2025-12-14T17:28:25.679Z",
"version": "text"
}{
"id": "text",
"name": "text",
"description": "All sales records from the current fiscal year",
"domains": [
"4d004a3a-4568-4c1d-822e-30958ef898dc"
],
"suspended": false,
"createdBy": "123e4567-e89b-12d3-a456-426614174000",
"createdAt": "2025-12-14T17:28:25.679Z",
"updatedAt": "2025-12-14T17:28:25.679Z",
"status": "PENDING",
"expiration": "2025-12-14T17:28:25.679Z",
"stats": {
"dataSourceCount": 1,
"pendingRequestCount": 1,
"approvedRequestCount": 1,
"revokedRequestCount": 1,
"canceledRequestCount": 1,
"deniedRequestCount": 1,
"totalRequestCount": 1
},
"requestId": "text",
"sourceTypes": [
"Databricks",
"Redshift",
"Snowflake"
],
"metadata": {
"subjectMatterExpert": {
"id": "123e4567-e89b-12d3-a456-426614174000",
"username": "text",
"name": "text"
}
},
"dataAccessPolicy": {
"version": "text",
"rules": [
{
"conditions": {
"all": []
},
"event": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
}
],
"defaultEvent": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
},
"maskingExceptionPolicy": {
"version": "text",
"rules": [
{
"conditions": {
"all": []
},
"event": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
}
],
"defaultEvent": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
}
}{
"id": "text",
"name": "text",
"description": "All sales records from the current fiscal year",
"domains": [
"4d004a3a-4568-4c1d-822e-30958ef898dc"
],
"suspended": false,
"createdBy": "123e4567-e89b-12d3-a456-426614174000",
"createdAt": "2025-12-14T17:28:25.679Z",
"updatedAt": "2025-12-14T17:28:25.679Z",
"status": "PENDING",
"expiration": "2025-12-14T17:28:25.679Z",
"stats": {
"dataSourceCount": 1,
"pendingRequestCount": 1,
"approvedRequestCount": 1,
"revokedRequestCount": 1,
"canceledRequestCount": 1,
"deniedRequestCount": 1,
"totalRequestCount": 1
},
"requestId": "text",
"sourceTypes": [
"Databricks",
"Redshift",
"Snowflake"
],
"metadata": {
"subjectMatterExpert": {
"id": "123e4567-e89b-12d3-a456-426614174000",
"username": "text",
"name": "text"
}
},
"dataAccessPolicy": {
"version": "text",
"rules": [
{
"conditions": {
"all": []
},
"event": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
}
],
"defaultEvent": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
},
"maskingExceptionPolicy": {
"version": "text",
"rules": [
{
"conditions": {
"all": []
},
"event": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
}
],
"defaultEvent": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
}
}{
"id": "text",
"name": "text",
"description": "All sales records from the current fiscal year",
"domains": [
"4d004a3a-4568-4c1d-822e-30958ef898dc"
],
"suspended": false,
"createdBy": "123e4567-e89b-12d3-a456-426614174000",
"createdAt": "2025-12-14T17:28:25.679Z",
"updatedAt": "2025-12-14T17:28:25.679Z",
"status": "PENDING",
"expiration": "2025-12-14T17:28:25.679Z",
"stats": {
"dataSourceCount": 1,
"pendingRequestCount": 1,
"approvedRequestCount": 1,
"revokedRequestCount": 1,
"canceledRequestCount": 1,
"deniedRequestCount": 1,
"totalRequestCount": 1
},
"requestId": "text",
"sourceTypes": [
"Databricks",
"Redshift",
"Snowflake"
],
"metadata": {
"subjectMatterExpert": {
"id": "123e4567-e89b-12d3-a456-426614174000",
"username": "text",
"name": "text"
}
},
"dataAccessPolicy": {
"version": "text",
"rules": [
{
"conditions": {
"all": []
},
"event": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
}
],
"defaultEvent": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
},
"maskingExceptionPolicy": {
"version": "text",
"rules": [
{
"conditions": {
"all": []
},
"event": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
}
],
"defaultEvent": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
}
}DELETE /marketplace/api/data-product/{id}/request/{requestId} HTTP/1.1
Host: na.api.immutacloud.com
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*
POST /marketplace/api/request-form HTTP/1.1
Host: na.api.immutacloud.com
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 510
{
"name": "text",
"fields": [
{
"id": "123e4567-e89b-12d3-a456-426614174000",
"type": "DROPDOWN",
"label": "text",
"required": true,
"options": [
{
"value": "text"
}
]
}
],
"policy": {
"version": "text",
"rules": [
{
"conditions": {
"all": []
},
"event": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
}
],
"defaultEvent": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
},
"id": "123e4567-e89b-12d3-a456-426614174000",
"dataUseAgreementIds": [
"123e4567-e89b-12d3-a456-426614174000"
]
}PUT /marketplace/api/data-product/{id} HTTP/1.1
Host: na.api.immutacloud.com
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 895
{
"name": "text",
"description": "All sales records from the current fiscal year",
"metadata": {
"subjectMatterExpert": {
"id": "123e4567-e89b-12d3-a456-426614174000",
"username": "text",
"name": "text"
}
},
"domains": [
"4d004a3a-4568-4c1d-822e-30958ef898dc"
],
"dataAccessPolicy": {
"version": "text",
"rules": [
{
"conditions": {
"all": []
},
"event": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
}
],
"defaultEvent": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
},
"maskingExceptionPolicy": {
"version": "text",
"rules": [
{
"conditions": {
"all": []
},
"event": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
}
],
"defaultEvent": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
},
"id": "123e4567-e89b-12d3-a456-426614174000",
"dataSources": [
{
"sourceId": "text"
}
],
"requestFormId": "text",
"suspended": false
}PUT /marketplace/api/data-product/{id}/datasources HTTP/1.1
Host: na.api.immutacloud.com
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 37
{
"dataSources": [
{
"sourceId": "text"
}
]
}PUT /marketplace/api/data-product/{id} HTTP/1.1
Host: na.api.immutacloud.com
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 895
{
"name": "text",
"description": "All sales records from the current fiscal year",
"metadata": {
"subjectMatterExpert": {
"id": "123e4567-e89b-12d3-a456-426614174000",
"username": "text",
"name": "text"
}
},
"domains": [
"4d004a3a-4568-4c1d-822e-30958ef898dc"
],
"dataAccessPolicy": {
"version": "text",
"rules": [
{
"conditions": {
"all": []
},
"event": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
}
],
"defaultEvent": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
},
"maskingExceptionPolicy": {
"version": "text",
"rules": [
{
"conditions": {
"all": []
},
"event": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
}
],
"defaultEvent": {
"type": "approve",
"params": {
"comment": "text",
"duration": 1,
"durationUnit": "HOURS"
}
}
},
"id": "123e4567-e89b-12d3-a456-426614174000",
"dataSources": [
{
"sourceId": "text"
}
],
"requestFormId": "text",
"suspended": false
}DELETE /marketplace/api/data-product/{id} HTTP/1.1
Host: na.api.immutacloud.com
Authorization: Bearer YOUR_SECRET_TOKEN
Accept: */*