WallaBee Devs

Developer information from @WallaBeeApp

[WallaBee Devs @WallaBeeDevs]

Place details now available on https://t.co/hUErDLuCXf! https://t.co/CPnmA4ecFF

[WallaBee Devs @WallaBeeDevs]

In honor of Video Games Day, Wallabee is proud to present Retrobee! https://t.co/k1YKGRh0ZL

[WallaBee Devs @WallaBeeDevs]

Layout updates and ability to view your Pouch and Set Items in your Profile now available on https://t.co/hUErDLuCXf 👍

[ItemBee @ItemBee]

Search functionality now available on Set Detail pages 👍

[WallaBee Devs @WallaBeeDevs]

Search your Sets and Friends list in your profile on https://t.co/hUErDLuCXf. Linking to items within your sets coming (hopefully) soon!

[WallaBee Devs @WallaBeeDevs]

After much sweat, blood, and tears... https://t.co/wLCOKo8bjc

[WallaBee @wallabeegame]

Android Is Here! https://t.co/fzn0kO7pqd

[WallaBee Devs @WallaBeeDevs]

@bighagrid fixed!

[WallaBee Devs @WallaBeeDevs]

@cttwtr @ItemBrowser should be working now - sorry about that

[WallaBee Devs @WallaBeeDevs]

@ItemBrowser @cttwtr we’re looking into it now

[WallaBee Devs @WallaBeeDevs]

The public API, much like the Death Star, is back to being “fully operational”

[WallaBee Devs @WallaBeeDevs]

@ItemBrowser if not, @bendodson will email you over a list of image_keys for each item_type_id and the URL to use :)

[WallaBee Devs @WallaBeeDevs]

@ItemBrowser ah yes, those are the public references. The hidden references aren’t. Not sure if you have an “image_key” reference anywhere?

[WallaBee Devs @WallaBeeDevs]

The public API is now offline. Thanks for all your great apps over the past 4 years.

[WallaBee Devs @WallaBeeDevs]

(However, we will keep full exports of all data so should you want anything at all, just email @bendodson and we’ll sort you out anytime)

[WallaBee Devs @WallaBeeDevs]

As per http://t.co/rwLFiP5vXv we’ll be shutting down the API at 5pm UTC on Friday 28th August. Thanks for the good times.

[WallaBee Devs @WallaBeeDevs]

@ItemBrowser you should probably use a robots.txt file to stop any search engine crawlers (could be that)

[WallaBee Devs @WallaBeeDevs]

@ItemBrowser lots of multiple requests to the same endpoint:

[WallaBee Devs @WallaBeeDevs]

@ItemBrowser probably rate limited as you are hitting it at about 20 requests a second (all /users/:id requests)

[WallaBee Devs @WallaBeeDevs]

@ItemBrowser not that we’re aware of

[WallaBee Devs @WallaBeeDevs]

Writes are synchronised in less than 10ms so there shouldn’t be any issues with the API being behind the app - we’ll monitor it though.