What ID Game Checker does and who it is for

When a top-up site asks a customer for their Free Fire ID before selling them diamonds, it needs a fast way to confirm that ID actually maps to a real account — and ideally display the username back to the customer for confirmation. That is the exact workflow ID Game Checker is built for. You pass a player ID (and sometimes a server or zone ID) to a dedicated endpoint and get the corresponding username back. No authentication against the game itself, no scraping logic on your side — the API handles the lookup.

The practical audience is narrow but well-defined: developers building top-up or gifting storefronts, gaming community tools, or account-verification flows for any of the supported titles. If you operate outside that niche — say, you want match history, leaderboard data, or item inventories — this API does not cover those use cases.

Important deprecation notice: the marketplace listing is officially deprecated. New subscribers are directed to subscribe directly at neferbyte.com. Indonesian users and anyone preferring IDR, PayPal, or e-wallet payments can reach the developer at [email protected] or via WhatsApp. The API itself remains operational (health status available at api.neferbyte.com/status/), but future updates will flow through the provider's own platform.

Endpoint walkthrough

ID Game Checker exposes 63 endpoints in total, grouped loosely by game category. The pattern is consistent across almost all of them: a GET request with the player ID embedded directly in the path.

Battle royale and mobile shooters

The most commercially relevant endpoints are here. GET /ff-global/{id} returns the username for a Free Fire Global account; a separate /free-fire/{id} endpoint handles Free Fire Indonesia. BGMI uses /bgmi/{id}, PUBGM Global has its own endpoint, and Call of Duty Mobile (Garena) is covered via /cod-mobile/{id}. These are single-parameter calls — straightforward to integrate.

Games requiring a server parameter

Some games partition players by server or zone, so the endpoint signature changes:

  • GET /mobile-legends/{id}/{server} — Mobile Legends Bang Bang, arguably the most popular mobile MOBA in Southeast Asia
  • GET /tom-and-jerry-chase/{id}/{server}
  • GET /mu-devils-awaken/{id}/{server}
  • GET /opm-the-strongest/{id}/{zone_id} — One Punch Man: The Strongest uses a zone ID rather than a server name

When integrating these, your front-end needs to collect both the ID and the correct server/zone value from the user. The extra parameter is important: submitting the wrong server for a Mobile Legends account will either return no result or the wrong username.

Streaming and live-chat platforms

A substantial chunk of the endpoint list covers live-streaming and social platforms: Bigo Live, Nimo TV, Likee, Poppo Live, and about fifteen others. The entire group is currently flagged as under maintenance, meaning these endpoints may return errors or incomplete data. Do not build production features around them without confirming their current status directly with the provider.

Supercell titles

Endpoints for Clash of Clans, Clash Royale, Brawl Stars, and Hay Day are listed but marked not available. Supercell's own official API exists for these games, and it is worth going directly to that rather than waiting for this coverage to resume.

Pricing breakdown

Plan Price Included requests Overage Rate limit
BASIC $0 / month 300 per month — —
PRO $7.99 / month 1,000 per day $0.0010 / req 3 req/s
ULTRA $14.99 / month 2,500 per day $0.0010 / req 10 req/s
MEGA $25 / month 44,443 per day $0.0005 / req —

The BASIC tier gives 300 requests per calendar month — enough for local development and testing, but not for any live customer-facing flow. A busy top-up site processing even 15 transactions per day would exhaust it in 20 days.

PRO and ULTRA are daily-quota plans. At 1,000 requests per day, PRO supports a modest store. The $0.001 overage on both plans means a spike of 500 extra calls costs $0.50 — predictable and cheap. ULTRA's 10 req/s rate limit is meaningfully higher than PRO's 3 req/s if you need to handle bursts.

MEGA (the provider-recommended plan at $25/month) offers 44,443 daily requests — roughly 1.37 million per month — at half the overage rate ($0.0005 per request). For a high-volume top-up platform, the per-request cost at MEGA is significantly better than PRO or ULTRA even before considering the higher included quota.

Practical use cases

Top-up validation UX: Before displaying a payment form, call the relevant endpoint with the customer's game ID. If it returns a username, show it to the user (