- #Make visuals great again v2.0 how to#
- #Make visuals great again v2.0 full#
- #Make visuals great again v2.0 registration#
"BodyPreview": "_\nFrom: Alex D\nSent: Sunday, Octo5:28 PM\nTo: Katie Jordan\nSubject: Meeting Notes\n\nPlease send me the meeting notes ASAP",īy default, the response includes all the properties of the specified message. "Content": "\n_\nFrom: Alex D\nSent: Sunday, Octo5:28 PM\nTo: Katie Jordan\nSubject: Meeting Notes\n\nPlease send me the meeting notes ASAP\n" "ChangeKey": "CQAAABYAAACd9nJ/tVysQos2hTfspaWRAAADTIKz", Sample response "W/\"CQAAABYAAACd9nJ/tVysQos2hTfspaWRAAADTIKz\"", "Address": "W/\"CwAAABYAAACd9nJ/tVysQos2hTfspaWRAAADTJqJ\"", "Address": "W/\"CQAAABYAAACd9nJ/tVysQos2hTfspaWRAAADTJqP\"", "value": "W/\"CQAAABYAAACd9nJ/tVysQos2hTfspaWRAAADTJqS\"", Sample response "$metadata#Me/MailFolders('sentitems')/Messages(Sender,Subject)", Sample request GET $select=Sender,Subject
#Make visuals great again v2.0 full#
Refer to the sample response in Get a message for a full list of properties that would be returned for a message if you don't use $select.
#Make visuals great again v2.0 how to#
The following example shows how to use $select to specify returning only the Sender and Subject properties of each message in the response. See OData query parameters for filtering, sorting, and paging parameters. Use $select to specify only those properties you need for best performance. Get a message collection Minimum required scopeīy default, each message in the response includes all its properties.
To get the entire, original HTML content, include the following HTTP request header: Prefer: outlook.allow-unsafe-html If the body is HTML, by default, any potentially unsafe HTML (for example, JavaScript) embedded in the Body property would be removed before the body content is returned in a REST response. The message body can be either text or HTML. You can get a message collection or an individual message from a mailbox folder.Įach message in the response contains multiple properties, including the Body property. See Use the Outlook REST API for more information common to all subsets of the Outlook REST API. A few API subsets, such as Focused Inbox API, can be performed on the signed-in user, or a user specified by a user ID, given the appropriate permissions. Target userĪll Mail API requests are performed on behalf of the signed-in user unless specified. The functionality may differ depending on the specific version. The Mail REST API is supported in all versions of the Outlook REST API. Keep this in mind as you proceed with the specific operations in the Mail API.
#Make visuals great again v2.0 registration#
You can find out more about some streamlined registration and authorization options for you. Getting an access token requires you to have registered and identified your app, and obtained the appropriate authorization. Like other Outlook REST API, for every request to the Mail API, you should include a valid access token. You can use the following well-known folder names instead of the ID to specify the corresponding folder: Inbox, SentItems, Drafts, or DeletedItems. You can get, create, change, delete, and manage folders. Mailbox folders can contain messages and other folders. A folder is either specified by an ID or a well-known folder name, such as Inbox, Drafts, SentItems, or DeletedItems. Messages are stored in mailbox folders, so message endpoints often include the folder that contains the message. Not interested in v2.0 of the API? In the table of contents on the left, go to the Office 365 REST API reference section and select the version you want. For simplicity of reference, the rest of this article uses to include these Microsoft account domains.