none
uniqueBody is always undefined on message resource o365 outlook mail api RRS feed

  • Question

  • According to the API specs: http://graph.microsoft.io/en-us/docs/api-reference/v1.0/resources/message, every message should contain a uniqueBody property. We're using v1 of the graph api and none of our returning messages contain this property or value. Has this not been rolled out yet? Can someone please confirm if this is available or if there is another way to access this information?

    Thank you.

    Monday, April 11, 2016 2:10 AM

Answers

  • Hi,

    The property "uniqueBody" is not explicit by default. If you would like to get uniqueBody through Graph API, please explicitly add it in an OData statement.

    For example:

    https://graph.microsoft.com/v1.0/me/mailFolders/Inbox/messages?$select=uniqueBody

    The above request would return uniqueBody for all the messages in the Inbox folder.

    Thanks,
    Reken Liu


    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Marked as answer by draisy Tuesday, April 12, 2016 2:55 AM
    Monday, April 11, 2016 6:37 AM
    Moderator

All replies

  • Hi,

    The property "uniqueBody" is not explicit by default. If you would like to get uniqueBody through Graph API, please explicitly add it in an OData statement.

    For example:

    https://graph.microsoft.com/v1.0/me/mailFolders/Inbox/messages?$select=uniqueBody

    The above request would return uniqueBody for all the messages in the Inbox folder.

    Thanks,
    Reken Liu


    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Marked as answer by draisy Tuesday, April 12, 2016 2:55 AM
    Monday, April 11, 2016 6:37 AM
    Moderator
  • Thanks. This worked perfectly. Could the documentation b updated to reflect this? There's no mention of any of this here: http://graph.microsoft.io/en-us/docs/api-reference/v1.0/resources/message
    Wednesday, April 13, 2016 12:11 AM