Direct answer

Resolve the supported platform shard and account, fetch an available match and follow its related telemetry asset URL. Index included resources by type and ID instead of counting them as players. Preserve match metadata separately from telemetry so a failed download can be retried without repeating every lookup.

Vehicles crossing open terrain
Vehicles crossing open terrain · PUBG: BATTLEGROUNDS — PUBG Corporation / KRAFTON, Inc. · Source page ↗

Resolve account and shard

Start with the platform shard supported by the official API and the account you need. Display names are lookup inputs, not permanent database keys. Store the returned account identifier with its platform. If lookup is empty, check spelling and platform before declaring a player inactive. Keep bearer tokens in a private local or server environment, outside public HTML and JavaScript.

Join resources through relationships

Do not count every included object as a player. Rosters group participants; a participant represents a player’s appearance in this match. Build indexes by resource type and ID, then follow the relationships. An asset, roster and participant are different records even when they appear in the same response. Preserve the original response while testing your joins.

A motorcycle jump near traditional buildings
A motorcycle jump near traditional buildings · PUBG: BATTLEGROUNDS — PUBG Corporation / KRAFTON, Inc. · Source page ↗

Use the returned asset URL

Find the match’s related telemetry asset and use its URL; do not construct an address from a date and match ID. The official telemetry overview says the asset download does not need an API authorisation header. Store the match response and telemetry document as separate inputs so a failed download does not discard the metadata you already retrieved.

Handle failure at the correct stage

A failed player lookup is not a reason to retry telemetry. If the match succeeds but the asset download fails, retry only that stage with a bounded policy. Read API rate-limit headers and current documentation instead of copying a fixed request quota. Distinguish empty results, HTTP errors and invalid JSON in logs so later investigation starts at the right step.

Validate resource identity before joining

Inspect the response's top-level type, ID and relationships. Build separate indexes for participants, rosters and assets. Follow the match's roster relationship and each roster's participant relationship before attributing a player to a team. Missing referenced resources should create an explicit validation result rather than silently becoming an empty team. Store the original IDs alongside derived tables. If a later aggregation doubles players, compare the join path with the source response before blaming telemetry. A match resource and a telemetry event document are different inputs and need different parsers.

Retry the failing stage, not the whole pipeline

Log the request stage, HTTP status and resource ID without logging bearer tokens. Distinguish an unavailable match, a rate-limited request, an asset transfer failure and invalid JSON. Use documented response information for bounded retries. The official telemetry overview says the asset download does not require the API authorization header; avoid sending the token to arbitrary asset hosts. A successful HTTP response still needs its expected shape validated. Cache the match metadata so retrying telemetry does not require re-resolving the player. Never ask a visitor to paste an API secret into a public static page.

Worked decision example

Illustrative flow: player lookup succeeds, match metadata succeeds, telemetry transfer fails. Preserve the first two results and retry only the asset request under a bounded policy. If the asset later parses, validate that it belongs to the intended match before computing anything.

Scope and evidence

Check your installed build, platform and available features. Historical announcements explain their stated version; practical examples are illustrative, not claimed playtests.

Next time you play

  1. Keep tokens private.
  2. Join by resource type and ID.
  3. Use the returned telemetry URL.

Selected official references

  1. Matches endpoint ↗Collected on November 16, 2026
  2. Players endpoint ↗Collected on November 16, 2026
  3. Telemetry overview ↗Collected on November 16, 2026
  4. API rate limits ↗Collected on November 16, 2026
  5. Making requests ↗Collected on November 16, 2026

A source is not a promise that an old feature is unchanged. Follow the current in-game description when details differ.