Which error is thrown for Rate Limits?

[sqlninja]

I know the API itself throws a 403 and 429 response codes but does this gem catch the response and yield an actual error or should I look for the response codes?

[jmulford-bw]

We yield an error that contains the response code and a description of the response

https://github.com/Bandwidth/ruby-bandwidth/blob/master/lib/bandwidth/errors.rb

[sqlninja]

So the GenericError?
Do you have an example response?

[jmulford-bw]

  begin
    messages = Bandwidth::Message.list(client, {:fromDateTime => start_date, :toDateTime => end_date, :size => 1000})
  rescue Bandwidth::Errors::GenericError => e
    puts e

[sqlninja]

yeah, I saw that...
but what all is e made up of?
is e.code == 429 || e.code == 403 an acceptable manner of catching the rate_limit?

[jmulford-bw]

Yes, that should work. Nope I'm wrong. Look below. Take note that 429 and 403 are slightly different errors, our error docs can be found here https://dev.bandwidth.com/ap-docs/errors.html

[sqlninja]

would e.code == 'too-many-requests' || e.code == 'message-rate-limit' be better?

Following this as an example of the response:

Status: 403 Forbidden
Content-Type: application/json

{
  "category": "limit",
  "code": "message-rate-limit",
  "message": "You can send 1 messages per 1 seconds, calculated as the average over 10 seconds. Your rate is: 1.1",
  "details": [
    {
      "name": "requestMethod",
      "value": "POST"
    },
    {
      "name": "remoteAddress",
      "value": "x.x.x.x"
    },
    {
      "name": "requestPath",
      "value": "users/u-asdf/messages"
    }
  ]
}

[sqlninja]

Basically is e.code going to have a value like 403 or message-rate-limit

[jmulford-bw]

Actually yeah that's right. The "code" field is set in this manner

    # Check response object and raise error if status code >= 400
    # @param response response object
    def check_response(response)
      if response.status >= 400
        parsed_body = JSON.parse(response.body)
        raise Errors::GenericError.new(parsed_body['code'], parsed_body['message'])
      end
    end

My apologies. I updated my previous comment