Free Fire Community API

Welcome to the Free Fire Community API - a comprehensive API service that provides access to Free Fire player statistics, craftland maps, wishlist data, and game assets.

View Full Documentation

Get Player Information

GET

/info

Retrieves comprehensive player information including profile data, rankings, badges, clan membership, pet information, and more.

Server

https://developers.freefirecommunity.com/api/v1

Full endpoint: https://developers.freefirecommunity.com/api/v1/info

Parameters

region

query

required

Region code (sg, ind, br)

uid

query

required

Player User ID (5-15 digits)

x-api-key

header

Your API key (recommended authentication method)

key

query

Alternative API key authentication in query string

Response Example

{
  "basicInfo": {
    "accountId": "10000001",
    "nickname": "Harold",
    "level": 65,
    "rank": 323,
    "region": "SG",
    "seasonId": 51
  },
  "captainBasicInfo": {
    "accountId": "310531180",
    "nickname": "GMAndrewYeti",
    "level": 68,
    "rank": 320,
    "region": "SG"
  },
  "clanBasicInfo": {
    "clanId": "1027439077",
    "clanName": "Cpt.BOOYAH",
    "clanLevel": 7,
    "memberNum": 40,
    "capacity": 55
  },
  "creditScoreInfo": {
    "creditScore": 100,
    "rewardState": 1,
    "rewardType": 2
  },
  "diamondCostRes": {
    "diamondCost": 390
  },
  "petInfo": {
    "id": "1300000071",
    "level": 7,
    "exp": 6000
  },
  "profileInfo": {
    "avatarId": "102000038",
    "clothes": [
      "214053001",
      "204053011"
    ]
  },
  "socialInfo": {
    "accountId": "10000001",
    "signature": "@freefireharold"
  }
}

Code Snippets

try {
  const url = 'https://developers.freefirecommunity.com/api/v1/info?region=sg&uid=10000001';
  const response = await fetch(url, {
    headers: {
      'x-api-key': 'YOUR_API_KEY',
      // Required: identify your app. Must NOT contain library/bot names
      // (axios, node-fetch, bot, etc.) or the firewall returns 403 (FW_002).
      'User-Agent': 'MyFreeFireApp/1.0 (+https://myapp.example.com)'
    }
  });
  if (!response.ok) {
    throw new Error(`HTTP error! status: ${response.status}`);
  }
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error('Error fetching data:', error);
}

Firewall & client requirements

To protect the API from scrapers and abuse, every request passes through an edge firewall before it reaches the endpoint. Server-side and bot integrations must follow these rules or they will receive a 403 before authentication even runs.

User-Agent header

Every request must send a User-Agent header that is at least 10 characters long.
The User-Agent must not contain HTTP library or automation names anywhere in the string. Blocked tokens include: python, requests, aiohttp, httpx, urllib, node-fetch, axios, got, undici, okhttp, java, curl, wget, bot, crawl, spider, scrapy, puppeteer, playwright, selenium, postman, insomnia, httpie. Note that 'bot' matches anywhere, including inside a URL (e.g. github.com/me/my-bot).
Default User-Agents from fetch, requests, Go, and curl are blocked. You must override the header explicitly in your HTTP client.

Recommended format: MyFreeFireApp/1.0 (+https://myapp.example.com)

Firewall error codes

Code	Status	Cause	Fix
`FW_001`	403	User-Agent header is missing or shorter than 10 characters.	Set a descriptive User-Agent of 10+ characters.
`FW_002`	403	User-Agent matches a known HTTP library or bot pattern.	Replace library/bot tokens with your own app identifier.
`FW_003`	403	User-Agent reports a very old browser version (likely a spoofed scraper).	Use a current browser UA or a custom app identifier.
`FW_004`	429	Too many requests from one IP in a short window (edge rate limit).	Slow down and retry after the Retry-After interval (60s).

Authentication & region

Preferred: send your key in the x-api-key request header.
Alternative: pass it as the key query parameter (e.g. ?key=ffc_...). Make sure parameters are separated by & so the key is parsed correctly.
The region parameter (sg, ind, br, and others) is a passthrough value and never affects authorization. Any plan authorized for an endpoint can use any region.