Skip to main content
Solved

Accessing Data of Catalog Item via Rest API or GraphQL


Hello everyone,

I’m working on a project that integrates a data masking tool with Ataccama, and I’m encountering some issues when trying to retrieve actual catalog item data (the row-level data) via the REST API. I’ve been testing both GraphQL and REST approaches, and here’s what I’ve found so far:

GraphQL vs. REST for Data Retrieval:
The GraphQL API appears to focus on metadata – attributes, versioning, policies, etc. However, based on my understanding, the actual table data (the rows and cells) isn’t available through GraphQL; it’s only accessible via a REST endpoint. Based on available documentation for MDM and RDM REST APIs, the REST endpoints follow a pattern using a fixed base path (/api/rest) on the default port (8051) and use basic HTTP authentication.

Endpoint URL Confusion:
Initially, I attempted to use an endpoint like:
  https://teranet.test.ataccama.online/catalog/data/catalogItem/<gid>/data
which returned a 404 error. Later, based on the docs, I switched to the documented REST API base URL:
  https://teranet.test.ataccama.online:8051/api/rest/
But then my Python script timed out when connecting to that URL.

Has anyone faced similar issues when trying to access actual catalog item data via the REST API? How do you determine the correct endpoint URL for your environment? Any other suggestions on how I can fetch the actual data from the data tab of a catalog item?

 

Thanks,

Karine

Best answer by anna.spakova

Hi,

just to add to ​@OGordon100 comment, there is a way through ONE Desktop to actually retrieve the data - there is a step called Catalog Item Reader that can access the actual data but it requires that the plan in the ONE Desktop is run remotely on the DPE that has access to the data source - that is achieved by changing the environment in the ONE Desktop tool. See more details: https://docs.ataccama.com/one-desktop/latest/work-with-ataccama-one/work-with-data.html#read-data-using-catalog-item-reader

Kind regards,

Anna

 

View original

OGordon100
Ataccamer
Forum|alt.badge.img

Hi Karine,

MDM (and RDM) are products in which Ataccama physically stores data, as they are designed to effectively be systems of record.

But by very deliberate design, DQ&C does not hold data; only metadata. (For many customers, this is part of Hybrid Processing, in which we process your data in your cloud, and then send only the results back to the central Ataccama platform). The only time in which data can be retrieved is during the Post-Processing phase of a Monitoring Project (or when Invalid result Samples are deliberately configured to be retained).

As such, because we do not hold data in ONE DQ&C, we therefore have no Rest API in DQ&C to access data in ONE DQ&C. 

(And as an aside - GraphQL is an API spec designed around parsing highly nested information - such as our Metadata Model - so it is not an appropriate tool for tabular data access in general!) 

But for Data Masking - I’d suggest having a look at our Data Protection Classification feature.

Hope this clears things up!

Oliver


anna.spakova
Ataccamer
Forum|alt.badge.img+3

Hi,

just to add to ​@OGordon100 comment, there is a way through ONE Desktop to actually retrieve the data - there is a step called Catalog Item Reader that can access the actual data but it requires that the plan in the ONE Desktop is run remotely on the DPE that has access to the data source - that is achieved by changing the environment in the ONE Desktop tool. See more details: https://docs.ataccama.com/one-desktop/latest/work-with-ataccama-one/work-with-data.html#read-data-using-catalog-item-reader

Kind regards,

Anna

 


Cansu
Community Manager
Forum|alt.badge.img+3
  • Community Manager
  • April 1, 2025

Hi ​@karine.davtyan, does any of the solutions shared above help you with your question? If yes, could you please mark it as a best answer 🙋🏻‍♀️


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings