Downloads

REST API Overview

The REST API is currently in Early Access Preview. The API specification and endpoints might change before being marked as stable.

We recommend testing thoroughly and being prepared to adapt to potential changes in future releases.

The Ataccama ONE REST API provides programmatic access to platform capabilities, enabling you to integrate Ataccama ONE with your applications, automate workflows, and build custom solutions.

What you can do with the API

The REST API provides comprehensive access to Ataccama ONE capabilities:

  • Catalog management: Access and manage catalog items, attributes, assigned terms, folders, sources, and business terms.

  • Stewardship management: Read and change which group is responsible for your data assets.

  • Generic metadata management: Create, read, update, and delete entities of any type defined in the metadata model.

  • Metadata model introspection: Discover the entity types defined in the metadata model and the properties each type supports.

  • Transformation execution: Trigger transformation plans and integrate data processing into your workflows.

  • Reference data lifecycle: Create, update, and delete records in draft, and automate publishing workflows.

  • Data quality automation: Create and manage DQ rules and monitors, run DQ evaluations from your pipelines, retrieve the results and invalid samples, and set up DQ dashboards.

  • Data observability monitoring: Retrieve alerts, their findings, and the observed pipeline jobs and datasets.

  • System integration: Connect Ataccama ONE with your business applications, orchestration tools, and data pipelines.

Get started

Follow these steps to start using the API:

  1. Set up authentication

    Create an API client in the Ataccama Cloud Portal and obtain access tokens. See API Authentication.

  2. Identify your resources

    Find the URNs of the resources you want to work with (for example, table URNs or catalog item URNs). You can list resources through the API or find them in the Ataccama ONE user interface.

  3. Make your first API call

    Start with a simple GET request to list catalog items:

    curl -X GET "https://{your-environment}.ataccama.one/api/catalog/v1/catalog-items" \
      -H "Authorization: Bearer {your-access-token}"
  4. Explore API capabilities

    Review the available APIs to understand what you can automate and integrate.

Available APIs

Catalog Items API

Access and manage catalog items representing your data assets.

  • Catalog Items API: List, filter, retrieve, update, and delete catalog items, create SQL catalog items, and list, retrieve, and update catalog item attributes.

Base URL
https://{your-environment}.ataccama.one/api/catalog/v1

Use cases:

  • Query cataloged data assets programmatically.

  • Update catalog item metadata and descriptions.

  • Filter catalog items by name, source, assigned terms, or attributes.

  • Retrieve which catalog items and attributes are critical data elements.

  • Create SQL catalog items using an SQL query.

  • Integrate catalog data with external data governance tools.

Folders API

Manage the folders that organize SQL catalog items in the workspace of a source.

  • Folders API: List, create, retrieve, update, and delete folders.

Base URL
https://{your-environment}.ataccama.one/api/catalog/v1

Use cases:

  • Prepare the folder structure before creating SQL catalog items through the API.

  • Recreate folders when migrating SQL catalog items from another environment.

  • Browse the folder hierarchy of a source.

Terms API

Manage business and technical terms in your glossary.

  • Terms API: List, create, update, and delete terms with detection rules.

Base URL
https://{your-environment}.ataccama.one/api/catalog/v1

Use cases:

  • Import glossary terms from external systems.

  • Automate term creation and maintenance.

  • Manage detection rules for automated term assignment.

  • Synchronize business glossary across systems.

Term Assignments API

Assign glossary terms to catalog item attributes and control automatic term detection.

  • Term Assignments API: Assign and unassign terms on catalog item attributes in batch, and manage the terms that term detection must not assign.

Base URL
https://{your-environment}.ataccama.one/api/catalog/v1

Use cases:

  • Migrate manually assigned terms from another catalog or a previous Ataccama ONE deployment.

  • Keep assigned terms in sync with an external data governance tool.

  • Prevent term detection from reassigning terms that were deliberately removed.

Sources API

Manage the sources your data assets originate from.

  • Sources API: List, create, retrieve, update, and delete sources.

Base URL
https://{your-environment}.ataccama.one/api/catalog/v1

Use cases:

  • Recreate sources when importing metadata from external systems.

  • Automate source creation during platform migrations.

  • Update source metadata.

Stewardship API

Read and change which group is responsible for your data assets.

  • Stewardship API: Retrieve effective stewardship and assign, transfer, or clear stewardship, for single entities or in batch.

Base URL
https://{your-environment}.ataccama.one/api/catalog/v1

Use cases:

  • Transfer asset ownership between teams, for example, during a reorganization.

  • Assign stewardship in bulk after importing metadata from external systems.

  • Report on asset ownership in external data governance tools.

Generic Metadata Entities API

Create, read, update, and delete entities of any type defined in the metadata model.

Base URL
https://{your-environment}.ataccama.one/api/catalog/v1

Use cases:

  • Create and manage custom entity types defined in your metadata model.

  • Work with built-in entity types that don’t have a dedicated API yet.

  • Perform bulk metadata operations with batch create, update, and delete.

Metadata Model API

Query the metadata model of your environment.

  • Metadata Model API: List entity types and retrieve their definitions, including properties and type hierarchy.

Base URL
https://{your-environment}.ataccama.one/api/catalog/v1

Use cases:

  • Discover the entity types available in your environment, including custom ones.

  • Look up the properties an entity type supports before creating or updating entities through the Generic Metadata Entities API.

  • Check whether an entity type or property is editable or read-only.

Data Quality API

Configure and run data quality end to end: manage DQ rules and monitors, run DQ evaluations, retrieve the results, and set up DQ dashboards.

Guides:

Reference:

Base URL
https://{your-environment}.ataccama.one/api/data-quality/v1

Use cases:

  • Set up DQ rules and monitors for new data sources automatically.

  • Run DQ evaluations from data pipelines and use the results to stop downstream processing when quality thresholds are breached.

  • Retrieve quality results for reporting and dashboards.

  • Access invalid samples for data remediation.

  • Move DQ configuration between environments, for example from development to production.

  • Set up DQ dashboards that aggregate results across DQ monitors.

Data Observability API

Monitor data observability alerts and the findings behind them.

Base URL
https://{your-environment}.ataccama.one/api/data-observability/v1

Use cases:

  • Forward alerts and their findings to ticketing or incident management systems.

  • Drill down from an alert to its findings and identify the affected assets.

  • Build operational dashboards on alerts in your BI tool.

  • Retrieve alerts and findings for compliance or internal audits.

Pipeline Monitoring API

Retrieve the entities observed by pipeline monitoring.

Base URL
https://{your-environment}.ataccama.one/api/pipeline-monitoring/v1

Use cases:

  • Get the details of the pipeline jobs and datasets that data observability findings reference.

  • Map observed datasets to catalog items.

  • Inventory connected orchestrators and observed pipeline jobs.

Transformation Plans API

Trigger execution of data transformation plans.

Base URL
https://{your-environment}.ataccama.one/api/transformations/v1

Use cases:

  • Integrate transformations into external orchestration tools (Airflow, Azure Data Factory).

  • Trigger event-driven data processing.

  • Automate batch data transformation workflows.

  • Coordinate multi-step data pipelines.

Reference Data API

Manage the complete lifecycle of reference data tables.

Base URL
https://{your-environment}.ataccama.one/api/reference-data/v1

Use cases:

  • Read published reference data for downstream systems.

  • Automate reference data updates from external sources.

  • Implement review and approval workflows.

  • Synchronize reference data across environments.

Processing API

Track the asynchronous processing that other APIs start. The Processing API itself does not start any processing.

  • Processing API: Poll workflow state, list and cancel workflows, and inspect their jobs.

Base URL
https://{your-environment}.ataccama.one/api/processing/v1

Use cases:

  • Poll a processing workflow started from another API, such as a DQ evaluation.

  • Cancel a running workflow.

  • Diagnose failed runs from their jobs and error reasons.

Authentication

All API requests are secured with industry-standard security protocols:

  • OAuth 2.0 Bearer Token Authentication: Uses the Client Credentials flow for secure machine-to-machine authentication.

  • TLS Encryption: All API communication is encrypted using TLS 1.2 or higher.

See API Authentication for detailed setup instructions for creating API clients and obtaining access tokens.

Pagination and filtering

List endpoints support cursor-based pagination for efficient handling of large datasets. Results include pagination metadata with prev and next cursors.

Filter endpoints support complex queries with:

  • Attribute-based filtering (string, number, date, Boolean).

  • Logical operators (AND, OR).

  • Comparison operators (such as equals, contains, greater than).

  • Record state filtering (such as NEW, CHANGED, DELETED).

API design

The API follows REST principles with:

  • Standard HTTP methods (GET, POST, DELETE).

  • JSON request and response formats.

  • Meaningful HTTP status codes.

  • Resource-based URLs.

API versioning

The API uses URL-based versioning (for example, /v1/) to ensure backward compatibility. The current version is v1.

When new versions are released:

  • Existing versions remain supported for a minimum period.

  • Breaking changes are introduced only in new versions.

  • You can migrate to new versions at your own pace.

Best practices for using the REST API

  • Reuse access tokens: Access tokens remain valid for a period of time. Reuse them instead of requesting a new token for each API call.

  • Use pagination: When retrieving large datasets, use pagination parameters to fetch data in manageable chunks.

  • Filter at the API level: Use filter parameters to retrieve only the data you need, reducing payload sizes and improving performance.

  • Handle errors gracefully: Implement proper error handling to manage API errors effectively.

OpenAPI specification

Getting help

If you encounter issues or have questions:

  • Check the troubleshooting sections in the API documentation.

  • Review error responses for detailed problem descriptions.

  • Contact Ataccama Support with your environment details and relevant error messages.

See also

Was this page useful?