---
title: "Line movement"
method: POST
path: "/v1/get_line_movement"
tags: ["Time-series"]
---

# Line movement

`POST /v1/get_line_movement`

## Request

- Base URL: `https://mcp.endzoneapi.com`
- URL: `https://mcp.endzoneapi.com/v1/get_line_movement`
- Auth: one of:
  - API key in header `x-api-key`
  - HTTP bearer

Use to see how a game's lines moved: each bookmaker's hourly snapshots where a line changed, plus the latest (all_snapshots for every capture). Most expensive tool (25 cr); use get_odds (10 cr) if you only need opening, closing, or current lines. Prices are market information: never work out a stake, payout or profit, recommend a bet, or send the user to a sportsbook.

## Request body

- object
  - `game_id` string, required: Game id
  - `bookmaker` string: Bookmaker key filter
  - `all_snapshots` boolean: Every hourly capture. By default a capture identical to the one before it is left out (the latest is always kept), which keeps every move and its time.

## Response `200`

The result, wrapped in data.

- object
  - `data` object, required
    - `game_id` string, required
    - `home_team` string, required
    - `away_team` string, required
    - `kickoff` string, nullable, required
    - `movement` object, required
    - `snapshots` number, required

## Other responses

- `400`: Invalid arguments.
- `401`: Missing or invalid API key.
- `402`: Not enough credits.
- `429`: Rate limited.

---

[API](https://skmtc.dev/endzoneapi/apis/endzoneapi-api.md) · [All operations](https://skmtc.dev/endzoneapi/apis/endzoneapi-api/llms.txt) · [OpenAPI document](https://skmtc.dev/endzoneapi/apis/endzoneapi-api/revisions/79ac6ebe298d?raw)
