{"id":12597,"date":"2023-01-04T05:13:57","date_gmt":"2023-01-04T13:13:57","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/?p=12597"},"modified":"2023-01-25T09:54:31","modified_gmt":"2023-01-25T17:54:31","slug":"microsoft-graph-developer-proxy-v0-3","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/microsoft-graph-developer-proxy-v0-3\/","title":{"rendered":"New Microsoft Graph Developer Proxy preview v0.3 with support for all APIs"},"content":{"rendered":"<p>Build resilient and performant apps with the latest preview version of the Microsoft Graph Developer Proxy.\u00a0In this new version, we&#8217;re excited to introduce the support for simulating errors on Microsoft Graph and other APIs, and contextual guidance to help you improve the performance of your apps.<\/p>\n<p><a href=\"https:\/\/github.com\/microsoftgraph\/msgraph-developer-proxy\/releases\/tag\/v0.3.0\">Download Microsoft Graph Developer Proxy v0.3<\/a> and check if your apps properly handle API errors.<\/p>\n<h2>Simulate errors on Microsoft Graph and other APIs<\/h2>\n<p>After releasing the Developer Proxy, we received some great feedback from all of you telling us how invaluable it is to finally be able to simulate different types of errors that applications can come across when calling APIs. You also shared that many of your applications use Microsoft Graph and other APIs that you\u2019d like to be able to test too.<\/p>\n<p>In this new release, we add support for simulating errors on any API. By default, we include configuration for Microsoft Graph and SharePoint APIs, but you can extend it to include other APIs as well by adding the URLs that the Proxy should intercept.<\/p>\n<p><figure id=\"attachment_12601\" aria-labelledby=\"figcaption_attachment_12601\" class=\"wp-caption alignnone\" ><a href=\"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2023\/01\/msgraph-developer-proxy-sharepoint-api.png\"><img decoding=\"async\" class=\"wp-image-12601 size-large\" src=\"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2023\/01\/msgraph-developer-proxy-sharepoint-api-1024x554.png\" alt=\"SharePoint Framework web part visible in a web browser. Network tab with a request to SharePoint API failed by the Graph Developer Proxy highlighted\" width=\"640\" height=\"346\" srcset=\"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2023\/01\/msgraph-developer-proxy-sharepoint-api-1024x554.png 1024w, https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2023\/01\/msgraph-developer-proxy-sharepoint-api-300x162.png 300w, https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2023\/01\/msgraph-developer-proxy-sharepoint-api-768x416.png 768w, https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2023\/01\/msgraph-developer-proxy-sharepoint-api-1536x831.png 1536w, https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2023\/01\/msgraph-developer-proxy-sharepoint-api-2048x1109.png 2048w\" sizes=\"(max-width: 640px) 100vw, 640px\" \/><\/a><figcaption id=\"figcaption_attachment_12601\" class=\"wp-caption-text\"><em>Simulating SharePoint API errors using Microsoft Graph Developer Proxy while building a SharePoint Framework web part<\/em><\/figcaption><\/figure><\/p>\n<p>For more information about the updated settings, check our <a href=\"https:\/\/github.com\/microsoftgraph\/msgraph-developer-proxy\/wiki\/Proxy-settings\">documentation<\/a>.<\/p>\n<h2>Use $select to improve performance of your apps<\/h2>\n<p>Microsoft Graph is a rich API that gives you access to data and insights from Microsoft 365. By extending your requests to Microsoft Graph with the $select query parameter, you\u2019ll limit the data that Microsoft Graph returns to just what\u2019s needed by your app, speeding up the API response.<\/p>\n<p>Microsoft Graph Developer Proxy will now warn you of any requests to Microsoft Graph API that don\u2019t use the $select parameter and provide you with a link to the guidance with more information about using the $select parameter.<\/p>\n<p><figure id=\"attachment_12600\" aria-labelledby=\"figcaption_attachment_12600\" class=\"wp-caption alignnone\" ><a href=\"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2023\/01\/msgraph-developer-proxy-select-guidance.png\"><img decoding=\"async\" class=\"wp-image-12600 size-large\" src=\"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2023\/01\/msgraph-developer-proxy-select-guidance-1024x549.png\" alt=\"Web request to Microsoft Graph API highlighted in a terminal window. Another terminal window showing guidance about the lack of $select query parameter.\" width=\"640\" height=\"343\" srcset=\"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2023\/01\/msgraph-developer-proxy-select-guidance-1024x549.png 1024w, https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2023\/01\/msgraph-developer-proxy-select-guidance-300x161.png 300w, https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2023\/01\/msgraph-developer-proxy-select-guidance-768x412.png 768w, https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2023\/01\/msgraph-developer-proxy-select-guidance-1536x824.png 1536w, https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2023\/01\/msgraph-developer-proxy-select-guidance-2048x1099.png 2048w\" sizes=\"(max-width: 640px) 100vw, 640px\" \/><\/a><figcaption id=\"figcaption_attachment_12600\" class=\"wp-caption-text\"><em>Microsoft Graph Developer Proxy showing a warning for a Microsoft Graph API call without the $select query parameter<\/em><\/figcaption><\/figure><\/p>\n<h2>What\u2019s next<\/h2>\n<p>Here are some things that we\u2019re currently working on.<\/p>\n<h3>Improve the readability of the Proxy\u2019s output<\/h3>\n<p>As we add more features to the Microsoft Graph Developer Proxy, we want to make it easier for you to follow the different messages. We\u2019ve been researching the different options to improve the Proxy\u2019s output and will start the implementation shortly.<\/p>\n<h3>Notify when using beta endpoints<\/h3>\n<p>Sometimes, during development, you might be using Microsoft Graph beta endpoints to try new functionality. Unfortunately, beta endpoints are subject to change, and we don&#8217;t support using them in production applications.<\/p>\n<p>We regularly release new features to Microsoft Graph APIs on the v1.0 endpoint. We&#8217;re looking into ways to help you understand which beta endpoints you use in your applications so that you can upgrade them to use the v1.0 endpoints instead which is supported in production.<\/p>\n<h3>Support plugins<\/h3>\n<p>We\u2019re working to refactor the Microsoft Graph Developer Proxy to make it more modular. This will not only make it easier to maintain the different features in the future but will also give you the opportunity to build plugins to support scenarios specific to your organization.<\/p>\n<h2>Try it today<\/h2>\n<p><a href=\"https:\/\/github.com\/microsoftgraph\/msgraph-developer-proxy\/releases\/tag\/v0.3.0\">Download Microsoft Graph Developer Proxy v0.3<\/a> and check if your apps properly handle API errors.<\/p>\n<p>After you&#8217;ve tried the Proxy, please let us know how we can make it better by <a href=\"https:\/\/github.com\/microsoftgraph\/msgraph-developer-proxy\/issues\">creating an issue on our GitHub repo<\/a>. We look forward to hearing from you!<\/p>\n<p>Visit our <a href=\"https:\/\/developer.microsoft.com\/graph\" target=\"_blank\" rel=\"noopener\">Microsoft Graph Dev Center<\/a> for more resources. And follow us on <a href=\"https:\/\/twitter.com\/Microsoft365Dev\" target=\"_blank\" rel=\"noopener\">Twitter @Microsoft365Dev<\/a> for the latest developer news!<\/p>\n<p>Happy coding!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Build resilient and performant apps with the latest preview version of the Microsoft Graph Developer Proxy.<\/p>\n","protected":false},"author":74222,"featured_media":12613,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[3],"tags":[222,146],"class_list":["post-12597","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-graph","tag-developer-proxy","tag-microsoft-graph-api"],"acf":[],"blog_post_summary":"<p>Build resilient and performant apps with the latest preview version of the Microsoft Graph Developer Proxy.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/12597","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/users\/74222"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/comments?post=12597"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/12597\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media\/12613"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media?parent=12597"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/categories?post=12597"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/tags?post=12597"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}