URN Reference
Resource identifiers in the Ataccama ONE Agentic Public API are Uniform Resource Names (URNs) following RFC 8141. URNs appear in request paths, request bodies, and responses.
URN structure
All URNs share the same structure:
urn:ata:{tenant}:{realm}:{resource-type}:{uuid}
-
urn:ata: Fixed prefix, consisting of theurnscheme and theata(Ataccama) namespace. -
{tenant}: Your tenant identifier, taken from the authentication context (lowercase letters, digits, and hyphens). -
{realm}: The API area the resource belongs to, such ascatalogordata-quality. -
{resource-type}: The type of resource, such ascatalog-itemordq-monitor. -
{uuid}: The unique identifier of the resource, a UUID.
urn:ata:acme-corp:data-quality:dq-monitor:123e4567-e89b-12d3-a456-426614174000
How to obtain URNs
URNs are returned by the API itself: list and create endpoints return the URNs of the resources they list or create. Save the URN from the response when you create a resource, and use it in subsequent requests.
Where a URN appears depends on the resource:
-
Resources created in the web application appear in list results like any other resource.
-
Sub-entities, such as rule input attributes or rule instances, have no list endpoints of their own: their URNs are returned inside the parent resource’s detail response.
-
DQ dimensions and their dimension results can be listed via
GET /data-quality/v1/dq-dimensions(see List DQ dimensions). -
DQ transformations can be listed via
GET /data-quality/v1/dq-transformations(see List DQ transformations). -
Groups, referenced as
groupUrnin a rule’s stewardship assignment, are managed in the web application and cannot be listed through the API.To build a
groupUrnfrom the UUID shown in the web application, see Match rules and monitors between environments.
Special values
Some endpoints accept a literal keyword instead of a URN:
-
primaryinstead of a DQ monitor URN resolves to the primary DQ monitor of the catalog item. -
latestinstead of a processing URN resolves to the most recent DQ processing for the DQ monitor.
Endpoints that support these keywords state so in their documentation.
URN types by API
Catalog and Glossary
| Resource | URN format |
|---|---|
Catalog item |
|
Catalog item attribute |
|
Source |
|
Term |
|
Detection rule |
|
Documentation flow configuration |
|
Data Quality
| Resource | URN format |
|---|---|
DQ monitor |
|
Processing (DQ monitor run) |
|
Rule |
|
Rule instance |
|
Rule attribute |
|
Rule parameter |
|
Rule input group |
|
Rule variable |
|
Dimension |
|
Dimension result |
|
Explanation |
|
DQ threshold |
|
DQ alert finding |
|
DQ transformation |
|
Reference Data Management
| Resource | URN format |
|---|---|
Table |
|
Draft dataset |
|
Record |
|
Review dataset |
|
Published dataset |
|
Was this page useful?