skills.rest
kirivandubai
kirivandubaiCOMMUNITY
Explore all skills by this author →
GitHub

marketplace

Manages Denodo 9.5 Data Marketplace tags, categories, and external elements via REST API.

Updated Sep 4, 2026
Search Tags:#rest api#tags#data catalog#lineage#data marketplace#denodo#external elements
One-click install
npx skills add https://github.com/kirivandubai/denodo_wipe_coading_skills --skill marketplace-kirivandubai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: marketplace
Source: https://github.com/kirivandubai/denodo_wipe_coading_skills/tree/main/skills/marketplace
Command: npx skills add https://github.com/kirivandubai/denodo_wipe_coading_skills --skill marketplace-kirivandubai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? The Denodo Data Marketplace is a separate server driven by REST rather than VQL, with numeric server-assigned ids, per-server scoping, and synchronization semantics that make naive automation fail silently. This Skill provides verified templates and read-back procedures for creating and assigning marketplace objects without corrupting a shared catalog. ## Core Features & Use Cases - Marketplace tags and categories: Create, update, and assign tags and category trees to views using lookup-first idempotent sequences, with exact-name matching to avoid substring-filter collisions. - Catalog synchronization: Synchronize the marketplace's copy of the VDP catalog (databases and views) with conflict-handling modes, checking the change radius before applying. - External elements: Register dashboards, ETL jobs, data contracts, notebooks, and AI agents from other tools by building the interface-view contract in VQL and importing it, so assets appear in the 360 lineage graph. - Use Case: A data team wants their Tableau dashboards to appear in the Denodo Data Marketplace beside the views they consume. The Skill creates the provider type and tool server, generates the contract VQL, imports the elements, and verifies lineage from the view's side. ## Quick Start Ask the agent to create a marketplace tag named pii, assign it to a synchronized view, and verify the assignment from both the tag's and the view's side.

Frequently Asked Questions about marketplace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a tag in the Denodo Data Marketplace API?▼

Look up the tag by name with GET /public/api/tag-management/tags using nameFilter, then POST /public/api/tags if missing or PUT with the id if present. The filter matches substrings case-insensitively, so compare the returned name exactly before updating.

How do I register external elements like dashboards in Denodo Data Marketplace?▼

External elements are imported, not created: define an interface view in VDP matching the contract from GET /public/api/external-tool-servers/{id}/vql-metadata, then POST to /public/api/external-tool-servers/synchronize. The marketplace reads the view and creates, updates, or deletes elements to match it.

What is the difference between VDP tags and marketplace tags in Denodo?▼

VDP tags are created with CREATE TAG inside Virtual DataPort, while marketplace tags are REST objects created via POST /public/api/tags on the separate Data Marketplace server. They are different objects on different servers, and VDP tags can be imported into the marketplace as read-only mirrors.

Why does the Denodo marketplace API return Session Expired on tag calls?▼

The 500 GENERIC Session Expired error occurs when multiple VDP servers are registered and no serverId is provided. Set marketplace_server_id in the profile from GET /public/api/configuration/servers, or pass --param serverId for a single call.

Why does assigning a tag to a view fail silently in Denodo marketplace?▼

The assignment endpoint returns 200 with a list of ids that were not assigned, so a non-empty response means failure. The usual cause is a view not yet synchronized into the marketplace catalog; run the element-management synchronize calls first, then re-assign.

When should I not use the marketplace REST API for Denodo tagging?▼

Do not use it for VDP tags, which belong to CREATE TAG and ALTER TAG in Virtual DataPort. Also avoid POST /views/{id}/tags when you only want to add one tag, because that endpoint replaces the view's entire tag set.

Related Skills

Explore More Data & Analytics Skills→
api-evangelistapi-evangelist

aggregations

Create, update, delete, and compute column aggregations on Frontline views via CLI.

Official
Basic
MarioDeFelipeMarioDeFelipe
25

Data Product Publisher

Publish and monetize curated data products through Datasphere's Data Sharing Cockpit.

Community
Advanced
prashsubprashsub
1

naming-tagging-standards

Enforce naming conventions, comment formats, and governed tags across data assets.

Community
Advanced
outfitter-devoutfitter-dev
6

claude-plugins

Guide the lifecycle of developing, validating, and distributing Claude Code plugins.

Official
Intermediate