# GET /v2/fixtures/{id}/players/{playerId}/actions

Group: Fixtures

A pitch-located log of one football player’s on-ball involvement in the fixture: passes and crosses (start → end, completion, key pass, long ball), take-ons, ball carries and defensive work (tackles, interceptions, ball recoveries, clearances, blocks). Available on Pro, Business and Enterprise plans.

Plans: Requires Pro, Business or Enterprise; a Free or Starter key receives 403 endpoint_not_in_plan.

Note: Football only, in covered leagues. A player who did not play, a fixture yet to kick off and any other sport all return 200 with empty lists. Coordinates run 0–100 in the player’s attacking direction (x 0 is the player’s own goal line, x 100 the goal they attack), the same frame as the heatmap. successful lines up with the accurate / won figures in the lineups’ statistics and is null on ball carries. The source supplies no timestamps, so actions follow the source’s own ordering.

## Parameters

| Name | In | Required | Description |
| --- | --- | --- | --- |
| `id` | path | yes | fixture id issued by DataSportsAPI, a positive integer |
| `playerId` | path | yes | player id issued by DataSportsAPI, for example taken from /lineups |

## Response

- `data`: `PlayerActions`
- `meta`: playerId, count (total actions)
- Objects: PlayerActions (https://datasportsapi.com/markdown/reference.md#playeractions)

## Errors

- 403 history_not_in_plan — kick-off falls before the start of your plan’s history window
- 404 not_found — the fixture id or player id is unknown

Plus the common errors (https://datasportsapi.com/markdown/docs.md#errors).

## Request

cURL:

```bash
curl -H "Authorization: Bearer sk_live_…" \
    "https://api.datasportsapi.com/v2/fixtures/{id}/players/{playerId}/actions"
```

TypeScript:

```ts
const { data, meta } = await client.fixtures.playerActions(id, playerId);
```

Python:

```python
res = client.fixtures.player_actions(id, player_id)
```

Go:

```go
res, err := client.Fixtures.PlayerActions(ctx, id, playerId)
```

CLI:

```bash
$ dsa fixtures player-actions <id> <playerId>
```

## Example response

```json
{ "data": {
    "passes": [ { "type": "pass", "start": { "x": 27.7, "y": 96 }, "end": { "x": 23.3, "y": 94.8 }, "successful": true, "keyPass": false, "longBall": false },
                { "type": "cross", "start": { "x": 79.8, "y": 11.3 }, "end": { "x": 94.9, "y": 59.1 }, "successful": true, "keyPass": true, "longBall": true }, … ],
    "dribbles": [ { "type": "dribble", "start": { "x": 67.2, "y": 89.8 }, "end": null, "successful": true, "keyPass": null, "longBall": null }, … ],
    "defensive": [ { "type": "tackle", "start": { "x": 33.4, "y": 89.5 }, "end": null, "successful": false, "keyPass": null, "longBall": null }, … ],
    "ballCarries": [ { "type": "ballCarry", "start": { "x": 62.5, "y": 93.3 }, "end": { "x": 69.8, "y": 86.8 }, "successful": null, "keyPass": null, "longBall": null }, … ] },
  "meta": { "playerId": 1403061, "count": 72 } }
```

---

Base URL: https://api.datasportsapi.com. Authenticate each /v2 call with the header `Authorization: Bearer <key>` (secret keys begin with `sk_live_`).
HTML: https://datasportsapi.com/docs/fixtures/player-actions/ · All docs: https://datasportsapi.com/markdown/docs.md · Data reference: https://datasportsapi.com/markdown/reference.md
