<?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 Did 404 change to 409 in v2? in Dropbox API Support &amp; Feedback</title>
    <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Did-404-change-to-409-in-v2/m-p/208370#M10278</link>
    <description>&lt;P&gt;I'm migrating Nebulous Notes to v2, and I noticed that if I sync a file that doesn't exist on DB, I get a 409, instead of 404. Is this intentional? I use the status check in my logic to determine whether or not to upload a file, and want to make sure I set it to the right code.&lt;/P&gt;</description>
    <pubDate>Wed, 29 May 2019 09:25:30 GMT</pubDate>
    <dc:creator>philipkd</dc:creator>
    <dc:date>2019-05-29T09:25:30Z</dc:date>
    <item>
      <title>Did 404 change to 409 in v2?</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Did-404-change-to-409-in-v2/m-p/208370#M10278</link>
      <description>&lt;P&gt;I'm migrating Nebulous Notes to v2, and I noticed that if I sync a file that doesn't exist on DB, I get a 409, instead of 404. Is this intentional? I use the status check in my logic to determine whether or not to upload a file, and want to make sure I set it to the right code.&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2019 09:25:30 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Did-404-change-to-409-in-v2/m-p/208370#M10278</guid>
      <dc:creator>philipkd</dc:creator>
      <dc:date>2019-05-29T09:25:30Z</dc:date>
    </item>
    <item>
      <title>Re: Did 404 change to 409 in v2?</title>
      <link>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Did-404-change-to-409-in-v2/m-p/208398#M10284</link>
      <description>Yes, API v2 makes different use of status codes than API v1. For example, where API v1 may have used a 404 to indicate a non-existent file (among other issues), that would be a 409 error in API v2, with more specific error information available in the body. &lt;BR /&gt;&lt;BR /&gt;You can find information on the design of API v2 on the blog:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://blogs.dropbox.com/developers/2015/04/a-preview-of-the-new-dropbox-api-v2/" target="_blank"&gt;https://blogs.dropbox.com/developers/2015/04/a-preview-of-the-new-dropbox-api-v2/&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://blogs.dropbox.com/developers/2015/04/how-many-http-status-codes-should-your-api-use/" target="_blank"&gt;https://blogs.dropbox.com/developers/2015/04/how-many-http-status-codes-should-your-api-use/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;You can find more information on error handling in the API v2 documentation:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://www.dropbox.com/developers/documentation/http/documentation#error-handling" target="_blank"&gt;https://www.dropbox.com/developers/documentation/http/documentation#error-handling&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this helps!</description>
      <pubDate>Fri, 24 Feb 2017 22:46:30 GMT</pubDate>
      <guid>https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/Did-404-change-to-409-in-v2/m-p/208398#M10284</guid>
      <dc:creator>Greg-DB</dc:creator>
      <dc:date>2017-02-24T22:46:30Z</dc:date>
    </item>
  </channel>
</rss>

