Pinnacle API Documentation

Historically, Soccer Extra Time markets (e.g., "France (To Advance)", "England (ET ONLY)") were distinct events. They are now provided as Periods of the parent live event.

Important Data Note: Goals and Red Cards occurring during Extra Time are only returned in Period 3.

Period Mapping for Soccer Extra Time:

• Period 3: Extra Time
• Period 6: Penalty Shootout
• Period 7: 1st Ten Shootout Pen
• Period 8: To Qualify
• Period 39: To Win Final

Market Availability by Period:

• Period 3: Spread, Moneyline, Total, and Team Totals.
• Periods 6, 8, 39: Moneyline only.
• Period 7: Total only.

// Example of an event with multiple periods (from Get Odds response)
"periods": [
    {
        "lineId": 1912670188,
        "number": 8, // To Qualify
        "moneyline": { "home": -322.0, "away": 212.0 }
    },
    {
        "lineId": 1912670213,
        "number": 3, // Extra Time
        "spreads": [...],
        "moneyline": { "home": 130.0, "away": 497.0, "draw": -109.0 },
        "totals": [...]
    }
]

Use the parentId field from the [Get Fixtures] endpoint to group related events (such as pre-game and live versions of the same match, or different market types like corners) to a single 'parent' event.

Key Rules:

• Parent events are pre-game events (liveStatus=0 or liveStatus=2) and do not have a parentId set.
• Live events (liveStatus=1) will always have a parentId set.
• Multiple events can be associated with one parent (e.g., if they have different resultingUnit or offer alternative odds).
• The parentId property is intended to replace the rotNum property, which is being decommissioned.

{
    "sportId": 29,
    "league": [
        {
            "id": 2331,
            "events": [
                {
                    "id": 837721686,
                    "liveStatus": 1,
                    "parentId": 834342247
                },
                {
                    "id": 834342247,
                    "liveStatus": 2,
                    "parentId": null
                }
            ]
        }
    ]
}

The parentId property in the /fixtures response is used to group associated events to a single "parent" pre-game event. This replaces the need for using rotation numbers to link related events (such as a main match and its associated corner or booking markets).

Example of grouping via parentId in a /fixtures response:

{
    "sportId": 29,
    "last": 148671597,
    "league": [
        {
            "id": 2331,
            "name": "Norway - 1st Division",
            "events": [
                {
                    "id": 837721686,
                    "starts": "2018-04-10T17:00:00Z",
                    "home": "Viking Fk",
                    "away": "Mjondalen",
                    "rotNum": "6751",
                    "liveStatus": 1,
                    "status": "O",
                    "parlayRestriction": 2,
                    "parentId": 834342247,
                    "altTeaser": false
                },
                {
                    "id": 834342247,
                    "starts": "2018-04-10T17:00:00Z",
                    "home": "Viking Fk",
                    "away": "Mjondalen",
                    "rotNum": "6751",
                    "liveStatus": 2,
                    "status": "I",
                    "parlayRestriction": 2,
                    "parentId": 834342247,
                    "altTeaser": false
                }
            ]
        },
        {
            "id": 6816,
            "name": "Norway - 1st Division Corners",
            "events": [
                {
                    "id": 837721684,
                    "starts": "2018-04-10T17:00:00Z",
                    "home": "Viking Fk (Corners)",
                    "away": "Mjondalen (Corners)",
                    "rotNum": "6751",
                    "liveStatus": 1,
                    "status": "O",
                    "parlayRestriction": 1,
                    "parentId": 834342247,
                    "altTeaser": false
                },
                {
                    "id": 837721615,
n                    "starts": "2018-04-10T17:00:00Z",
                    "home": "Viking Fk (Corners)",
                    "away": "Mjondalen (Corners)",
                    "rotNum": "6751",
                    "liveStatus": 2,
                    "status": "I",
                    "parlayRestriction": 1,
                    "parentId": 834342247,
                    "altTeaser": false
                }
            ]
        }
    ]
}

As of the September 12, 2022 update, Tennis events have moved away from embedding handicap information and period descriptions directly into the team names. Instead, the API uses explicit resultingUnit values and separate event objects to represent different markets.

Key changes:

• Explicit resultingUnit: Markets now explicitly state whether they use Sets, Games, or Regular units.
• Spread Markets: Set Handicap markets no longer use Moneylines with handicap points in the name; they are now offered as spread markets.
• Period Handling: For Live tennis, instead of using Period 0 with descriptions in the team names, the API uses the number field within the periods array to distinguish between different resulting units.

To find the specific descriptions for Tennis Periods, use the following endpoint: /v1/periods?sportId=33

{
    "id": 1562180480,
    "starts": "2022-10-31T20:30:00Z",
    "home": "Sebastian Korda",
    "away": "Alex De Minaur",
    "resultingUnit": "Sets", 
    "version": 440033645
},
{
    "id": 1562180497,
    "starts": "2022-10-31T20:30:00Z",
    "home": "Sebastian Korda (Games)",
    "away": "Alex De Minaur (Games)",
    "parentId": 1562180480,
    "resultingUnit": "Games", 
    "version": 440033657
}