<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">

 
 
  <channel>
    <title>Flow APIs on ServiceNow Developer Blog</title>
    <link>https://developer.servicenow.com/blog.do?p=/tags/flow-apis/</link>
    <description>Recent content in Flow APIs on ServiceNow Developer Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 22 Feb 2019 10:58:15 -0500</lastBuildDate>
    
        
        
         
        <atom:link href="https://developer.servicenow.com/blog.do?p=/tags/flow-apis/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>New for Developers in Madrid: Flow and Action APIs</title>
      <link>https://developer.servicenow.com/blog.do?p=/post/new-for-developers-in-madrid-flow-apis/</link>
      <pubDate>Fri, 22 Feb 2019 10:58:15 -0500</pubDate>
      
      <guid>https://developer.servicenow.com/blog.do?p=/post/new-for-developers-in-madrid-flow-apis/</guid>
      <description>As we continue our lightning tour of new developer-facing features of the Madrid release, we touch on some that are not net-new but include relevant changes. Today&amp;rsquo;s post is one of these. The London release featured the first release of Flow Designer APIs that allowed for invoking Flows via JavaScript APIs. That capability has been beefed up in Madrid and we&amp;rsquo;ll look at that.
Server-Side Flow APIs The London release had two APIs, startAsync for Flows and SubFlows.</description>
    </item>
    
  </channel>
</rss>