Free Fire Likes Generator API

The Free Fire Likes Generator API by HL Gaming Official is your long-term, reliable solution for automating daily like rewards in Free Fire. Built on secure HL GAMING OFFICIAL authentication and strict domain whitelisting, this API ensures:

Safe & Authentic: All requests use industry-standard HTTPS, HL GAMING OFFICIAL UID/API-key auth, and domain origin checks.
Long-Term Stability: Battle-tested endpoints engineered for continuous 24/7 operation—no rate spikes, no downtime.
Full HL Gaming Suite: One credential set powers a growing family of Free Fire APIs (avatars, outfits, stats, banners, likes).
Future-Proof: Backward-compatible upgrades, versioned endpoints, and proactive deprecation notices ensure seamless integration over time.

Whether you’re running a tournament platform, community bot, or loyalty program, our API delivers up to 100 guaranteed daily likes per UID—all while keeping your system secure and fully under your control.

Overview

The Free Fire Likes Generator API by HL Gaming Official enables your application to grant up to 100 likes per Free Fire UID every 24 hours, seamlessly and securely. Free Fire is one of the world’s most popular mobile battle‐royale games, with over 1 billion downloads on Google Play and more than 150 million daily active users. Despite its massive community, there is no official public API from Garena for automating in-game like rewards—this is where our service steps in.

Seamless Integration: Use either GET (query string) or POST (JSON body) requests to invoke the endpoint.
Usage Tracking: Every response includes usage.remainingToday so you can monitor quota consumption in real time.
Domain Whitelisting: Restrict access to only your approved domains, preventing unauthorized or malicious calls.
Guaranteed Reliability: Battle-tested 24/7 uptime ensures you never miss a rewards cycle for your players or community.

Why choose a third-party API?

Garena does not expose an official “likes” endpoint—community and tournament platforms must rely on trusted third-party solutions.
Our API abstracts away the complexity of reverse-engineering game servers, offering a simple, secure interface.
Built on top of HL GAMING OFFICIAL and hardened with strict rate-limits, domain checks, and logging, you can trust it for long-term, large-scale use.

🚫 API usage is currently limited to 25 requests per day on the free plan. This includes all actions such as ban status checks, rank lookups, and related endpoints. To raise the limit and unlock features like advanced rank data, ban history details, and real-time moderation, consider upgrading your plan.

🚨 Security Warning: Never expose your useruid or api key directly in client-side code (such as HTML, JavaScript, or public repositories). These credentials are sensitive and must be securely stored and handled on your server. If exposed, anyone could misuse your account, exhaust your API limits, or access protected data on your behalf.

✅ Happy News! The Free Fire Likes Generator API is normally available only on paid plans (Basic Starter or higher). However, you can receive **5 months of free access** by providing us with 50+ valid Free Fire guest accounts files. We’ve created a tutorial video showing how to generate and download guest files—submit them via the table below, then contact us directly and we’ll grant your free 5-month API access. Please note: sustaining and scaling this API incurs significant development and hosting costs, so paid subscriptions are appreciated.

Action	URL
Submit Guest Files	https://www.hlgamingofficial.com/p/guest-token-upload-give-us-guest.html
Contact Support	https://www.hlgamingofficial.com/p/contact-us.html

Authentication

Every request to the Free Fire Likes Generator API must be accompanied by two pieces of confidential information that uniquely identify and authorize your application. These credentials ensure that only approved clients—tied to your HL Gaming Official account—can grant in-game likes.

useruid — your unique HL Gaming Official user UID, assigned when you registered. This string ties every API call back to your account record in HL GAMING OFFICIAL and enables per-UID rate limiting, usage tracking, and logging.
api — your secret API key, also provisioned in your dashboard. This key must remain strictly confidential: anyone possessing it can exhaust your daily quota or impersonate your service.

Where and how to include these credentials

GET requests: Append both useruid and api as URL query parameters.
GET https://hl-gaming-official-ff-likes-devs.vercel.app/api/v1/data/likes?useruid=YOUR_UID&api=YOUR_KEY&region=AS&ff_uid=12345678
POST requests: Send a JSON body with keys useruid and api alongside your region and ff_uid fields.
{ "useruid": "YOUR_UID", "api": "YOUR_KEY", "region": "AS", "ff_uid": 12345678 }

Common pitfalls & troubleshooting

Typos & case-sensitivity: Both useruid and api are case-sensitive. Even a single character mismatch will result in “Auth Failed.” Always copy-and-paste or use a secure credential store.
Key rotation: If you regenerate your API key in the dashboard, remember to update it in every environment (development, staging, production). Old keys immediately become invalid.
Environment separation: Never hard-code credentials in client-side code. Use environment variables or a secure vault on your server, and never expose them to browsers or public repositories.
Invalid UID: The useruid must exactly match a registered HL GAMING OFFICIAL UID under your HL Gaming project. Mistyped or deleted UIDs will trigger “Auth Failed.”
Rate-limit vs. Auth failure: If you see an unexpected 403 error after many successful calls, verify whether you’ve inadvertently hit your plan limit (quota). Otherwise, re-check your credentials.

Security best practices

Use HTTPS exclusively to encrypt credentials in transit and prevent interception.
Store your API key and useruid in a secure server-side environment (e.g. AWS Secrets Manager, Vault).
Rotate your API key periodically (e.g. every 90 days) and immediately revoke any compromised key.
Limit access to credentials only to the microservice or server component that needs to call the API. Avoid broad access permissions.

Domain Restriction

To protect your API credentials and prevent unauthorized usage, the Free Fire Likes Generator API enforces strict Origin Domain validation. Only requests originating from domains you explicitly register in your HL Gaming Official dashboard will be honored. Any call coming from an unrecognized or unapproved domain will be rejected with a “Not Allowed” error.

🚫 Domain Restriction Active: Verify that the Origin or Referer header in your HTTP request matches one of your whitelisted domains.

How it works

When you register or update a domain in your dashboard, we store it in our secure configuration store.
Each incoming request’s Origin or Referer header is parsed, lower-cased, and compared against your list.(We Implemented Intelligent Security)
If no match is found, the API returns a 200 status with { "error": "Not Allowed" } to avoid exposing internal status codes.

Registering Your Domains

Log into the HL Gaming Official dashboard.
Navigate to Settings > Allowed Domains.
Enter each domain using the full hostname (e.g. api.yoursite.com), without protocol or path.
Click Save—your changes take effect immediately.

Tip: Include both www.yoursite.com and yoursite.com entries if your app uses both variants.

Troubleshooting Domain Errors

Missing or malformed header: Some clients strip the Origin header on non-browser calls—ensure your HTTP library sends it.
Port numbers: Ports (e.g. localhost:3000) must match exactly if you’re testing locally.
HTTPS enforcement: For production, always use https://—browsers suppress Origin on mixed-content requests.
Check dashboard: Confirm your domains are saved correctly—typos or trailing slashes will cause mismatches.

If an unauthorized domain attempts access, the API will respond with:

{
  "error": "Not Allowed"
}

Tip: For CLI testing, manually set the Origin header with curl using -H "Origin: https://api.yoursite.com".

Setup Guide

All developers must retrieve their unique credentials and configure domain access before making API requests. Use the official HL Gaming portal to complete the required setup steps.

Action	Purpose	Where to Do It
Get `useruid`	Your developer account ID—used to identify your project.	HL Gaming Official API Page
Get `api` key	Private key used for authenticating your requests.	HL Gaming Official API Page
Configure Domain Whitelisting	Restricts API access to trusted sources only.	Domain Whitelist Manager

🔐 Make sure your api key remains confidential and never exposed in front-end code. All credentials and settings can be managed securely via the HL Gaming portal.

Rate Limits & Plans

You may grant likes up to the following quotas per UID, every 24 hours (resets exactly 24 hours after your last successful claim):

Plan	Likes / 24h per UID	Price (USD/mo)
Free	0	$0
Starter	1,00	$19
Enterprise	Unlimited	Contact Sales

Quota Reset Details

The limitReset timestamp in your account indicates when your daily quota resets. After 24 hours from your last successful call, usedToday is reset to 0.

Supported Free Fire Regions

Specify the region parameter exactly as listed below (case-sensitive). Each code maps to a distinct Free Fire server cluster optimized for low latency.

Code	Name	Timezone	Notes
IND	India	GMT+5:30	Optimized for Indian ISPs (Jio, Airtel)
EU	Europe	GMT+1	EU & UK cluster
NP	Nepal	GMT+5:45	Dedicated Nepal servers
BD	Bangladesh	GMT+6	Optimized for Dhaka & Chittagong
SG	Singapore	GMT+8	SEA cluster (Singapore)
ME	Middle East	GMT+3	MENA region
TH	Thailand	GMT+7	Bangkok & Chiang Mai
VN	Vietnam	GMT+7	Hanoi & Ho Chi Minh City
ID	Indonesia	GMT+7	Jakarta & Surabaya
TW	Taiwan	GMT+8	Taipei cluster
RU	Russia	GMT+3	Moscow & St. Petersburg
PK	Pakistan	GMT+5	Karachi & Lahore
US	North America	GMT−5	US & Canada

IND — India

The India cluster serves the entire Indian subcontinent with GMT+5:30 timezone.

Player base: ~25 M daily.
Peak hours: 14:00–23:00 IST.
Optimized for Reliance Jio, Airtel, Vodafone networks.

EU — Europe

The Europe cluster (GMT+1) covers EU member states and the UK with low-latency routing.

Player base: ~20 M daily.
Peak hours: 18:00–02:00 CET.
Recommended for EU-wide tournaments.

NP — Nepal

The Nepal cluster (GMT+5:45) provides dedicated infrastructure for Nepalese players.

Player base: ~5 M daily.
Peak hours: 16:00–01:00 NPT.

BD — Bangladesh

The Bangladesh cluster (GMT+6) optimizes performance around Dhaka and Chittagong.

Player base: ~8 M daily.
Peak hours: 18:00–02:00 BDT.

SG — Singapore

Serving all Southeast Asia under the Singapore cluster (GMT+8).

Player base: ~50 M daily.
Peak hours: 12:00–22:00 SGT.

ME — Middle East

The Middle East cluster (GMT+3) serves MENA countries with sub-120ms latency.

Player base: ~8 M daily.
Peak hours: 20:00–02:00 AST.

TH — Thailand

The Thailand cluster (GMT+7) covers Bangkok, Chiang Mai, and the rest of Thailand.

Player base: ~7 M daily.
Peak hours: 17:00–23:00 ICT.

VN — Vietnam

The Vietnam cluster (GMT+7) provides localized servers for Hanoi, Ho Chi Minh City, and beyond.

Player base: ~9 M daily.
Peak hours: 17:00–23:00 ICT.

ID — Indonesia

The Indonesia cluster (GMT+7) optimizes for Jakarta, Surabaya, and other major cities.

Player base: ~15 M daily.
Peak hours: 18:00–02:00 WIB.

TW — Taiwan

The Taiwan cluster (GMT+8) ensures fast access for Taipei and surroundings.

Player base: ~5 M daily.
Peak hours: 13:00–22:00 CST.

RU — Russia

The Russia cluster (GMT+3) serves Moscow, St. Petersburg, and Western Russia.

Player base: ~12 M daily.
Peak hours: 18:00–02:00 MSK.

PK — Pakistan

The Pakistan cluster (GMT+5) covers Karachi, Lahore, and Islamabad.

Player base: ~6 M daily.
Peak hours: 17:00–23:00 PKT.

US — North America

The North America cluster (GMT−5) serves US and Canada data centers on East & West coasts.

Player base: ~15 M daily.
Peak hours: 16:00–00:00 EST.

⚠️ Access Requirement: This API is not free—your account must be on at least the Basic (Starter) plan to use it. Region codes are case-sensitive; if you supply an invalid or mismatched code you may see errors such as Missing parameters. or Auth Failed.

Endpoint URL

https://hl-gaming-official-ff-likes-devs.vercel.app/api/v1/data/likes

Accepts both GET and POST.

Parameters

Parameter	Required	Type	Description
`useruid`	Yes	string	HL GAMING UID for auth
`api`	Yes	string	Secret API key
`region`	Yes	string	Server code (e.g. `PK`)
`ff_uid`	Yes	number	Free Fire player UID

Parameter Notes

Case-sensitive. Missing/invalid = { "error": "Missing parameters." }.
Extra parameters are ignored.

Request Examples

POST

curl -X POST https://hl-gaming-official-ff-likes-devs.vercel.app/api/v1/data/likes \
  -H "Content-Type: application/json" \
  -d '{
    "useruid":"abc123UID",
    "api":"yourApiKey",
    "region":"PK",
    "ff_uid":8651617771
}'

GET

curl "https://hl-gaming-official-ff-likes-devs.vercel.app/api/v1/data/likes?useruid=abc123UID&api=yourApiKey&region=PK&ff_uid=8651617771"

Response Schema

{
  "source":"HL Gaming Official",
  "endpoint":"data/likes",
  "result":{
    "LikesAfterCommand":number,
    "LikesBeforeCommand":number,
    "LikesGivenByAPI":number,
    "PlayerNickname":string,
    "TokensUsed":number,
    "UID":number,
    "status":number
  },
  "message":string,
  "usage":{
    "usedToday":number,
    "dailyLimit":number,
    "remainingToday":number
  }
}

Field Descriptions

result.LikesGivenByAPI: Likes granted this call.
result.status: 1=success, 2=already claimed.
message: User-friendly text.
usage.remainingToday: Likes left for UID today.

Example Responses

Already Claimed

{
  "source":"HL Gaming Official",
  "endpoint":"data/likes",
  "result":{
    "LikesAfterCommand":6233,
    "LikesBeforeCommand":6233,
    "LikesGivenByAPI":0,
    "PlayerNickname":"PlayerOne",
    "TokensUsed":41,
    "UID":8651617771,
    "status":2
  },
  "message":"Hello PlayerOne, it looks like you've already claimed your daily likes within the last 24 hours. Please try again after 24 hours. Thank you for understanding!",
  "usage":{"usedToday":53,"dailyLimit":100,"remainingToday":47}
}

Successful Grant

{
  "source":"HL Gaming Official",
  "endpoint":"data/likes",
  "result":{
    "LikesAfterCommand":6233,
    "LikesBeforeCommand":6193,
    "LikesGivenByAPI":40,
    "PlayerNickname":"PlayerOne",
    "TokensUsed":41,
    "UID":8651617771,
    "status":1
  },
  "message":"Hello PlayerOne, you’ve successfully received 40 new likes! You had 6193 before, and now you have 6233. Thank you for choosing HL Gaming Official!",
  "usage":{"usedToday":52,"dailyLimit":100,"remainingToday":48}
}

Error Responses

400 Bad Request – Missing Parameters

Returned when one or more required parameters are absent or empty.

{ "error": "Missing parameters." }

Ensure useruid, api, region, and ff_uid are all provided.
All parameters are case-sensitive and must not be null or empty strings.

403 Forbidden – Auth Failed

Indicates that either your useruid or api key is invalid.

{ "error": "Auth Failed" }

Verify you’re using the correct HL GAMING OFFICIAL UID (useruid).
Double-check that the api key matches exactly what’s in your HL Gaming Official dashboard.
If you recently rotated keys, ensure you’ve updated them in your code.

403 Forbidden – Upgrade Plan

You’ve hit a plan restriction (e.g. using the Free/Starter plan but calling an endpoint that requires Basic or higher).

{ "error": "Upgrade Plan" }

The Basic (Starter) plan grants up to 100 likes/UID per 24 h.
If you need more (e.g. Pro: 1,000/UID or Enterprise: Unlimited), upgrade via your dashboard.
Visit “Billing & Plans” in the HL Gaming Official portal to adjust your subscription.

403 Forbidden – Not Allowed

The request’s origin domain isn’t on your whitelist.

{ "error": "Not Allowed" }

Go to “Allowed Domains” in your dashboard and add the calling domain (including protocol).
Remember to include both https:// and http:// variants if needed in testing.

429 Too Many Requests – Quota Exceeded

Your UID has already claimed the maximum likes for the current 24 h window.

{ "error": "Quota exceeded." }

Check usage.remainingToday to monitor your remaining balance before calling.
Quota resets exactly 24 h after your last successful call (see limitReset in your account data).
Consider upgrading your plan for a higher daily allowance.

500 Internal Server Error – Server Error

An unexpected error occurred on our side.

{ "error": "Something went wrong. Please try again later." }

No action required on your end—this is a transient issue.
Retry after a brief wait (e.g. 30–60 seconds).
If the problem persists, contact support with the timestamp and any request IDs.

Best Practices

Secure your useruid and api on server side only.
Monitor usage.remainingToday to avoid surprises.
Implement retry with exponential backoff on errors.
Cache identical calls within minutes to reduce load.
Maintain consistent domain configuration in your dashboard.

Security Recommendations

Store API keys in environment variables—not in code.
Rotate and revoke keys periodically.
Enforce HTTPS for all calls.
Validate inputs server-side before forwarding.

Logging & Analytics

Every request is logged with:

method, endpoint, query
timestamp, status, usedToday
timezone (America/Los_Angeles)

Use logs to audit usage patterns and detect anomalies.

FAQ

Q: Can I claim likes twice in 24 hours?: A: No—each UID can claim only once per rolling 24-hour window.
Q: How is the window determined?: A: It resets exactly 24 hours after your last successful claim (limitReset timestamp).
Q: What if the Free Fire API is down?: A: You’ll receive a generic server error. Please retry after a short delay.
Q: How to upgrade my plan?: A: Visit your HL Gaming Official dashboard and select “Upgrade Plan.”

Changelog

v1.2.0 – Added supported regions table and detailed notes.
v1.1.0 – Enhanced error response details, professional messaging.
v1.0.0 – Initial launch: daily 100 likes generator.

Support

If you need assistance:

Email: support@hlgamingofficial.com
Open a ticket via your dashboard’s “Help & Support” section.