canonical: https://jentic.com/apis/skynewz-api-fortnite.herokuapp.com/skynewz-api-fortnite-herokuapp

# Skynewz Api Fortnite FORTNITE REST API

REST API about Fortnite game. The API exposes 9 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get fortnite game status, get fortnite news. Covers 9 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Get Fortnite game status
- Manage developer tools data programmatically
- Integrate FORTNITE REST API into automated workflows
- Query and filter FORTNITE REST API records by parameters
- Monitor FORTNITE REST API operational status and events

## Use cases

### Developer Tools Operations

Use the FORTNITE REST API to perform developer tools operations programmatically. The API provides 9 endpoints covering core functionality including get fortnite game status, get fortnite news, get a bearer token.

Example prompt: Call GET /check to get fortnite game status

### Automated Security Management

Automate security operations by combining multiple FORTNITE REST API endpoints. Agents can get fortnite news and then get a bearer token in a single workflow.

Example prompt: Call GET /news to get fortnite news, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call FORTNITE REST 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 apiKey tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/check` | Get Fortnite game status |
| GET | `/news` | Get Fortnite News |
| POST | `/oauth/token` | Get a Bearer token |
| GET | `/pve/info` | Get Fortnite PVE Info (storm, etc) |
| GET | `/pve/user/{username}` | Get PVE Stat by given username |
| GET | `/stats/id/{plateform}/{id}` | Get user's stats by user id |
| GET | `/stats/{plateform}/{username}` | Get user's stats by username |
| GET | `/store` | Get Fortnite Store |

## Key resources

- **Security** — How to access to this API
- **User** — Get user info
- **Stats** — Get all you Fornite stats
- **Check** — Get Fortnite status
- **PVE** — Get all your PVE Stats

## 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:** 50 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 87 / 100
  - Developer Experience & Jentic Compatibility: 65 / 100
  - AI-Readiness & Agent Experience: 26 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 60 / 100
- **View full report:** https://jentic.com/apis/skynewz-api-fortnite.herokuapp.com/skynewz-api-fortnite-herokuapp/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 FORTNITE REST API by hand means sending an Authorization header token to the skynewz-api-fortnite.herokuapp.com host and handling the stats, PvE, and store calls yourself. Through Jentic you install once, import the FORTNITE REST API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** This API puts the player username and id in the URL path (`/stats/{plateform}/{username}` and `/pve/user/{username}`), so a rule can pin your agent to specific player lookups. You choose the operations it may call, so if you only grant stats reads, the news and store operations are not included unless you add them.
- **Credential handling:** Your FORTNITE REST 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 a player's stats' or 'fetch the item store', and Jentic returns the matching FORTNITE REST API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the FORTNITE REST API use?

The FORTNITE REST API uses an API key passed 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 fortnite game status with the FORTNITE REST API?

Yes. Use the GET /check endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the FORTNITE REST 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 fortnite game status through Jentic?

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

### How many endpoints does the FORTNITE REST API have?

The FORTNITE REST API exposes 9 endpoints covering security, user, stats operations.

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

Yes. Jentic One runs self-hosted, so your own rules decide which FORTNITE REST API operations and credentials your agent may use. You pick the operations it can call, so granting only the stats reads such as GET `/stats/{plateform}/{username}` and GET `/pve/user/{username}` leaves the news and store endpoints off-limits until you add them. Because the player username and id sit in the URL path, you can pin the agent to specific player lookups rather than open-ended access.