You found a bug? We'll fix that for you! Let's first check if things are working with Postman. This is to eliminate any issues that might have come from your environment.
Whenever you run into any authentication issues we expect you to go through this self-check test.
Check out our video guide on how to set up environment and test in Postman!
- Create credentials in myfrontdesk for Postman
- Get access_token/refresh_token in Postman
- Postman's redirect URL: https://www.getpostman.com/oauth2/callback
- Authenticate using Postman
First test access_token. Using call /access_token_check and sending Authorization header
SUCCESS
{
"success": true
}ERROR
{
"error": "access_denied",
"message": "The resource owner or authorization server denied the request."
}
Then see if access_token has access to requested property (two-ways)
-
/getHotels(with no parameters) will return all properties that thisaccess_tokenhas access;
OR
-
/getHotels?propertyID=#requested_property#
ERROR
{
"success": false,
"message": "None of the included property id's match the access_token user's property id"
}You're still experiencing issues. Send us an email to devhelp@cloudbeds.com with the following details:
- X-response-ID (from the response header)
- Your app's assigned client_id
- Call(s) requested
- Access token used
- Parameters sent
- Response received
- Expected/unexpected records, and why
- Property ID Involved
A while back, we added the key X-Request-ID in the HTTP Response Header. We encourage you to include this ID anytime you submit a customer service request so we can provide you with quicker and more accurate support.
If you’re not logging it, it’s a great time to start. Otherwise you’ll be able to see the X-Request-ID when testing with Postman.
This value is set by our server, it can be logged on the client side and at the moment it does not accept an ID sent by the client.
Comments
0 comments
Please sign in to leave a comment.