Mews API Authentication

How to authenticate Mews API requests: one Bearer API key plus a connectionId. MindCloud handles Mews's custom auth scheme for you.

Every Mews API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Mews account. This page covers both, plus exactly how to send them, so you do not need to visit any other page to get authenticated.

Steps to authenticate

Create a MindCloud account at app.mindcloud.co if you do not already have one.
Generate a MindCloud API Key in API Keys. This is the Bearer token you send on every request. Keep it on your server.
Create a Mews connection in Connections. Mews uses its own authentication scheme. You provide whatever it requires when you create the connection — MindCloud handles the provider-specific details for you.
Copy the connection’s connectionId — you will send it on every request alongside your MindCloud API Key.

How requests are authenticated

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Mews account that should run the action. MindCloud stores and refreshes the Mews credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions.

For example, calling Get Configuration with an Mews connection looks like this:

curl --request POST \
  --url "https://connect.mindcloud.co/v2/universal/apps/mews/actions/get-configuration/run" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
  "connectionId": "$CONNECTION_ID",
  "arguments": {}
}'

The Authorization: Bearer <your MindCloud API Key> header authenticates you to MindCloud; the connectionId tells MindCloud which Mews account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.

Get your Mews Connector API credentials

You need a Mews ClientToken, AccessToken, and Platform Address for the same environment. Mews uses different token sets for demo and production.

Choose your Mews environment
Use the Mews Connector API environment that matches the property you want to connect. The demo environment uses https://api.mews-demo.com. The production environment uses https://api.mews.com.
Mews Open API → Connector API → Environments
Get the Client Token for that environment
For demo testing, Mews publishes shared demo ClientToken values in the Environments guide. For production, Mews issues your ClientToken after you complete their certification process.
Mews Open API → Connector API → Environments
Get the Access Token for the property
Use an AccessToken from the same environment as the ClientToken. In production, the AccessToken is provided for each enterprise that connects to your Mews integration.
Mews Open API → Connector API → Authentication
Enter the values in MindCloud
Paste the Platform Address, Client Token, and Access Token into this connection.

Keep your key safe

Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs. Anyone with the key can call the Universal API as your MindCloud account, across every connection you have created.