Service Integration
Every push or pull through a web service writes ArtifactExported or ArtifactImported to the ledger, stamped with the source ULID. ETL platforms downstream can prove which Magellan version their generated code was derived from.
Magellan can push mapping relationships to external web services or pull them in from external systems using standardized formats.
This enables automated code generation: your ETL or data integration platform can consume Magellan's mapping metadata and generate transformation code automatically.
Standardized export formats ensure compatibility with a wide range of integration platforms and custom tooling.
Every export writes an `ArtifactExported` entry carrying the mapping ULID, the artifact format, the consumer identifier, and a sha256 of the emitted bytes. Bidirectional ingest writes `ArtifactImported` with the same fields. The downstream ETL pipeline can prove provenance by referencing the ledger ULID.
Bidirectional integration means Magellan can also ingest mappings created or modified externally, keeping it as the single source of truth for mapping metadata.
Audit ledger entries written by this feature
Each action in this feature appends one of the following entry types to the ULID‑keyed, SHA‑256 hash‑chained audit ledger. A reviewer can replay the chain to reconstruct exactly what happened, when, and under which role.
ArtifactExportedArtifactImportedServiceCalledRelated glossary terms
Definitions for the technical, regulatory, and standards terms referenced on this page. Each link opens the term in the full glossary.
Open the full glossary