Getting Started with Wexer

This documentation hub will help you get started with Wexer's range of integration options.

Partnering with Wexer

Wexer is a globally recognised leading provider of wellness content. We serve thousands of customers globally, through on-premise hardware and software solutions, through to web, mobile app and content API integrations with many of the leading brands in the sector.

This documentation explains the ways you can partner with us, enabling you to deliver your and our content to your users quickly and easily.


Content API

Rapidly build a platform to platform integration with Wexer. We provide the content delivery (CDN), streaming tech, content management and all the APIs you need to build an end user experience with minimal cost and hassle. You can take the Wexer library of thousands of titles across the full spectrum of wellness content categories, use our platform to deliver your own, or both.

Read more


Single Sign On (SSO) Integration

If your preference is to launch via an existing Wexer solution, an SSO integration can be developed by our team - enabling your end users to log in through existing account credentials. We already have integrations with many of the worlds leading club management systems, as well as the main authentication frameworks but we can implement new integrations as required.

Choosing this approach, you can offer the Wexer Web Player and/or mobile apps (iOS and Android), which can be fully white-labelled and extensively configured to suit your use-case.

Read more


Seamless Embedded

If you already have a mobile app, and you'd like to offer Wexer content and services through it, this option is your you. We can configure our Web Player to run in an embedded mode, allowing your app team to simply load it within a webview in your app. Your users won't be bothered with any extra login prompts or popups, for a totally seamless experience, and minimal effort for your team.

There are two options for authenticating users:

  1. Authentication endpoint on your platform. This is the recommended option, as it allows you to match usage data with your users.
  2. Device identifier. If you don't have the capability to provider an authentication API, we can configure the Web Player to record the users hardware device as the unique identifier.

Read more


What’s Next

Take a look at our Content API Integration Guide