PUBG API

Name: PUBG API
Brand: PUBG API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIOTSensor Databearer13 EndpointsREST

Install Jentic One Beta

Connect the PUBG API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PUBG API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with PUBG API.

Get players

Access PUBG API resources via REST API

Use Cases

Patterns agents use PUBG API for, with concrete tasks.

GET STARTED

Start building with PUBG API

Explore with Jentic

View OpenAPI Document

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.

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.

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

Key Endpoints

13 endpoints — 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.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

PUBG API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'get players') and Jentic returns the matching PUBG API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct PUBG API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using PUBG API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.

PUBG API

Connect the PUBG API to your agent

Capabilities

Use Cases

Start building with PUBG API

Key Endpoints

Why Jentic?

Related APIs

FAQs