Check if the APIs used in your app are registered with Azure API Center<\/h2>\n
Azure API Center<\/a> helps you catalog APIs that you use in your organization. Using API Center, you create a single location to keep track of which APIs you use, where they\u2019re located and documented, and who their owner is. API Center also allows you to validate APIs against your organizational rules so that you can stay compliant.<\/p>\n To help you onboard your APIs to API Center, we\u2019re excited to announce the new ApiCenterOnboardingPlugin. The plugin allows you to connect Dev Proxy to your API Center instance. When Dev Proxy intercepts an API request, it\u2019ll compare if the API is registered in API Center. If it\u2019s not registered, it\u2019ll show you which endpoints and operations are not registered. Optionally, it\u2019ll also create a new API with all discovered endpoints and operations.<\/p>\n Using Dev Proxy to detect and onboard APIs used in your applications to API Center saves you time and helps you quickly get insights into what APIs are <\/a>actually used in your organization.<\/p>\n Learn more about the ApiCenterOnboardingPlugin<\/a> in the docs.<\/p>\n API Center lets you track APIs used in your organization throughout their whole lifecycle. As the APIs you use evolve, you\u2019ll be tracking their different versions: from experimental prereleases to outdated versions marked to be decommissioned.<\/p>\n To get the most out of your apps, you want them to use the latest production versions of the available APIs. To help you detect if that\u2019s indeed the case, we\u2019re excited to introduce the new ApiCenterProductionVersionPlugin. The plugin connects Dev Proxy to your API Center instance. For every recorded API request, the plugin checks if it matches a production version of the API. When the API request matches a non-production API, the plugin not only warns you about it, but also recommends upgrading to a production version!<\/p>\n Using Dev Proxy, you can easily ensure that your apps use production APIs which are governed by SLAs and actively managed. This makes your apps more robust and reliable.<\/p>\n Learn more about the ApiCenterProductionVersionPlugin<\/a> in the docs.<\/p>\n Using Dev Proxy, you can easily mock API requests, simulating any scenario: from successful responses relevant for different use cases to errors that let you verify that your app can handle them properly. Dev Proxy allows you to create mocks without having to change your app\u2019s code or write any code that you won\u2019t be shipping.<\/p>\n In this release we extended the existing MockResponsePlugin with the ability to match mock responses based on request bodies. This ability is invaluable for mocking different POST requests which differ only by the request body, such as requesting an access token.<\/p>\n To create a mock response for a request matching it request body, use the new bodyFragment property.<\/p>\n When finding the matching mock response, the MockResponsePlugin will check if the request body contains the specified fragment and return the specified mock response if it does.<\/p>\n This addition further improves Dev Proxy\u2019s ability to simulate API responses and makes it suitable for even more scenarios!<\/p>\n We keep extending Dev Proxy with new features to help you save time and focus on what\u2019s most important: building apps that solve business problems for your colleagues and customers. To help you get the most out of Dev Proxy, we\u2019re excited to announce the Dev Proxy Toolkit VSCode extension!<\/p>\n The Dev Proxy Toolkit extension helps you create Dev Proxy configuration files. It guides you through the different configuration options and warns you if something\u2019s incorrect. It helps you catch any potential issues early and provides you with contextual documentation keeping you in focus. It also notifies you when there\u2019s a new version of Dev Proxy available, so that you can benefit from our latest work.<\/p>\n Install the Dev Proxy Toolkit VSCode extension<\/a> and we\u2019d love to hear from you<\/a> how we could make it better!<\/p>\n To simplify acquiring, setting up and upgrading Dev Proxy, we\u2019re excited to announce that Dev Proxy is now available on winget for Windows, and Homebrew for macOS and Linux!<\/p>\n To install Dev Proxy on Windows using winget, run:<\/p>\n To install Dev Proxy using Homebrew, run:<\/p>\n If you prefer, you can still install Dev Proxy manually from ZIP files that we publish on each release. We hope that these new ways of installing Dev Proxy will encourage you to give it a try, and we\u2019d love to hear from you how we can make it better.<\/p>\n Install Dev Proxy v0.17<\/a> today and build better apps connected to APIs!<\/p>\n Thanks to Elio Struyf and Adam W\u00f3jcik for their feedback on improving handling mock responses. Also, thanks to our recent focus group participants whose feedback led to many improvements around Dev Proxy acquisition and setup, and documentation.<\/p>\n Have any questions, feedback, or suggestions? Join us on Discord<\/a>. We can\u2019t wait to see what you create with Dev Proxy!<\/p>\n Follow us on X (Twitter) \/ @Microsoft365Dev<\/a> and subscribe to our YouTube channel<\/a> to stay up to date on the latest developer news and announcements.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":" We’re excited to share the launch of Dev Proxy v0.17 to help you to build robust apps connected to APIs.<\/p>\n","protected":false},"author":100385,"featured_media":20725,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[289],"class_list":["post-20719","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-365-developer","tag-dev-proxy"],"acf":[],"blog_post_summary":" We’re excited to share the launch of Dev Proxy v0.17 to help you to build robust apps connected to APIs.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/20719","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\/100385"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/comments?post=20719"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/posts\/20719\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media\/20725"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/media?parent=20719"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/categories?post=20719"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-json\/wp\/v2\/tags?post=20719"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"Dev](\"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2024\/04\/Screenshot-2024-04-23-204100.png\")
<\/a>Dev Proxy showing a list of APIs used in an app, and which aren\u2019t registered in API Center.<\/em><\/p>\nCheck if your app uses production APIs as registered with Azure API Center<\/h2>\n
![\"Code,](\"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2024\/04\/Screenshot-2024-04-23-203919.png\")
<\/a>Dev Proxy warning of non-production APIs used in an app and suggesting their production equivalents as listed in API Center.<\/em><\/p>\nImproved mocking requests<\/h2>\n
![\"Code,](\"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2024\/04\/word-image-20719-3.png\")
The new bodyFragment property that allows you to match mock responses based on request body.<\/em><\/p>\nEasily manage Dev Proxy configuration using Dev Proxy Toolkit<\/h2>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/microsoft365dev\/wp-content\/uploads\/sites\/73\/2024\/04\/dev-proxy-toolkit.gif\")
<\/a><\/p>\nSimplified acquisition and setup for Windows and macOS<\/h2>\n
winget install Microsoft.DevProxy --silent<\/code><\/p>\nbrew tap microsoft\/dev-proxy <\/code>\nbrew install dev-proxy<\/code><\/p>\nTry it now<\/h2>\n
\n