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

# PUBG API

The official PUBG API provides programmatic access to in-game PUBG data including player stats, match data, season statistics, leaderboards, weapon mastery, survival mastery, and telemetry. Data is formatted using the JSON:API specification. The API exposes 13 endpoints secured with bearer authentication.

## For AI agents

Programmatically get players, get a single player. Covers 13 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for iot and hardware only.

## Capabilities

- Get players
- Access PUBG API resources via REST API
- Access PUBG API resources via REST API

## Use cases

### IoT and Hardware Operations

Use the PUBG API to perform iot operations programmatically. The API provides 13 endpoints covering core functionality including get players, get a single player, get seasons.

Example prompt: Call GET `/shards/{platform}/players` to get players

### Automated Players Management

Automate players operations by combining multiple PUBG API endpoints. Agents can get a single player and then get seasons in a single workflow.

Example prompt: Call GET `/shards/{platform}/players/{playerId}` to get a single player, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call PUBG API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'get players', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/shards/{platform}/players` | Get players |
| GET | `/shards/{platform}/players/{playerId}` | Get a single player |
| GET | `/shards/{platform}/seasons` | Get seasons |
| GET | `/shards/{platform}/players/{playerId}/seasons/{seasonId}` | Get player season stats |
| GET | `/shards/{platform}/players/{playerId}/seasons/{seasonId}/ranked` | Get player ranked stats |
| GET | `/shards/{platform}/players/{playerId}/seasons/lifetime` | Get player lifetime stats |
| GET | `/shards/{platform}/seasons/{seasonId}/gameMode/{gameMode}/players` | Get batch season stats |
| GET | `/shards/{platform}/matches/{matchId}` | Get a match |

## Key resources

- **Players** — Player lookup and search
- **Seasons** — Season information
- **Stats** — Player season and lifetime statistics
- **Matches** — Match data and details
- **Leaderboards** — Ranked leaderboards

## Why Jentic

- **Setup:** Wiring the PUBG API by hand means setting bearer auth, choosing the right platform shard, and threading player, season, and match ids through each call yourself. Through Jentic you install once, import the PUBG API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The PUBG API is read-only, with the player and match ids in the URL path (`/shards/{platform}/players/{playerId}`), so a rule can pin your agent to reading a specific player's stats. Every operation in this spec is a lookup, and you decide which ones the agent may call.
- **Credential handling:** Your PUBG API token 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 a player by id' or 'read season stats for a player', and Jentic returns the matching PUBG operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Complementary API for broader integration workflows
- **Twilio** — Complementary API for broader integration workflows
- **Sendgrid** — Complementary API for broader integration workflows

## FAQ

### What authentication does the PUBG API use?

The PUBG API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get players with the PUBG API?

Yes. Use the GET `/shards/{platform}/players` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

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

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get players through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get players'. Jentic returns the matching PUBG API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the PUBG API have?

The PUBG API exposes 13 endpoints covering players, seasons, stats operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which PUBG operations and credentials the agent may use. The PUBG API is entirely read-only lookups, and since the player and match ids sit in the URL path such as `/shards/{platform}/players/{playerId}`, you can pin the agent to reading a specific player's stats or matches. You choose exactly which endpoints, from get players to get season and lifetime stats, the agent is allowed to call.