Endpoints¶
This page describes all endpoints that the KRFN app connects to.
In-game¶
krr-prd.star-api.com (API endpoint)¶
Main APIs endpoint. This domain includes all game APIs used in the game.
Request example¶
GETkrr-prd.star-api.com/api/version/app/getGETkrr-prd.star-api.com/api/player/get_allPOSTkrr-prd.star-api.com/api/player/quest_log/order
Parameters¶
See api-encryption.
asset-krr-prd.star-api.com (Asset endpoint)¶
Asset files endpoint. This domain provides the game asset files.
Request example¶
- Basic
asset-krr-prd.star-api.com/[bundleHash]/[platform]/[folder name hash]/[file name hash] - Cri files
asset-krr-prd.star-api.com/[bundleHash]/CRI/cv.b
Parameters¶
See assets-bundles.
Dynamic Endpoint Override¶
The game client supports dynamic endpoint overriding at startup. By returning a specific response from the app version check API (/api/app/version/get), you can force the client to update its target API and asset endpoints in memory for the current session without modifying configuration files on the device.
How it works¶
When the client boots and requests GET /api/app/version/get, the API can return a result code of 2 (APPLYING) along with the override URLs.
Response Payload (JSON Example)¶
{
"resultCode": 2,
"applyUrl": "https://custom-api-server.com/api/",
"applys3Url": "https://custom-asset-server.com/bundleHash/"
}
Client-side Behavior¶
Upon receiving the APPLYING (code 2) result, the client dynamically updates its in-memory connection endpoints for the current session:
- API Endpoint: Overridden by
applyUrl. - Asset Endpoint: Overridden by
applys3Url.
Consequently, all subsequent API requests and asset downloads are seamlessly routed to these newly specified URLs.
Web¶
These endpoints are used for displaying information such as news, updates, and gachas.
kirara.star-api.com¶
Main info pages.
Links¶
- Wayback machine
- First screen at login
- Gacha pages
- Terms of Uses
- Help
krr-prd-web.star-api.com¶
Gacha rates/details, terms of use, legal notices, and help documents.
Links¶
Differences between Web Domains¶
Although both domains serve web content to the client's internal WebViews, they are decoupled for traffic handling, server-side dynamic processing, and operational boundaries:
| Metric / Aspect | kirara.star-api.com |
krr-prd-web.star-api.com |
|---|---|---|
| Primary Content | Main game news, maintenance notifications, and application updates. | Gacha drop rates/details, terms of use, legal notices, and help documents. |
| Traffic Profile | High peak traffic at startup and during login (polled by all active clients). | Scattered traffic triggered by specific user interactions inside the game. |
| Caching (CDN) | Heavily cached (e.g., via CloudFront) to survive sudden load spikes. | Low caching or dynamic routing to handle query parameters (e.g., gachaID). |
| Service Availability | Must remain online even during database or game API maintenance. | Can be shut down or limited during maintenance without blocking user notice displays. |
| Owner / Supervisor | Game Operations (CMS-based rapid announcements). | Publisher/Legal team (strictly audited policy files and gacha configurations). |
kirarafantasia.com¶
Official website. Includes the "jail" screen (ROOT or jailbreak detected! screen).