Unable to run the first example

[sagihaider]

---

ZooplaAPIException Traceback (most recent call last)
in ()
----> 1 rl = zoopla.property_rich_list({'area': 'SW11'})

G:\GitHub\zoopla-master\zoopla\api.py in property_rich_list(self, params)
105 request_schema=BaseRequestSchema,
106 result_schema=RichlistResultSchema,
--> 107 parameters=params
108 )
109

G:\GitHub\zoopla-master\zoopla\api.py in _base_call(self, action, request_schema, result_schema, parameters)
58 raise RequestFormatException(request_errors)
59
---> 60 response = self._api_call(action, parameters)
61 result, errors = result_schema().load(response)
62

G:\GitHub\zoopla-master\zoopla\api.py in _api_call(self, action, params)
49 return response.json()
50 else:
---> 51 raise ZooplaAPIException(response.reason)
52
53 def _base_call(self, action, request_schema, result_schema, parameters):

ZooplaAPIException: Zoopla returned an error: Forbidden

[AnthonyBloomer]

Hi @sagihaider, the Forbidden error indicates an invalid api key. Has your API key since been allowed authorisation to the API? I remember when I initially signed up there was a waiting period before I could make requests to the API.

[clbarnes]

Zoopla may have abandoned their public API

I made an account a few days ago and was able to use the key immediately, but started getting "developer inactive" 403 Forbiddens today. I got a new key but that got 403s immediately. Really annoying, as I put a day's work into it when it was working, and another half-day before actually trying to hit the API today.

[monkeydust]

Same issue - any word from Zoopla? Any supported alternatives?

[mmenti]

I believe the Zoopla API is dead in the water. I wrote about it well over a year ago, and nothing has changed since then, so it looks completely abandoned. The only action they took over the last 16 months was to remove the forums (which consisted of only 2 types of posts, spam and "why does my API key not work?")

https://medium.com/@mariomenti/how-not-to-run-an-api-looking-at-you-zoopla-bda247e27d15

[aleks-mariusz]

FWIW (and sorry to revive a stale thread), i am still able to use the API today (just started yesterday so maybe i'll run into this issue at some point as well, will update this post if issues are found)

i have noticed however that i occasionally have gotten 403 Forbidden errors instead when trying to browse the site and pull up pages manually using a browser - from a simple investigation, it appears Zoopla implements some kind of occasional blacklisting of IPs (or ranges), When i try to access it from a proxy the site works fine - eventually i get unblocked and 403's dissappear and i'm able to browse the page

So i'm wondering if Zoopla occasionally blocks you - maybe try your API access from another IP range if possible? UPDATE: so i've gotten the "Forbidden" API response after-all now as well, but seems this happens to me (so far) if i exceed 100 queries per hour (which is an abysmally low query allowance, agreed) - however after the hour, the queries continue to work. Not sure if people have considered this as a possible explanation (though understandably, if you are brand new, reaching the limit wouldn't explain getting a Forbidden response then).

Also curiously, if i set page_number to 100 or higher, i always get a 'Bad Request' response - is it the case that you can only query the first 100 pages (of size "page_size" param, which by default is 10 but can be set up to a max of 100)? If so, this would imply that you can only ever get look at the first 10k listing-search results (and if your overall query returns more than that, you can't query for the 10001th or later listing).. my work-around (since my listing search query returns just under 20k) is once i reach page 99, to switch the ordering from descending to ascending so in effect, starting on the overall list, but from the other direction to get the remaining 10000 at the other end.

[albertnjoku]

The api has not worked for once since I registered (4 days ago). I keep getting:
zoopla.exceptions.ZooplaAPIException: Zoopla returned an error: Forbidden

[chiragxarora]

FWIW (and sorry to revive a stale thread), i am still able to use the API today (just started yesterday so maybe i'll run into this issue at some point as well, will update this post if issues are found)

i have noticed however that i occasionally have gotten 403 Forbidden errors instead when trying to browse the site and pull up pages manually using a browser - from a simple investigation, it appears Zoopla implements some kind of occasional blacklisting of IPs (or ranges), When i try to access it from a proxy the site works fine - eventually i get unblocked and 403's dissappear and i'm able to browse the page

So i'm wondering if Zoopla occasionally blocks you - maybe try your API access from another IP range if possible? UPDATE: so i've gotten the "Forbidden" API response after-all now as well, but seems this happens to me (so far) if i exceed 100 queries per hour (which is an abysmally low query allowance, agreed) - however after the hour, the queries continue to work. Not sure if people have considered this as a possible explanation (though understandably, if you are brand new, reaching the limit wouldn't explain getting a Forbidden response then).

Also curiously, if i set page_number to 100 or higher, i always get a 'Bad Request' response - is it the case that you can only query the first 100 pages (of size "page_size" param, which by default is 10 but can be set up to a max of 100)? If so, this would imply that you can only ever get look at the first 10k listing-search results (and if your overall query returns more than that, you can't query for the 10001th or later listing).. my work-around (since my listing search query returns just under 20k) is once i reach page 99, to switch the ordering from descending to ascending so in effect, starting on the overall list, but from the other direction to get the remaining 10000 at the other end.

Is it still working?