Ellipse Gradient for Header

Collibra Integration Guide

Connect Collibra’s data governance and metadata model with enterprise platforms through REST APIs, selected webhook notifications, and controlled import workflows.

Collibra integration options at a glance

Collibra’s primary integration surface is its authenticated REST API for searching, creating, and updating Communities, Domains, Assets, Attributes, Relations, and Responsibilities. Selected Collibra events can produce webhook-style notifications, although coverage depends on the tenant and product capability. Import and bulk-processing features can support controlled metadata loads, while file-oriented import scenarios vary by feature and deployment. Martini can consume Collibra REST APIs, expose endpoints for supported notifications, schedule reconciliation workflows, transform JSON payloads, and coordinate validation, batching, retries, and downstream updates. OAuth 2.0, Basic authentication, or API credentials should be confirmed for the target Collibra environment.

Integration pointSupported by Collibra?Common use casesHow Martini supports it
REST APIsYesSearch, create, and update Communities, Domains, Assets, Attributes, Relations, Responsibilities, and governance metadata.Martini can consume Collibra REST endpoints from workflows, map request and response payloads, apply business rules, and expose APIs for downstream consumers.
Webhooks / outbound callbacksLimitedReceive notifications for selected Collibra events and integration scenarios where webhook coverage is enabled.Martini can expose an inbound API or webhook-triggered workflow to validate, normalize, deduplicate, and process supported notifications.
Bulk / async / batch APIsLimitedLoad or update multiple metadata objects through supported import and bulk-processing capabilities.Martini can partition payloads, submit controlled batches, track results or jobs where available, and separate retryable failures from data-quality errors.
File / attachment APIsLimitedSupport selected file-oriented metadata import and loading scenarios; formats and behavior vary by feature and deployment.Martini can transform structured files and invoke documented Collibra import mechanisms, but a universal attachment API should not be assumed.
AuthenticationYesAuthenticate API users or service accounts using tenant-supported OAuth 2.0, Basic authentication, or API credentials.Martini can store environment-specific secrets, configure authenticated REST requests, and apply secure credential handling and token renewal patterns.
GraphQL APIsNot confirmedNo generally documented Collibra GraphQL API was confirmed for new integrations.Martini can consume GraphQL when a separate confirmed endpoint exists, but Collibra integrations should use REST unless the target environment documents otherwise.
SOAP APIsNot confirmedNo current, generally recommended Collibra SOAP API was confirmed.Martini supports SOAP generally, but a Collibra SOAP integration should not be designed without a tenant-specific documented interface.
Database accessNoDirect access to Collibra’s internal database is not the recommended Cloud integration approach.Martini should use supported Collibra APIs and documented import or export mechanisms rather than querying internal platform databases.

How Collibra exposes data and business events

Collibra REST APIs

Collibra’s REST API is the principal programmatic integration surface for governance and metadata objects. It supports searches and operations involving Communities, Domains, Assets, Attributes, Relations, Responsibilities, and related configuration, subject to API version and tenant permissions.

Martini implementation pattern

Martini implementation pattern: a workflow authenticates to the target Collibra environment, retrieves paginated resources, maps them to a canonical model, applies governance rules, and writes changes to downstream systems or back to Collibra. Stable identifiers and permission-aware error handling make the process repeatable.

Implementation sequence

Authenticate with the configured Collibra API user or service account
Retrieve the required resources and continue through all result pages
Normalize Collibra objects into the integration model
Apply ownership, vocabulary, and authority rules
Create or update dependent objects in the required order
Record results, errors, and replay checkpoints

Collibra Webhooks

Collibra supports webhook-style notifications for selected events and integration scenarios. Notifications are not necessarily available for every object or lifecycle event, so event coverage, delivery behavior, and authentication must be verified for the target tenant.

Martini implementation pattern

Martini implementation pattern: expose an authenticated Martini API endpoint, validate and record the notification, retrieve the current Collibra resource when necessary, and invoke downstream workflows. Scheduled reconciliation provides consistency when notifications are incomplete or missed.

Implementation sequence

Receive the Collibra notification at a Martini API endpoint
Validate authentication, structure, and any available event identifier
Deduplicate the notification and acknowledge it promptly
Retrieve the current Collibra object when the payload is incomplete
Map the event to downstream actions and apply business rules
Run scheduled reconciliation for unsupported or missed events

Collibra bulk and import processing

Collibra provides import and bulk-processing capabilities for selected metadata and governance scenarios. Supported object types, payload limits, synchronous or asynchronous behavior, and partial-failure semantics depend on the specific capability and deployment.

Martini implementation pattern

Martini implementation pattern: construct validated batches, submit them through the documented Collibra interface, capture per-record or job results, and retry only safe failures. The workflow maintains source keys so successful records are not duplicated during replay.

Implementation sequence

Validate source objects and required Collibra vocabulary
Order Communities, Domains, Assets, Attributes, Relations, and Responsibilities
Partition the data into bounded batches
Submit each batch through the documented import or bulk interface
Retrieve job or result status when the operation is asynchronous
Store successes and isolate invalid or retryable records

Collibra file-oriented imports

Collibra can support file-oriented metadata loading and import scenarios, but a general-purpose attachment API should not be assumed. Formats and availability vary by feature and deployment.

Martini implementation pattern

Martini implementation pattern: receive or generate a supported structured file, validate its content, transform fields into the required Collibra import shape, and submit it through the documented process. Martini records the source file, outcome, and rejected rows for reconciliation.

Implementation sequence

Receive or generate the supported metadata file
Validate required columns, identifiers, and vocabulary values
Transform the file into the documented Collibra import format
Submit the import and capture its processing result
Reconcile rejected rows and retry only corrected data
Record the import outcome for operational reporting

Common Collibra integration patterns

Pattern 1: Synchronize data platform metadata to Collibra

When to use this pattern

Use this pattern when Snowflake, Databricks, or another data platform is the source of technical metadata and Collibra is the governance system of record for definitions, stewardship, and certification. A scheduled workflow provides complete reconciliation even when event coverage is limited.

Integration direction
Snowflake
Martini
Collibra
Example Mapping
Collibra FieldCanonical FieldTarget Field
databaseNamesource.databaseAsset.communityOrDomain
tableNameasset.qualifiedNameAsset.name
columnDescriptionmetadata.descriptionAttribute.description
ownersteward.ownerResponsibility.assignee
Martini implementation pattern

Martini schedules metadata retrieval, paginates through source objects, resolves existing Collibra Assets using stable identifiers, and creates or updates Communities, Domains, Assets, Attributes, and Relations in dependency order. Validation failures are isolated, throttled requests are retried with backoff, and the workflow records reconciliation results.

Martini capabilities used
  • workflows
  • scheduling
  • API consumption
  • data mapping
  • business rules
  • error handling

Pattern 2: Send Collibra governance status to ServiceNow

When to use this pattern

Use this pattern when approved, deprecated, ownerless, or policy-related Collibra status should create operational work. It supports event-driven processing where the relevant notification is available and scheduled polling where complete status coverage is required.

Integration direction
Collibra
Martini
ServiceNow
Example Mapping
Collibra FieldCanonical FieldTarget Field
assetIdgovernance.assetIdu_collibra_asset_id
assetStatusgovernance.statusstate
responsibilityOwnergovernance.ownerassignment_group
policyIssuegovernance.issueshort_description
Martini implementation pattern

Martini receives a supported notification or retrieves status on a schedule, enriches incomplete events through the Collibra REST API, applies rules for task creation and duplicate detection, and submits a ServiceNow task. Responses and task identifiers are stored for status reconciliation; transient failures are retried safely.

Martini capabilities used
  • API exposure
  • webhook consumption
  • workflow orchestration
  • data mapping
  • business rules
  • error handling

Pattern 3: Load a business glossary in controlled batches

When to use this pattern

Use this pattern when an upstream glossary or catalog produces many terms and definitions that must be loaded into Collibra through supported import or bulk-processing capabilities. It is useful for migrations and recurring controlled loads.

Integration direction
Business glossary source
Martini
Collibra
Example Mapping
Collibra FieldCanonical FieldTarget Field
termIdglossary.externalKeyAsset.externalIdentifier
termNameglossary.nameAsset.name
definitionglossary.definitionAttribute.definition
businessOwnerglossary.ownerResponsibility.assignee
Martini implementation pattern

Martini validates and transforms source terms, detects duplicates using external keys, partitions submissions into bounded batches, and invokes the documented Collibra import or bulk interface. Per-record results are preserved so invalid terms can be corrected without replaying successful records.

Martini capabilities used
  • workflows
  • file and JSON processing
  • data mapping
  • validation
  • batch orchestration
  • error handling

Pattern 4: Reconcile Collibra events with scheduled polling

When to use this pattern

Use this pattern when webhook coverage is selected rather than universal, or when the integration must detect missed notifications and unsupported lifecycle changes. Event processing provides responsiveness while scheduled reconciliation establishes completeness.

Integration direction
Collibra
Martini
Operational system
Example Mapping
Collibra FieldCanonical FieldTarget Field
eventTypechange.typeworkflow.route
assetIdchange.objectIdtarget.externalId
lastModifiedchange.timestamptarget.updatedAt
statusgovernance.statustarget.status
Martini implementation pattern

Martini processes supported notifications immediately, stores event identifiers and checkpoints, and runs a scheduled search for changes since the last successful window. Idempotent upserts, comparison rules, and bounded retries prevent duplicates while allowing missed changes to be recovered.

Martini capabilities used
  • webhook consumption
  • scheduling
  • API consumption
  • checkpointing
  • data mapping
  • retry handling

Applications commonly integrated with Collibra

Collibra commonly participates in metadata, governance, catalog, and stewardship architectures. The applications below represent realistic integration targets; exact capabilities and object-level support should be confirmed for the Collibra edition and tenant configuration.

Application Scenario Direction Martini Pattern
Snowflake Synchronize databases, schemas, tables, columns, ownership, and classification metadata into Collibra. Snowflake → Martini → Collibra Schedule metadata retrieval from Snowflake, map technical structures to Collibra Assets, Attributes, and Relations, resolve existing objects using stable identifiers, and log rejected records for reconciliation.
Databricks Catalog lakehouse objects, schemas, data products, and governance metadata in Collibra. Databricks → Martini → Collibra Consume Databricks metadata APIs, normalize schemas and ownership data, apply environment-specific vocabulary rules, and submit ordered Collibra updates with controlled retries.
Tableau Connect reports, dashboards, and usage context with governed Collibra Assets and ownership information. Tableau → Martini → Collibra Retrieve Tableau metadata, match reports and data sources to Collibra Assets, transform ownership and lineage attributes, and route unmatched items for review.
Microsoft Power BI Relate reports and semantic models to governed data definitions, owners, and classifications. Microsoft Power BI → Martini → Collibra Retrieve Power BI metadata, map reports and models to Collibra objects, enforce deterministic matching rules, and reconcile changes on a schedule.
ServiceNow Create governance or remediation tasks from Collibra ownership, policy, certification, or data-quality issues. Collibra → Martini → ServiceNow Receive a supported Collibra notification or poll governance status, map the issue to a ServiceNow task, preserve Collibra identifiers, and optionally return task status to Collibra.
Salesforce Synchronize business definitions, customer-data ownership, and governance metadata associated with Salesforce data. Salesforce → Martini → Collibra Retrieve selected Salesforce metadata, map source identifiers and ownership into Collibra Assets and Attributes, and apply authority rules so governance fields are not overwritten incorrectly.
Alation Coordinate catalog metadata, glossary information, and governance ownership between data intelligence platforms. Alation → Martini → Collibra Exchange selected catalog and glossary objects through APIs, normalize vocabulary, prevent duplicate Assets with external keys, and route conflicts to an explicit system-of-record workflow.

How to build a Collibra integration in Martini

Objective

Establish authenticated access to the target Collibra environment and configure tenant-specific endpoint, API version, permissions, and secrets.

Instructions in Martini

  • Confirm the Collibra base URL, API version, and supported authentication method
  • Create a least-privilege API user or service account
  • Store credentials and tokens in Martini environment-specific secrets
  • Configure OAuth renewal or credential rotation according to the tenant policy

Objective

Select the trigger that matches completeness and latency requirements: supported Collibra notifications for selected changes, or scheduled retrieval for reconciliation and full synchronization.

Instructions in Martini

  • Verify that the required Collibra event is supported before choosing webhooks
  • Expose a Martini API endpoint for supported notifications
  • Configure a scheduler for polling, reconciliation, or batch imports
  • Use both event processing and scheduled reconciliation when completeness matters

Objective

Retrieve current Collibra objects or source metadata and account for pagination, permissions, and incomplete event payloads.

Instructions in Martini

  • Call the documented Collibra REST endpoints
  • Continue through paginated search and listing responses
  • Retrieve the current resource when a notification contains only an identifier
  • Record source identifiers and checkpoints for repeatable processing

Objective

Coordinate dependencies and business decisions in a Martini workflow rather than embedding integration logic in isolated scripts.

Instructions in Martini

  • Create workflow stages for Communities and Domains before dependent Assets
  • Process Attributes, Relations, and Responsibilities after their dependencies exist
  • Route records by object type, status, and authority rules
  • Use reusable workflow logic for common lookup and error behavior

Objective

Transform Collibra objects and source metadata into a canonical model while validating identifiers, vocabulary, required fields, and ownership rules.

Instructions in Martini

  • Map source fields to Collibra Assets, Attributes, Relations, and Responsibilities
  • Use stable external identifiers or qualified names for matching
  • Validate custom asset types, attribute types, relation types, and statuses
  • Separate invalid data-quality failures from transient API failures

Objective

Create or update Collibra objects and downstream records idempotently, then preserve outcomes for monitoring and replay.

Instructions in Martini

  • Search before creating to prevent duplicate Assets
  • Apply bounded concurrency and backoff for throttling responses
  • Capture per-record or bulk-job results
  • Retry safe failures without duplicating successful updates
  • Run reconciliation for missed events and incomplete batches

Common Collibra data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
CommunitiesRepresent top-level organizational or governance containers.Data catalogs, data platforms, reporting systems, governance repositoriesMartini retrieves or resolves Communities before creating dependent Domains and Assets, using environment-specific identifiers and permissions.
DomainsOrganize Assets and governance content within Communities.Data catalogs, metadata platforms, governance applicationsMartini maps source ownership and vocabulary to Domains, checks for existing objects, and creates or updates them before dependent metadata.
AssetsRepresent cataloged data sets, reports, applications, processes, policies, and glossary terms.Snowflake, Databricks, Tableau, Power BI, ServiceNow, reporting platformsMartini searches by stable source identifiers or qualified names, then creates or updates Assets idempotently.
AttributesStore descriptions, classifications, owners, statuses, and business definitions associated with Assets.Data platforms, catalogs, governance and reporting systemsMartini transforms source fields into Collibra Attribute values and applies authority rules to prevent inappropriate overwrites.
RelationsExpress typed relationships such as contains, is related to, or is derived from.Catalogs, lineage platforms, data discovery toolsMartini creates Relations after participating Assets exist, validates endpoints, and records partial failures for replay.
ResponsibilitiesAssign users or groups to governance roles for Assets and other Collibra resources.Identity directories, ServiceNow, stewardship and governance applicationsMartini maps source owners or groups to Collibra responsibilities, validates permissions, and reconciles changes without duplicating assignments.

Authentication and security considerations

Authenticated API access

Collibra integrations use authenticated requests to a specific Collibra environment. OAuth 2.0 bearer tokens, Basic authentication, or API credentials may be available depending on the deployment, API version, and tenant policy.

Authorization

Authentication does not grant unrestricted access. Collibra roles and permissions determine which Communities, Domains, Assets, Attributes, Relations, Responsibilities, and operations an API user can access.

Martini security controls

  • Store Collibra credentials and environment-specific values in Martini secrets.
  • Use least-privilege service accounts for each integration purpose.
  • Use HTTPS/TLS for API communication.
  • Refresh or renew OAuth tokens according to the selected flow and token lifetime.
  • Do not place credentials in workflow payloads, source code, or logs.

Operational considerations for Collibra integrations

Pagination and throttling

Assume search and listing endpoints may be paginated. Use bounded concurrency, request pacing, retry delays, and backoff for throttling responses.

Idempotency and ordering

Use stable identifiers, external keys, or qualified names to locate existing Assets before creation. Process Communities and Domains before Assets, then Attributes, Relations, and Responsibilities.

Partial failures

Bulk imports may contain both valid and invalid records. Preserve per-record or job results, separate retryable failures from data-quality errors, and support replay without duplicating successful updates.

Webhooks and reconciliation

Webhook coverage may be limited and notifications may be incomplete. Validate and deduplicate events, acknowledge promptly, and use scheduled reconciliation to recover missed or unsupported changes.

Versioning and testing

Confirm the target API version, endpoint behavior, custom vocabulary, permissions, and authentication model before implementation. Test representative object types, pagination, rate limiting, schema changes, and duplicate delivery.

Why use Martini instead of scripts or point-to-point integrations?

Orchestration instead of isolated scripts

Martini provides a maintainable workflow for authentication, pagination, dependency ordering, mapping, validation, business rules, and downstream writes. This keeps Collibra integration behavior visible and reusable.

Reliable synchronization

Scheduled workflows, supported webhook endpoints, checkpoints, retries, and reconciliation can combine responsiveness with completeness when Collibra notifications cover only selected events.

Controlled change management

Environment-specific secrets, reusable mappings, explicit authority rules, and centralized error handling reduce the operational risk of point-to-point integrations and make tenant-specific configuration easier to manage.

API-led reuse

Martini can expose a controlled API façade for downstream applications while keeping Collibra authentication, object lookup, transformation, and governance rules behind reusable workflows.

Frequently asked questions

How can Collibra be integrated with enterprise systems?

Collibra is primarily integrated through its authenticated REST API for Communities, Domains, Assets, Attributes, Relations, Responsibilities, and governance metadata. Selected events can produce webhook-style notifications, and import or bulk-processing capabilities can support controlled metadata loads. The exact methods depend on the Collibra edition, API version, and tenant configuration.

Can Martini integrate with Collibra?

Yes. Martini can consume Collibra REST APIs, receive supported webhook-style notifications through a Martini API, orchestrate scheduled synchronization, and transform data for import or bulk-processing workflows. A dedicated native Martini Collibra connector is not documented in the supplied materials.

Do I need a connector to integrate Collibra with Martini?

No. A dedicated Collibra connector is not required. Martini can use Collibra’s confirmed native integration mechanisms, including REST APIs, selected webhook notifications, authenticated requests, and documented import or bulk-processing interfaces.

Is there any extra Lonti cost to integrate Collibra with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Collibra. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Collibra, cloud infrastructure, or other third-party systems depending on subscription, usage, and deployment model.

Which Collibra integration methods should new projects use?

REST APIs should be the default because they are Collibra’s principal documented integration surface. Use selected webhook-style notifications when the required event is supported, and use import or bulk-processing capabilities for appropriate larger loads. GraphQL and SOAP were not confirmed as current recommended Collibra methods.

Are Collibra events and webhooks available?

Collibra supports webhook-style notifications for selected events and integration scenarios, but coverage is not universal for every object or lifecycle event. Verify event types, delivery behavior, authentication, and retry expectations for the target tenant, and use scheduled reconciliation where completeness is required.

How should Collibra synchronization and data mapping work?

Martini can paginate Collibra searches, map source data to Communities, Domains, Assets, Attributes, Relations, and Responsibilities, and apply explicit authority and vocabulary rules. Stable external identifiers or qualified names should be used for idempotent matching, with dependency ordering and reconciliation for partial failures.

How does Martini handle Collibra errors, retries, and duplicates?

Martini workflows can distinguish validation failures from transient API errors, apply bounded retries and backoff, record per-record or bulk-job results, and preserve checkpoints for replay. Duplicate prevention should use stable source identifiers, external keys, or qualified names rather than display names alone.

Related Martini documentation

APIs

Workflows

Data

Security

Operations

Connect Collibra with Martini

Use Martini to build governed Collibra integrations around REST APIs, selected webhook notifications, scheduled reconciliation, and controlled metadata processing.

EXPLORE MARTINI
BOOK A DEMO