Warning: Undefined array key "HTTP_REFERER" in /customers/1/a/a/habboapi.net/httpd.www/static/php/functions/page.functions.php on line 101 Documentation - Habbo API

HabboAPI Documentation

HabboAPI's Public APIs

HabboAPI is a free to use API, that aim to help Habbo fansite builders create awesome tools and features for their sites. We offer a large number of API endpoints, that serve you the lastest badges, furniture, clothes and a lot more. No need to be an programming expert. All you need is the basic skills and a little flair for detail. The rest is on our side - just copy and paste in our code examples, style it to match your layout and your are ready!

We are proud to say that we has the fastest scanners out there! We find the latest badges, furniture and clothes, within seconds. In addition to that, our Habbo Finder database is constantly updated with the latest Habbos.

Note that the HabboAPI is not affiliated with, endorsed, sponsored, or specifically approved by Sulake Corporation Oy or its Affiliates. HabboAPI may use the trademarks and other intellectual property of Habbo, which is permitted under Habbo Fan Site Policy.

HabboAPI collect data from different source files and folders, hosted on Habbo's servers. We find the latest added Habbo badges. You can even see how many own the badge. We break up the furniture and clothing .swf files and make images from the different layers. We find the different directions, states and colors. We sort the data and serve it to you in a nice readable JSON format, that you can use to make new and awesome tools for your Habbo fansite.

The HabboAPI are created and maintained by volunteers.

But, what is a API?

An API is an application programming interface - in short, it’s a set of rules that lets programs talk to each other, exposing data and functionality across the internet in a consistent format. In other words, we give you access to an API accessed via HTTP protocol at a predefined set of URLs. These URLs represent various resources - any information or content accessed at that location, which can be returned as JSON, HTML, audio files, or images. Often, resources have one or more methods that can be performed on them over HTTP.

HabboAPI for example, provides many separate REST APIs for looking up Habbo content information and a whole lot more. In HabboAPI’s ecosystem, each product is its own API, but you will work with each of them in roughly the same way.

HabboAPI has a 5 different endpoints. You can use the /badges, /furni, /furni/lines, /clothing or /habbos endpoint to extract info and images of the different items. We have the info on more than 60.000 badges, 6.500 furniture, 250 lines and 500 clothing.

Our API require some form for development language. We have provided a few examples (jQuery, JavaScript and PHP), but we recommend that you use some time and read up on one of the languages, to better understand what is going on in the examples. Our examples are simple, but you should be able to make great tools from them, without a lot of programming knowledge. You can navigate the documentation and find the right solution or parameter for your need.

Working with Endpoints

An API endpoint is the point of entry in a communication channel when two systems are interacting. It refers to touchpoints of the communication between an API and a server. The endpoint can be viewed as the means from which the API can access the resources they need from a server to perform their task. An API endpoint is basically a fancy word for a URL of a server or service.

We all know that APIs operate through ‘requests’ and ‘responses’. And when an API requests to access data from a web application or server, a response is always sent back. The location where the API sends a request and where the response emanates is what is known as an endpoint. Reputedly, the endpoint is the most crucial part of the API documentation since it’s what the developer will implement to make their requests.

HabboAPI got multiple endpoints, that you can use to look information about different Habbo items. Stuff like badges, furniture or clothing. You can chain up multiple parameters to get a different response, like the latest badge or a specific furniture.


Hopefully we will be able to add more endpoints in the future.

URL Parameters

URL parameters are options you can pass with the API endpoint (such as specifying the response format or the amount returned) to influence the response.

We got multiple URL parameters for each endpoint. Some endpoints got more than others, but we will work over time to get more added. You can find a list of them all and description on what they do, under each endpoint documentation.

URL parameters are placed after an endpoint in the call's URL. The URL parameter set should be separated from the endpoint by a "?" symbol. If you add more than one URL parameter they should be separated from each other by a "&" symbol. For example:


The example above, will result in 10 badges, discovered less than 24 hours ago.

Response Fields

Response fields are ‘objects‘ you use to extract a specific piece of data, from the JSON result. Response field objects are placed within your code, to call that information in the JSON result. If you for example want a list of badge URLs, you want to use the object named image. Or if you want the amount of owners on the badge, you use badge_owners.

Some response fields can also be used for manipulate the JSON result. For example if you want to use the pagination or if you use directions on furniture and clothing.

You can find a list of response fields for each API endpoint, on their documentation page.

What is next?

You are ready! Click yourself over to the first endpoint documentation and read what to do next and check our examples.

Documentation: Badges, Furniture, Lines, Clothing or Habbos.