GET Single Category by Month Broken

 The endpoint in question. 

I originally responded to a year-old thread which experienced a near-identical error here.

That thread confirmed that it wasn't supposed to be broken and they pushed a timely fix to production. However, it looks like the bug has been reintroduced.

When the endpoint is hit, the response returned by all the clients I've tested (including the YNAB's Swagger interface) is:

{
  "error": {
    "id": "404.2",
    "name": "resource_not_found",
    "detail": "Resource not found"
  }
}

Can you guys confirm that it is indeed broken and when to expect a fix?

2replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Why is it that YNAB support has responded to every single thread that's newer than this one in this forum section but has failed to respond to mine?

    Like
  • Hi Matt - are you getting this response when trying to fetch a month several months in the future?

    Like
Like Follow
  • 2 mths agoLast active
  • 2Replies
  • 138Views
  • 2 Following