<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Oauth Scopes required for workflow extensions in APIs &amp; Integrations</title>
    <link>https://community.hubspot.com/t5/APIs-Integrations/Oauth-Scopes-required-for-workflow-extensions/m-p/227957#M6853</link>
    <description>&lt;P&gt;Hi!&lt;/P&gt;
&lt;P&gt;I had the same issue at the beginning, and HubSpot mentioned us that in order to create the extension definitions with their API, I needed it to use the hapikey associated to our development portal instead of our organization hapikey to create them.&lt;/P&gt;
&lt;P&gt;Let me know if it was the same issue.&lt;/P&gt;</description>
    <pubDate>Fri, 31 Aug 2018 18:57:52 GMT</pubDate>
    <dc:creator>danielolarte</dc:creator>
    <dc:date>2018-08-31T18:57:52Z</dc:date>
  </channel>
</rss>

