Help Center

Getting Data Out

Catalog data is available outside of Altana through exports and the Altana API. This page covers what you can export, how to get it, and where to find field-level documentation.

Exports from the catalog

From the catalog and value chain views, you can export data on your products, suppliers, transactions, and exposure flags. Exported files include:

  • Products — product names, identifiers, upstream supplier counts, and exposure counts for your value chain networks.
  • Suppliers — supplier names, facility addresses, countries, transaction history, value chain tier, and exposure flags by category.
  • Transactions — the shipment-level records underlying your value chains, including Harmonized System (HS) codes, goods descriptions, port data, and Altana-derived analytical fields.
  • Exposures — a per-product, per-supplier breakdown of exposure flags, risk list details, issuing authorities, and proximity (direct or indirect).

To export, open a catalog view or workspace and use the export control in the toolbar. Exports are delivered as CSV files.

API access

The Altana API gives you programmatic access to catalog data for integration with your own systems, including enterprise resource planning (ERP) platforms, compliance workflows, and internal dashboards. API access is configured through the Integrations settings in your account administration area.

See API Documentation for the API reference, authentication, and credentials, and the Integrations overview for all the ways to connect Altana to your own systems.

Automated integrations

For automated, ongoing data exchange, Altana connects to systems you run outside it — pushing data to endpoints you control and exchanging files over SFTP. These are configured under Settings → Integrations by an account administrator; your implementation team or Technical Account Manager (TAM) can help set one up. Each mechanism has a technical reference:

  • Catalog Subscriptions — receive each product change in a catalog (created, updated, archived) at your endpoint as it happens, so your systems stay current without polling.
  • Webhooks and Event Mapping — receive transaction screening results at your endpoint when a run completes.
  • SFTP File Ingestion — exchange transaction files over SFTP for screening, with results written back.

Field-level reference

For the exact field names, data types, and definitions for every column in the export schema (transactions, products, suppliers, and exposures), see the Catalog Glossary.

Related