Stack Apps is a question and answer site for apps, scripts, and development with the Stack Exchange API. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In reading about the API rate limiting, the documentation talks about a method responding with an ominous backoff field, and states that the client should cease from calling that method for that many seconds.

Is there a dummy method that always returns a backoff that I can test against? Otherwise, what does the backoff field come back in the form of?

Regular int?

{ ... "backoff": 20}

a string to be parsed?

{ ... "backoff": "20"}
share|improve this question
    
Related feature request with a possible stopgap in the answer(s): "Can we have some debug endpoints for testing corner cases?" – Brock Adams Jan 3 '15 at 18:09

The documentation for the response wrapper defines the backoff field as an integer, so you can expect it to come back in the first form.

I don't believe there's any way to graciously test a backoff response short of actually angering the API (which I'd recommend against).

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .