...
protel uses protel I/O to route incoming and outbound data messages. Messages can be delivered to protel I/O from an HTTPS endpoint or via a Websocket. protel I/O provides different endpoints for synchronous and asynchronous SOAP 1.2 messages to accommodate WSDL requirements.
Systems send messages to protel I/O using HTTP endpoints.
In addition, protel I/O requires some information in the message header.
Security, Access, + Authentication
Security is important to you and protel. All messages must be authenticated using protel IO’s secure authentication processes. To ensure the source of messages are valid, all messages flowing to and from protel are checked.
Messages are verified by protel I/O
Who can send messages
What messages they can send
Where they can send to and receive from
Access to the API is only permitted through SSL (secure sockets layer).
For HTNG messaging, all messages will utilize the HTNG 2.1 SOAP header.
Authentication of Inbound messages
Direction Vendor to protel. All messages require a protel provided Bearer Token (whether RQ or RS!). The Authentication token can be submitted in HTTP headers and SOAP headers. If the token can be found in more than one of these places, the SOAP header has the higher priority than the HTTP header. The place with the highest priority that has the token set determines which is used and which is ignored.
Protel will provide you with your bearer token at the time we commence testing. When requesting a test environment protel will provide you with a token at that time.
protel Access Token
For API access, each service connecting to a hotel will have it’s own access token.
| Codeblock | ||||
|---|---|---|---|---|
| ||||
Authorization: Bearer <HOTEL_TOKEN> |
Authentication is specific in each case and requires partner applications to provide this access token with each API request message. This access token is provided by protel. protel authenticates this access token before allowing any actions to be taken
.
Format of Headers
You must send HTTP headers. There are 2 mandatory HTTP header parameters
...