canonical: https://jentic.com/apis/pubg.com/pubg

# PUBG API

Jentic publishes the only available OpenAPI specification for PUBG API, keeping it validated and agent-ready. The PUBG API returns in-game PUBG: Battlegrounds data for players on the steam, kakao, xbox, psn, stadia, and tournament shards: player lookups, season, ranked, and lifetime stats, match details, weapon and survival mastery, and leaderboards per season and game mode. Responses follow the JSON:API specification, and a sample endpoint returns a random set of recent match ids for bulk analysis.

## For AI agents

Look up PUBG players by name or id, then read their season, ranked, and lifetime stats, weapon and survival mastery, and match details. Also returns leaderboards per season and game mode on each platform shard.

## Scope

Does not handle game purchases, account management, or other games' stats. Use for reading PUBG: Battlegrounds player, match, and leaderboard data only.

## Capabilities

- Look up up to 10 PUBG players at once by name or account id on a platform shard
- Read a player's season, ranked, and lifetime stats, or batch season stats for up to 10 players in one game mode
- Fetch a match by id with its rosters
- Retrieve weapon mastery and survival mastery progress for a player
- Get the leaderboard for a season and game mode such as squad-fpp, paged with page[number]
- Pull a sample of recent match ids from a createdAt start time for bulk match analysis

## Use cases

### Agent-built PUBG performance reports

A Discord bot or coaching assistant can resolve a player name to an account id, read the matches list on the player record, fetch each match, and combine that with season and lifetime stats to explain how the player is trending. The PUBG API answers per platform shard, so the agent includes steam, xbox, psn, or kakao in the path to read the right account.

Example prompt: Look up player name shroud on the steam shard with filter[playerNames], then get the current season id and return that player's squad-fpp season stats

### Season leaderboards and team scouting

Community sites and esports scouts track the strongest players per mode. The leaderboard operation returns ranked players for a seasonId and gameMode from solo to squad-fpp, and the batch season stats operation pulls stats for up to 10 player ids in one request, so a roster can be compared without a call per player.

Example prompt: Get the leaderboard for the current season with gameMode squad-fpp on steam, then batch fetch season stats for the first 10 player ids

### Bulk match sampling for analysis

Analysts studying the meta need many matches, not one player's history. The samples operation returns a random set of recent match ids, optionally from a filter[createdAt-start] time, which a pipeline then expands with the match operation to study placement, kills, and survival across a broad player base.

Example prompt: Fetch match samples on the steam shard from filter[createdAt-start] 2026-11-11T00:00:00Z and retrieve the first five matches by id

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/shards/{platform}/players` | Find players by name or id |
| GET | `/shards/{platform}/players/{playerId}/seasons/{seasonId}` | Get player season stats |
| GET | `/shards/{platform}/players/{playerId}/seasons/lifetime` | Get player lifetime stats |
| GET | `/shards/{platform}/matches/{matchId}` | Get a match |
| GET | `/shards/{platform}/leaderboards/{seasonId}/{gameMode}` | Get a leaderboard |
| GET | `/shards/{platform}/players/{playerId}/weapon_mastery` | Get weapon mastery |
| GET | `/shards/{platform}/samples` | Get match samples |

## Key resources

- **Players** — PUBG accounts on a platform shard, found by name or id
- **Seasons and stats** — Season, ranked, and lifetime stats per player and game mode
- **Matches** — Single match records with their rosters
- **Mastery** — Weapon mastery and survival mastery progress
- **Leaderboards** — Ranked players per season and game mode
- **Samples** — Random sets of recent match ids

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 61 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 75 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 42 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/pubg.com/pubg/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the PUBG API by hand means attaching its API key as a Bearer token, parsing its JSON:API responses, and resolving player names to account ids before any stats call. Through Jentic you install once, import PUBG from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The PUBG API puts the platform shard and player id in the URL path (`/shards/{platform}/players/{playerId}/...`), so a rule can pin your agent to one shard or one player account and the operations you pick. The spec contains read operations only, and you choose which lookups the agent may call.
- **Credential handling:** Your PUBG API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get PUBG player stats' or 'show the season leaderboard', and Jentic returns the matching PUBG operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Riot Games API** — Riot's API returns player, match, and ranked data for League of Legends and other Riot titles.
- **Halo Stats API** — The Halo Stats API serves match history and service records for Halo players.
- **Discord API** — Discord is where most PUBG stats bots post their results.

## FAQ

### Why is there no official OpenAPI spec for PUBG API?

PUBG documents its API on the PUBG Developer Portal but does not publish a machine-readable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the PUBG API via structured tooling. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### What authentication does the PUBG API use?

The PUBG API authenticates with an API key sent as a Bearer token in the Authorization header, per its OpenAPI spec. The GET /status check needs no key. Through Jentic the key is stored once and injected at call time, so it never appears in your agent's prompt or logs.

### Can I look up several PUBG players in one request?

Yes. GET `/shards/{platform}/players` accepts comma-separated values in filter[playerNames] or filter[playerIds], up to 10 per request. For stats, GET `/shards/{platform}/seasons/{seasonId}/gameMode/{gameMode}/players` returns season stats for up to 10 player ids in one game mode.

### What are the rate limits for the PUBG API?

The OpenAPI spec defines a rate-limited response but does not state the limit itself. Check the PUBG Developer Portal at https://developer.pubg.com for the limit attached to your API key.

### How do I get a player's season stats with the PUBG API through Jentic?

Search Jentic for 'get PUBG player season stats', which returns GET `/shards/{platform}/players/{playerId}/seasons/{seasonId}` with its input schema. Resolve the player id first with the players lookup and the season id from GET `/shards/{platform}/seasons`, then call it.

### Is there a PUBG MCP server?

You don't need an MCP server to give your agent the PUBG API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, finding each operation by intent instead of loading a full tool list into its context.

### Can I limit what my agent is allowed to do with the PUBG API?

Yes. Write a rule that allows only the season and lifetime stats operations under `/shards/steam/players/{playerId}`, naming one account id, so a personal stats bot reads that player and nothing else, and every call it makes is logged.