We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
return a 400 bad request stating the tenenant ID is invalid when tenant is referenced with domain in the path. Main issue though here is that the docs specifically use the domain and not the guid. GET https://manage.office.com/api/v1.0/{Domain}/ServiceComms/Services => 400 Bad Request GET https://manage.office.com/api/v1.0/{GUID}/ServiceComms/Services => 200 OK
on other endpoints for example /ServiceComms/Messages both approaches works fine. https://manage.office.com/api/v1.0/{Domain}/ServiceComms/Messages => 200 OK https://manage.office.com/api/v1.0/{GUID}/ServiceComms/Messages => 200 OK
The text was updated successfully, but these errors were encountered:
No branches or pull requests
return a 400 bad request stating the tenenant ID is invalid when tenant is referenced with domain in the path.
Main issue though here is that the docs specifically use the domain and not the guid.
GET https://manage.office.com/api/v1.0/{Domain}/ServiceComms/Services => 400 Bad Request
GET https://manage.office.com/api/v1.0/{GUID}/ServiceComms/Services => 200 OK
on other endpoints for example /ServiceComms/Messages both approaches works fine.
https://manage.office.com/api/v1.0/{Domain}/ServiceComms/Messages => 200 OK
https://manage.office.com/api/v1.0/{GUID}/ServiceComms/Messages => 200 OK
The text was updated successfully, but these errors were encountered: