API · /habbo-api

Habbo Hotel API

healthy 3,097 Subscribers

Live player profiles from Habbo, the long-running virtual-world social platform, served straight from Habbo's official public API — no key, nothing cached. Habbo has been one of the largest teen virtual worlds for two decades, built around avatars, badges, groups and player-built rooms. The user endpoint returns a player's public profile: their avatar figure, motto, online status, member-since and last-online dates, level and total experience, and their hand-picked showcase badges — for example Puhekupla, a member since 2009. The profile endpoint returns the full social graph the player has made public: their groups, their player-built rooms, and their friend and badge counts. The badges endpoint returns every badge the player has earned with its code, name and description — dedicated collectors rack up hundreds. The avatar endpoint turns a player's figure string into ready-to-use avatar image URLs at several sizes and angles, straight from Habbo's imaging service. Every hotel is supported — the international .com plus the Brazilian, German, Spanish, Finnish, French, Italian, Dutch and Turkish hotels. Everything is live from Habbo, nothing stored. This is the Habbo social layer for any fan site, badge tracker, community tool or bot. Distinct from mainstream social-network APIs — this is the Habbo virtual world: avatars, badges, groups and rooms. 5 endpoints, no key on our side.

api.oanor.com/habbo-api
Get an API key Try in playground → Contact provider

Machine-readable spec so AI agents can integrate this API.

/api/habbo-api/openapi.json
/api/habbo-api/llms.txt

Discovery: GET /api/index.json lists every API.

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
468 ms
Server probes · 24h
Subscribers
3,097
active
Total calls
25
last 7 days
status Full status page → · 15 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 2,000 calls / month
  • 3 requests / second
  • Hard cap (429 above quota, no overage)
  • 2,000 calls/month
  • 3 req/sec
  • Profiles, badges, avatars
  • No credit card
Sign in to subscribe

Starter

€8.00 /month

  • 40,000 calls / month
  • 8 requests / second
  • Hard cap (429 above quota, no overage)
  • 40,000 calls/month
  • 8 req/sec
  • Social graph + all hotels
  • Email support
Sign in to subscribe

Pro

€21.00 /month

  • 220,000 calls / month
  • 20 requests / second
  • Hard cap (429 above quota, no overage)
  • 220,000 calls/month
  • 20 req/sec
  • Badge trackers & fan sites
  • Priority support
Sign in to subscribe

Mega

€49.00 /month

  • 1,200,000 calls / month
  • 50 requests / second
  • Hard cap (429 above quota, no overage)
  • 1,200,000 calls/month
  • 50 req/sec
  • Platform scale
  • Dedicated SLA
Sign in to subscribe

Built by

Related APIs

Other APIs with overlapping tags.

Wikipedia Trends API

Live readership-trend data from the Wikimedia Pageviews API — the official measure of what the world is reading on Wikipedia and its sister projects. See the most-viewed articles on any Wikipedia language edition for a given day (the daily trending list); pull the daily or monthly pageview trend for any single article over a date range; read a whole project's total pageviews over a range as a barometer of overall traffic; or rank several articles head-to-head by total views for topic-engagement comparison. Special / namespace pages (Main Page, Search, Portal…) are filtered out by default so the trending list is real articles. Read live from Wikimedia, nothing stored — data lags about 1-2 days, so ranges default to ending two days back. This is the Wikipedia readership-trend and topic-engagement layer for any trends, research, newsroom or analytics app — distinct from Wikipedia content APIs: this is the pageview, trending and engagement signal of what people are actually reading and how it changes.

api.oanor.com/wikitrends-api

PieFed API

Live community, post and user data from PieFed, an open-source threadiverse platform — a federated Reddit-style link aggregator in the fediverse — via the flagship piefed.social instance's public API. PieFed is organised into communities people subscribe to, where they post links and discussions that others up- and down-vote. List the platform's communities with their subscriber, post and comment counts. Get the feed of posts with each one's title, link, score, vote and comment counts, author and community. Read a single post in full. Read a member's profile with their post and comment counts and join date. Live, no key, nothing stored; to keep results work-safe, NSFW posts and communities are filtered out of the feeds. Distinct from Lemmy, Mbin and other aggregator APIs — this is the PieFed platform, its communities, posts and members. Perfect for social-reader, fediverse and community apps.

api.oanor.com/piefed-api

Wattpad API

Live data from Wattpad, the world's largest storytelling social platform where writers publish serialized fiction and millions of readers follow, vote and comment, served straight from Wattpad's public API — no key, nothing cached. The search endpoint finds stories by keyword, each with its read, vote and comment counts, part count, completion and maturity flags, tags and author — a popular dragon-romance pulls hundreds of thousands of reads. The story endpoint returns one story in full: its description, cover, the engagement counts, the number of parts, language, tags and the author with their follower count. The user endpoint returns a writer's profile: their follower and following counts, the number of stories they have published, their bio and location — Wattpad's own account has tens of millions of followers. The user-stories endpoint returns a writer's published stories with each one's stats. Everything is live from Wattpad, nothing stored. This is the web-fiction social layer for any reading, discovery, writing-community or recommendation app. Distinct from mainstream social and the book-catalog APIs — this is Wattpad's stories, their engagement and their authors. 4 endpoints, no key on our side.

api.oanor.com/wattpad-api

Coub API

Live looping-video data from Coub, the social platform built around short, seamlessly looping video clips, served straight from Coub's public API — no key, nothing cached. The explore endpoint returns the trending feed (rising, hot or random coubs across the whole site), each with its title, view, like and recoub counts, duration, channel and tags, plus ready-to-use loop-preview image URLs at several sizes. The tag endpoint returns the newest coubs for a tag — cats, gaming, music — the hashtag feed of Coub. The channel endpoint returns a creator's profile (title, follower and recoub counts) together with their most recent coubs. Every clip comes back cleaned up: the watch URL, the channel handle, the human tags and several preview-image sizes. Everything is live from Coub, nothing stored. This is the looping-video discovery layer for any feed, meme, moodboard, embed or social app. Distinct from YouTube, Vimeo, Dailymotion and other video APIs — this is Coub's looping clips by trend, tag and channel. 3 endpoints, no key on our side.

api.oanor.com/coub-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for Habbo Hotel API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Habbo Hotel API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Habbo Hotel API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does Habbo Hotel API cost?
Habbo Hotel API has a free tier with 100 calls / month. Paid plans start at €8.00 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is Habbo Hotel API GDPR-compliant?
All requests to Habbo Hotel API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.

Pick an endpoint from the list on the left to see its details and try it.

Code snippets

Sign up to get an API key, then call any path under your slug.

curl https://api.oanor.com/habbo-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/habbo-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/habbo-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
    "https://api.oanor.com/habbo-api/SOME_PATH",
    headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())

Ratings

Sign in to rate.

No reviews yet.

Discussion

Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.

Sign in to start a thread or reply.

Sign in

New thread

/ 4000

📌 Pinned 🔒 Locked

·

· ·

/ 4000

🔒 This thread is locked — no new replies.

  • No threads yet — start the discussion.

Support

Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.

Sign in to open a support ticket.

Sign in

Open new ticket

Describe what you need help with. The provider team gets an email and replies on the ticket page.

  • No tickets yet for this API.

Subscription active — calls can start immediately.

Send your first request —

Subscription active — copy a snippet and fire off your first call.