Integrasi

Interfaces: booking-engine & rate mapping

One instance per external system, with its own pull and push rate-code mapping and its own country/currency vocabulary — the booking engine is the first one wired up.

Terakhir diperbarui

Who this is for: requires integration.mapping.manage to create or edit an interface instance and its mappings. Where: Integrations → Interfaces

An interface is one external system Nerve exchanges data with — the direct booking engine today, and the same shape a future channel-manager-style interface would reuse. Select New interface to register one, or open an existing row for Interface Details.

Configuration#

A Name, an Interface kind (e.g. Booking engine), an optional Vendor code and Endpoint URL for the external system, and an Active toggle.

Pull Rate Mapping#

An inbound rate code from the external system has to resolve to a Nerve rate plan before a booking it carries can be understood. Each row is external code → internal rate plan (e.g. RATE-BAR → Best Available Rate). New mapping adds one.

Catatan

Unlike the cashless-payment method mapping and e-procurement supplier mapping elsewhere in Settings, this screen does not currently surface a dedicated "unmapped codes seen so far" queue — an inbound code with no mapping simply fails to resolve, without a list an operator can work from here. Resolving one today means knowing the external code in advance and adding the mapping proactively, or diagnosing a failed resolution from elsewhere (logs, the sending system) rather than from this screen.

Push Rate Mapping#

The outbound direction: which external code Nerve publishes a given internal rate plan under. Same shape, reversed — internal rate plan → external code. A rate plan with no push mapping is a gap in what you publish, not a wrong price, since nothing is sent for it until one exists.

Country & Currency#

External systems carry their own country and currency vocabularies. Each row is one mapping — tagged Country or Currency — from the external system's code to the Nerve/ISO value it means (e.g. IDR-STD → IDR). New mapping adds one; both directions (ingest and publish) resolve through the same table.

What's next#