DAM developer API reference
Use DAM REST APIs to integrate enterprise portals, development platforms, catalogs, quality operations, and AI applications. Begin with read-only discovery, definitions, and governance status before adding updates, approvals, or execution.
This guide selects interfaces by business object and scenario. Test endpoints, telemetry, icons, cache operations, service restarts, internal synchronization, permission bypasses, and legacy compatibility endpoints are not recommended integration entry points. Inclusion does not constitute an independent public API stability commitment.
Start with a task
| Goal | Guide | Outcome |
|---|---|---|
| Explain tables and fields in a portal | Conventions, metadata | Definitions traceable to systems and standards |
| Synchronize standards and reference values | Standards and metrics | Versioned definitions and reference code snapshots |
| Integrate quality dashboards or tickets | Quality and jobs | Rules, runs, issues, and verification |
| Display catalogs and ownership | Assets and security | Authorized assets and classification information |
| Assess changes before release | Lineage and graphs | Dependencies, transformations, impact |
| Combine multiple services | Integration scenarios | Call sequence, identity mappings, validation |
API base URLs
Combine the deployment entry point with the correct service prefix. For example: https://dam.example.com/metadata/entities/123/get.
| Variable | Example base URL | Responsibility |
|---|---|---|
BASE_BASE_URL | https://<host>/base | Systems, tags, shared services |
METADATA_BASE_URL | https://<host>/metadata | Sources, tables, fields, reports, metamodels |
DOMAIN_BASE_URL | https://<host>/domain | Standards, reference codes, metrics |
QUALITY_BASE_URL | https://<host>/quality | Rules, validation tasks, issues |
ASSETS_BASE_URL | https://<host>/assets | Catalogs and asset details |
DATASECURITY_BASE_URL | https://<host>/datasecurity | Classification, discovery, policies |
SQLINK_BASE_URL | https://<host>/sqlink | Lineage, parsing, impact |
GRAPH_BASE_URL | https://<host>/graph | Cross-object relationships and asset access |
JOB_BASE_URL | https://<host>/job | Scheduling and execution records |
USER_BASE_URL | https://<host>/user | Users, organizations, credentials |
Versions and compatibility
The baseline is the current documented release. A service's info.version alone does not identify the product release. Availability depends on deployed Swagger/OpenAPI and permissions. Archive definitions, service build identifiers, and integration records.
Graph v2 and unified asset access are deployment-dependent capabilities. Confirm availability before including them. Before upgrades, compare methods, paths, schemas, permissions, and enums, then regress representative scenarios. Similar screens do not establish API compatibility.
Examples use fictional hosts and IDs and configured authentication variables. Tables list key parameters; the customer deployment's Swagger defines the complete contract.
Implementation sequence
- Create a dedicated integration identity with necessary domain and module access.
- Confirm entry point, credentials, and validity through request conventions.
- Query a small sample and record IDs, pagination, and response structures.
- Combine services using scenarios and compare with DAM pages.
- Assign incremental synchronization, retries, access changes, and upgrade regression ownership before expanding.
Governance REST APIs query or manage governance objects. Data Services publishes approved business data APIs. Reading a definition does not authorize access to the underlying data.