URN Reference
Resource identifiers in the Ataccama ONE API are Uniform Resource Names (URNs) following RFC 8141. URNs appear in request paths, request bodies, and responses.
For the URN structure, how to obtain URNs, and the keywords that some endpoints accept instead of a URN, see Resource identifiers in the API reference. This page lists the URN format of every resource type, by API.
URN types by API
Catalog and glossary
| Resource | URN format |
|---|---|
Catalog item |
|
Catalog item attribute |
|
Location |
|
Folder |
|
Source |
|
Term |
|
Detection rule |
|
Documentation flow configuration |
|
Data quality
| Resource | URN format |
|---|---|
DQ monitor |
|
DQ dashboard |
|
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 |
|
Data observability
| Resource | URN format |
|---|---|
Alert |
|
Finding |
|
Data observability findings (data-observability:finding) are a different resource type than DQ alert findings (data-quality:dq-finding).
For data observability findings, see the Findings in the API reference.
|
Pipeline monitoring
| Resource | URN format |
|---|---|
Orchestrator |
|
Pipeline job |
|
Dataset |
|
Reference data management
| Resource | URN format |
|---|---|
Table |
|
Draft dataset |
|
Record |
|
Review dataset |
|
Published dataset |
|
Data transformations
| Resource | URN format |
|---|---|
Transformation plan |
|
Processing
| Resource | URN format |
|---|---|
Processing workflow |
|
Processing job |
|
Connection |
|
Other
| Resource | URN format |
|---|---|
Group (IAM) |
|
Groups cannot be listed through the API.
To build a groupUrn, see the Stewardship in the API reference.
Was this page useful?