<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>APIM on Tomas Pivny</title>
		<link>https://www.tompivny.com/tags/apim/</link>
		<description>Recent content in APIM on Tomas Pivny</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Sun, 10 May 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://www.tompivny.com/tags/apim/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Design-First REST APIs in Power Platform</title>
				<link>https://www.tompivny.com/posts/design-first-rest-apis-in-power-platform/</link>
				<pubDate>Sun, 10 May 2026 00:00:00 +0000</pubDate>
				<guid>https://www.tompivny.com/posts/design-first-rest-apis-in-power-platform/</guid>
				<description>&lt;p&gt;When integrating with information systems, establishing a contract before any actual development starts is the common approach, especially in enterprise environments. The reasons for this revolve around established organizational processes and the complexity of implementations. In larger organizations, API contract design does not have to be handled directly by engineers — it is often delegated to roles like enterprise architects, solution analysts or other non-coding roles.&lt;/p&gt;&#xA;&lt;p&gt;For REST APIs, the industry standard for contracts is the &lt;a href=&#34;https://spec.openapis.org/&#34; target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;OpenAPI&lt;/a&gt; specification and the &lt;a href=&#34;https://swagger.io/&#34; target=&#34;_blank&#34; rel=&#34;noreferrer&#34;&gt;Swagger&lt;/a&gt; toolset. Applying this approach, especially when dealing with &lt;strong&gt;inbound integrations&lt;/strong&gt; as a Power Platform engineer, poses some challenges that I&amp;rsquo;d like to address in this post.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
