# FUT GG EA FC Ultimate Team API

> FUT.GG: EA FC Ultimate Team player cards, trending SBCs and evolutions, live events and objectives

- Vendor: `futggeafcultimateteamapi` · version 1.0 · category Gaming · tags fut gg api, ea fc api, ultimate team api, fut players api, sbc api, fut evolutions api
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/futggeafcultimateteamapi
- This document: https://apiclay.com/docs/futggeafcultimateteamapi.md
- OpenAPI 3.1: https://apiclay.com/api/futggeafcultimateteamapi/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `futggeafcultimateteamapi`
- Updated: 2026-11-18

## About

## FUT GG EA FC Ultimate Team API

The data behind FUT.GG, the EA FC Ultimate Team database: every player card of a game with overall rating, rarity, card image and page link, 30 per page; the SBCs, evolutions and objectives the community votes as hot right now; the live events with their rules, rounds and objective groups; and the season's objectives campaign with every level, its XP and rewards.

Data comes from **fut.gg** (https://www.fut.gg). Every route calls the source's own public API and returns it unchanged.

Typical flow: `POST /players?page=1` with the body `{"game": "27"}`, `POST /whats-hot`, then `POST /live-events` and `POST /objectives` with the same body.

### Routes

#### POST `/players` - Players
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| game | body | string | yes | EA FC edition, e.g. `27`. |
| page | query | number | no | Page, from 1; 30 cards per page. |

Returns: `data` array of cards: `id`, `eaId`, `basePlayerEaId`, `commonName`, `cardName`, `overall`, `rarityName`, `slug`, `url`, `cardImageUrl`, `isEvolutionPlayerItem`, `chemistry`, colours; `total`, `currentPage`, `next`.

#### POST `/whats-hot` - Whats hot
No parameters.

Returns: `data`: `sbcs`, `evolutions` and `objectives`, each with `hotScore`, `votePercentage`, `wilsonScore` and the item itself.

#### POST `/live-events` - Live events
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| game | body | string | yes | EA FC edition, e.g. `27`. |

Returns: `data` array: `eaId`, `slug`, `name`, `description`, `competitionType`, `modeType`, `matchMode`, `gameLength`, `tags`, `startTime`, `endTime`, `requirementsText`, `objectivesGroup`.

#### POST `/objectives` - Objectives
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| game | body | string | yes | EA FC edition, e.g. `27`. |

Returns: `data`: the season campaign `id`, `name`, `startTime`, `endTime` and `levels` (`level`, `xp`, `isPremium`, `awards`).

### Caveats

- Player names, card art and game data belong to EA and their rights holders; FUT.GG compiles them.
- Upstream responses can change over time. Verify fields before relying on them.
- Not affiliated with or endorsed by fut.gg.

## Pricing

- Pay as you go: 0.01 credits/request
- Trial: 1 free requests per buyer
- Billing order: trial requests -> subscribed plan requests -> pay as you go. 1 credit's USD value is shown on the marketplace page.

## HTTP routes

Only the public, buyer-facing parts of each route are listed; vendor-side credentials stay on the gateway.

### POST /players — Players
- Gateway: `POST https://api.apiclay.com/v1/api/futggeafcultimateteamapi/players`
- Public query params: `page` (number)
- Public body fields: `game` (string, required)
- Body sample (JSON):

```json
{
  "game": "<game>"
}
```

- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### POST /whats-hot — Whats hot
- Gateway: `POST https://api.apiclay.com/v1/api/futggeafcultimateteamapi/whats-hot`
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### POST /live-events — Live events
- Gateway: `POST https://api.apiclay.com/v1/api/futggeafcultimateteamapi/live-events`
- Public body fields: `game` (string, required)
- Body sample (JSON):

```json
{
  "game": "<game>"
}
```

- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### POST /objectives — Objectives
- Gateway: `POST https://api.apiclay.com/v1/api/futggeafcultimateteamapi/objectives`
- Public body fields: `game` (string, required)
- Body sample (JSON):

```json
{
  "game": "<game>"
}
```

- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

## Call example

```bash
curl -X POST "https://api.apiclay.com/v1/api/futggeafcultimateteamapi/players" \
  -H "token: <YOUR_APICLAY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{ "game": "<game>" }'
```

Index of every published API: https://apiclay.com/llms.txt
