CORS support for PATCH on /v1/budgets/default/transactions ?

I've been playing around with the API for a simple webapp, and generally things are working well (great job, YNAB!).  However, when it comes to an updateTransactions call from Javascript, it works fine in a nodejs test app, but fails in the browser.


It appears to be getting blocked by CORS, as I get a 401/unauthorized when requesting OPTIONS with "Access-Control-Request-Method: PATCH" (GET method immediately before that works fine - and the response lists GET,POST,PUT,OPTIONS... no PATCH).

Am I possibly doing something wrong?  Is there some reason this could be on purpose?



3replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Blue Guitar - You've hit something unexpected!  Sure enough, I checked and we don't have PATCH whitelisted for CORS.  I'll get an update in to fix this.  Thanks for letting us know.

    Reply Like
  • Hey Blue Guitar , looks like yesterday's update should mean that our API now support CORS! Here are the release notes for your reading pleasure. :) Have a great weekend!

    Reply Like
    • Dan Yep, looks like it works now!  Thanks. Brady  too!

      Reply Like
Like Follow
  • 2 mths agoLast active
  • 3Replies
  • 50Views
  • 3 Following