Skip to content

Conversation

tkho
Copy link

@tkho tkho commented Jul 6, 2015

Saw requests failing, with the exception KeyError('error'). This will hopefully allow us to see the real error.

@pon
Copy link
Contributor

pon commented Jul 6, 2015

So the reason this is happening is because the most recent version of the wrapper only supports the latest version of the API. In older versions of the API, the errors were returned in the following format:

{
  errors: [
    {
      message: '<Error Message>',
      status_code: 422
    }
  ]
}

And now they look like this

{
  error: {
    message: '<Error Message>',
    status_code: 422
  }
}

So even with this change I don't think it's going to fix your root problem which is using an older version. Does that make sense?

@tkho
Copy link
Author

tkho commented Jul 6, 2015

Makes sense. Thanks!

@mgartner mgartner closed this Jul 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants