Added the api version to api docs

Added the api version to api docs

Updated the Client API version from v1.2 to v1.3, so we can use the new features in the v1.3 Client API which are documented here

• Fixed an issue which was preventing some devices from receiving push notifications.
  This issue was temporarily fixed on 26-06-2020 around 19:00, but has now made it's way into an official release.

• Fixed an issue which was preventing some devices from receiving push notifications.
  This issue was temporarily fixed on 26-06-2020 around 19:00, but has now made it's way into an official release.

Fixed an issue where push notifications wouldn't get send to the client's devices.

• Changes for the upcoming change in Chrome's REFERER Header. It's now possible to set your own referer value by using the referer param in the PostMessages api call.
• PostDevices now returns a warning when the account, for which this devices get's registered, has no or not working push settings.
• We now return an error when the API has no connection to the Database. Before we only showed a white screen without any information on it.
• We now support CIDR ip ranges and ipv6 in the IP restriction configuration
• Added the following security headers
  • X-XSS-Protection: 1; mode=block Enables XSS filtering. Rather than sanitizing the page, the browser will prevent rendering of the page if an attack is detected.
  • X-Content-Type-Options: nosniff Prevents MIME-sniffing
  • X-Frame-Options: SAMEORIGIN The page can only be displayed in a frame on the same origin as the page itself
• Added the no_access error to the documentation
• Added the api base url to the documentation

• Added a new param when doing POST /messages calls to the API that contains the full url of the current page. Normally this information is found in the referer header, but Chrome is changing the content of this header to contain only the domain of the website you are on. (the API doesn't do anything with this new param yet, we are working on this)
• Fixed a problem where the focus would not automatically go into the chat when reloading the page
• Fixed a problem where the send button was not showing in the chat conversation screen, even though the inviteNotificationSendButton setting was true (due to the naming of the setting this was expected behaviour, but it wasn't very practical to only allow turning this feature on in the inviteNotification screen)

Added

• The notificationLink setting.

Fixed

• Issue where the same notification would show more than 1x
• Issue where sometimes the client window won't open when clicking on a notification
• Issue in IE11 that prevented the chat from starting (document.contains() doesn't exists in IE11, document.body.contains() does)
• Another issue in IE11; Array.from() doesn't exists so i added the core-js es.array.from module polyfill

Added

• A new global function sendMessage(), which is a rename of sendInitialMessage() since it is not only usable for the initial message. reference
• An optional type param to sendMessage(): reference
• Created a new setting parentNode: reference
  Which can be used to conform to the WCAG rule: https://www.w3.org/TR/WCAG20-TECHS/ARIA11.html

Improved

• Focus will be 'trapped' in all Parley screens untill the chat has been closed/minimized to conform to the WCAG rule: https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-order.html

Fixed

• Fixed color contrasts of elements to conform to the WCAG level AAA guidelines
• Fixed problem where some HTML elements had the same ID

Deprecated

• The sendInitialMessage function since it is now replaced by the sendMessage which is an identical replacement