The Data Catalog provides a stateless REST API to perform programmatically all the tasks explained in this guide.
The documentation of this REST API is available on
Data Catalog 7.0 provided a REST API to perform the following tasks:
Synchronize with Virtual DataPort
Compute the usage statistics
This REST API of Data Catalog 7.0 is kept for backward compatibility, but it is deprecated. You should consider migrate to the REST API of Data Catalog 8.0.
You will find the REST API of Data Catalog 7.0 documented in the entries that
Most of the endpoints in the REST API require authentication, so you must provide your credentials on every request. The REST API supports the HTTP Basic Authentication method. Follow these steps to provide your credentials:
Build the user-pass by concatenating the user-id, a single colon character (
:) and the password.
Encode the user-pass using Base64 into a sequence of US-ASCII characters.
Build a header with the name
Authorizationand the value
The following example retrieves the information of the new home page of the
Data Catalog authenticating with the user
admin and the password
curl --location --request GET 'http://localhost:9090/denodo-data-catalog/public/api/home' --header 'Authorization: Basic YWRtaW46YWRtaW4='
If you have registered several Virtual DataPort servers in the Data Catalog, you
must specify which one you want to connect to. Use the query parameter
serverId with the internal identifier of the server as a value.
You can obtain the internal identifiers of the Virtual DataPort
servers registered in Data Catalog with the following endpoint of the REST
In order to access the REST API of the Data Catalog from a cross-site environment, you must configure the Denodo Platform as follows:
Do the steps of the section Initial Set-Up of CORS (you have done this already if you published a Denodo REST web service with CORS enabled).
Before starting any server of this Denodo installation, edit the file
<DENODO_HOME>/resources/apache-tomcat/conf/context.xmland change the default policy for the
SameSitecookies to this:
<CookieProcessor sameSiteCookies="none" />