<?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 Access token from Authorization Code Flow requires specific parameter order in Spotify for Developers</title>
    <link>https://community.spotify.com/t5/Spotify-for-Developers/Access-token-from-Authorization-Code-Flow-requires-specific/m-p/5360852#M4296</link>
    <description>&lt;P&gt;&lt;STRONG&gt;Plan&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Premium&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Country&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;France&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Operating System&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Windows 10&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;My Question or Issue&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm new to the Spotify community. I'm trying to implement Oauth2 in my application and it seems like I found a bug. Normally speaking, HTTP parameters does not have any order and you can provide them in the order you want. When asking to retrieve an Access Token form the&amp;nbsp;Authorization Code Flow, I found out that order is important with the same valid parameters in different orders you can obtain either a 400 HTTP error with no info or a 200 valid response with a token.&lt;/P&gt;&lt;P&gt;&lt;A href="https://developer.spotify.com/documentation/general/guides/authorization/code-flow/#request-access-token" target="_blank" rel="noopener"&gt;https://developer.spotify.com/documentation/general/guides/authorization/code-flow/#request-access-token&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you either fix this bug and allow to pass parameters in any order or at explicitly write in the page that parameter order has meaning and give more information in the response than a raw 400 error ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;I linked some screenshot from my Python test requests.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your time,&lt;/P&gt;&lt;P&gt;Hylectrif&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 31 Mar 2022 17:54:31 GMT</pubDate>
    <dc:creator>Hylectrif</dc:creator>
    <dc:date>2022-03-31T17:54:31Z</dc:date>
    <item>
      <title>Access token from Authorization Code Flow requires specific parameter order</title>
      <link>https://community.spotify.com/t5/Spotify-for-Developers/Access-token-from-Authorization-Code-Flow-requires-specific/m-p/5360852#M4296</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Plan&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Premium&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Country&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;France&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Operating System&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Windows 10&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;My Question or Issue&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm new to the Spotify community. I'm trying to implement Oauth2 in my application and it seems like I found a bug. Normally speaking, HTTP parameters does not have any order and you can provide them in the order you want. When asking to retrieve an Access Token form the&amp;nbsp;Authorization Code Flow, I found out that order is important with the same valid parameters in different orders you can obtain either a 400 HTTP error with no info or a 200 valid response with a token.&lt;/P&gt;&lt;P&gt;&lt;A href="https://developer.spotify.com/documentation/general/guides/authorization/code-flow/#request-access-token" target="_blank" rel="noopener"&gt;https://developer.spotify.com/documentation/general/guides/authorization/code-flow/#request-access-token&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you either fix this bug and allow to pass parameters in any order or at explicitly write in the page that parameter order has meaning and give more information in the response than a raw 400 error ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;I linked some screenshot from my Python test requests.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your time,&lt;/P&gt;&lt;P&gt;Hylectrif&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 31 Mar 2022 17:54:31 GMT</pubDate>
      <guid>https://community.spotify.com/t5/Spotify-for-Developers/Access-token-from-Authorization-Code-Flow-requires-specific/m-p/5360852#M4296</guid>
      <dc:creator>Hylectrif</dc:creator>
      <dc:date>2022-03-31T17:54:31Z</dc:date>
    </item>
  </channel>
</rss>

