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.
1. Check authentication
Whenever you run into any authentication issues we expect you to go through this self-check test.
Check our Authentication section for additional details.
Already have an access_token/refresh_token pair or API ley?
First test the access_token or API keu. 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"
}
2. Send us a ticket
You're still experiencing issues. Send us an email to integrations@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
- Logs for the request/response including the timestamp
- Expected/unexpected records, and why
- Property ID Involved
Comments
0 comments
Please sign in to leave a comment.