OPERA Interfaces

Different systems reach OPERA through different interfaces. Door locks, room controls, gateways and PBX systems usually use IFC8 FIAS; restaurant and retail POS use IFC8 XML POS; CRS, CRM and revenue systems exchange business data over OXI; kiosks, websites and apps use OWS/OEDS or HTNG; new projects on OPERA Cloud should start with OHIP.

FIAS

IFC8 FIAS

The main protocol for locks, room control, gateways, PBX and pay-TV systems.

IFC8 XML POS

Guest inquiry and room-charge posting for POS systems.

OXI (OPERA Exchange Interface)

Business data exchange between OPERA and CRS, CRM, revenue and data systems.

OWS / OEDS

SOAP web services for kiosks, websites and apps.

HTNG

Standards-based integration for distribution, CRS and self-service.

OHIP

REST APIs and business events — the default for new OPERA Cloud work.

Your system	Interface	Transport
Door lock / key encoder	IFC8 FIAS	TCP/IP socket (or serial), ASCII records
Room control / energy / BMS	IFC8 FIAS	same
Internet gateway	IFC8 FIAS	same
PBX / call accounting	IFC8 FIAS	same
Restaurant / retail / spa POS	IFC8 XML POS	TCP/IP, XML messages
CRS / CRM / revenue / data warehouse	OXI	XML message exchange
Self-service kiosk / website / app	OWS (OEDS)	SOAP web services
HTNG-compliant distribution & self-service	HTNG	SOAP / XML
New systems on OPERA Cloud	OHIP	REST API + OAuth

FAQ

I build door locks / room controls. Which interface do I need?

Most locks, room controls, gateways, PBX/call accounting and pay-TV systems integrate with OPERA through IFC8 using the FIAS protocol. See IFC8 FIAS.

How do OPERA 5 and OPERA Cloud differ?

IFC8 (FIAS / XML POS) is used on both. OXI and OWS/OEDS are the main integration options on OPERA 5 on-premise; new OPERA Cloud integrations are mostly built on OHIP REST APIs. What you can use depends on the hotel’s version and licences.

Talk to an engineer

Scan with WeChat