Skip to content

Update authentication guidelines for token acquisition #96

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
amandine-mestre wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Update authentication guidelines for token acquisition #96

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1b7b23b
Update authentication guidelines for token acquisition
amandine-mestre Sep 16, 2026
a4d30eb
Update channel-manager-api/guidelines/authentication.md
amandine-mestre Sep 16, 2026
b12b245
Update channel-manager-api/guidelines/authentication.md
amandine-mestre Sep 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions channel-manager-api/guidelines/authentication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,11 +15,13 @@ Additionally, all operations regarding a specific connection with a property req

To get started using the API, you need to obtain the necessary tokens:

* **Client Token**: This token is provided by Mews and is essential for authenticating your Channel Manager application. You will receive it during the initial setup process.
* **Connection Token**: This token is specific to each connection with a property. You can obtain it in three ways:
* **Client Token**: This token is provided by Mews and is essential for authenticating your Channel Manager application. Once we have created your integration profile, you will receive an automatic email containing your clientToken.
* **Connection Token**: This token is specific to each connection with a property. You can obtain it in four ways:
* **Using the API**: Automatic (recommended) : If your application supports [Mews: /changeNotification](../channel-manager-operations/notifications.md), you will receive an API notification to this endpoint when the property first connects, which contains their unique connectionToken.
* **Using the API**: Manual : If your application supports [Mews: Get properties](../mews-operations/configuration.md#get-properties), you can recover the Connection Tokens for all connections the property supports for this client application. In this case, an employee email address is used as an authorization token.

@moxly moxly Sep 16, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[warning] correctness

The employee email is not itself an authorization token. The linked Get properties contract requires both clientToken and an email, and describes the email as a verified enterprise employee address (channel-manager-api/mews-operations/configuration.md:5-7, 20-23). Calling the email an authorization token may lead integrators to put it in an auth header or omit the required client token. Describe it as an authorization input used alongside the Client Token instead.

* **From Mews**: When authorized by the property, Mews will provide you with the Connection Token.
* **Through the property**: The property can also obtain the token via __Mews Operations__.
* **Using the API**: If your application supports [Mews: Get properties](../mews-operations/configuration.md#get-properties), you can recover the Connection Tokens for all connections the property supports for this client application. In this case, an employee email address is used as an authorization token.


> For detailed steps and additional information, refer to [Your integration journey](../your-journey/README.md).

Expand Down