locked
EWS URL from Office 365 discovery endpoints RRS feed

  • Question

  • We are using a mix of EWS SOAP API and Office 365 REST API to access user's calendar. We use discover services to determine the Office 365 service endpoints. Can we use the hostname from the Office 365 service endpoint URL to construct the URL for EWS (e.g. https://<hostname from discovery>/ews/exchange.asmx ) ?
    Thursday, February 18, 2016 11:07 PM

Answers

  • Hi,

    I am afraid you were mixing EWS and Office 365 REST API. The Office 365 REST API is a new API provide the endpoint for developers interact the Office 365 data on the cloud.

    After we using the discover service, it return the resource IDs and endpoint URIs. Then we can using the endpoint URIs associate the access token to call the REST service directly.

    More detail about the discovery service and the workflow for the Office 365 REST, please refer to the link below:
    Common endpoint discovery tasks using the Discovery Service API

    And if you were using EWS, you may use the autodicover instead of Office 365 discovery service. Here is an helpful link:
    Autodiscover for Exchange

    And if you still have problem developing with EWS, I suggest that you reopen a new thread in Exchange Server Development forum.

    The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us.

    Thanks for your understanding.

    Regards & Fei


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.


    Friday, February 19, 2016 2:38 AM

All replies

  • Hi,

    I am afraid you were mixing EWS and Office 365 REST API. The Office 365 REST API is a new API provide the endpoint for developers interact the Office 365 data on the cloud.

    After we using the discover service, it return the resource IDs and endpoint URIs. Then we can using the endpoint URIs associate the access token to call the REST service directly.

    More detail about the discovery service and the workflow for the Office 365 REST, please refer to the link below:
    Common endpoint discovery tasks using the Discovery Service API

    And if you were using EWS, you may use the autodicover instead of Office 365 discovery service. Here is an helpful link:
    Autodiscover for Exchange

    And if you still have problem developing with EWS, I suggest that you reopen a new thread in Exchange Server Development forum.

    The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us.

    Thanks for your understanding.

    Regards & Fei


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.


    Friday, February 19, 2016 2:38 AM
  • Thanks Fei. I have posted the question in Exchange Server Development forum.

    We are mixing EWS and Office 365 REST API because of missing features in the REST API (e.g. getting calendar for multiple users in one call). The user has an Office 365 (single/multi/dedicated tenancy) account. So as per your suggestion we have to do separate endpoint discovery for each. We will try this solution.

    Friday, February 19, 2016 4:47 PM
  • Hi,

    Thanks for the detail information for this issue. If you have any idea or feedback about Office 365 REST API, you can try to contact the Office developer team via link below:

    Customer Feedback for the Office Developer Platform

    Regards & Fei


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, February 22, 2016 6:25 AM