Ingestion
APIs, GDS and PNR access, SFTP/FTPS, OBTs, TMCs and other agreed sources.
Connect sources once. Distribute data reliably.
Source connections and data delivery remain separate, so a provider change does not automatically alter your downstream processes. Learn how APIs, file transfers and data contracts work together. Explore external sources and target systems under Integrations.
Clear definition
The integration layer includes connectors, APIs, webhooks, file transfers and documented data products. Defined data contracts govern delivery to Finance, BI, Corporate Security and other target systems, separating their data views from individual source connections.
View the overview of sources and destination systems
NP4
NP4’s role
TD hub and NP4 integration services currently prepare agreed travel data and distribute it through APIs, files and other project-specific methods.
Platform component
Integration is designed as an operating model, not merely an interface.
Mapping & contracts
Fields, formats, permissions, freshness and responsibilities are described unambiguously.
Distribution
Raw or enriched data is delivered to defined consumers on a schedule or by event.
Operations
Error paths, monitoring, versioning, changes and maintenance become part of the integration design.
Typical situations
When this platform component becomes relevant
New TMC, OBT or direct connect
Enterprise data warehouse or Power BI
Provider change with stable downstream interfaces
Customer-specific data formats and destination processes
Relevant product
TD hub prepares data for agreed delivery to your destination systems.
How does this platform component fit your architecture?
In a technical discussion, we review data sources, interfaces, architecture, security and the potential implementation approach.