Pinnacle API

https://www.pinnacle.com/en/api/manual
Admin
Pinnacle API is a RESTful service for betting all bet types on all sports.
Tokens:1,722
Snippets:23
Trust Score:9.5
Update:6 months ago
Show doc for...
Tokens:
Raw
### Compression

Source: https://www.pinnacle.com/en/api/manual

HTTP compression is supported and recommended for optimal performance. Ensure the `User-Agent` header is set.

```APIDOC
## Compression

Pinnacle API supports HTTP compression. We strongly recommend using compression as it would give the best performance.
Please make sure to set the `User-Agent` HTTP header or compression might not work.
```

--------------------------------

### Authentication

Source: https://www.pinnacle.com/en/api/manual

The API uses HTTP Basic access authentication. Always use HTTPS. You need to send an Authorization header with a Base64 encoded username:password.

```APIDOC
## Authentication

The API uses HTTP Basic access authentication. Always use HTTPS to access the API.
You need to send HTTP Request header like this:
```
Authorization: Basic <Base64 value of UTF-8 encoded “username:password”>
```

Example:
```
Authorization: Basic U03MyOT23YbzMDc6d3c3O1DQ1
```

Please note that in order to access Pinnacle API, you must have a funded account.
```

--------------------------------

### API Reference - Rules

Source: https://www.pinnacle.com/en/api/manual

General rules and guidelines for interacting with the Pinnacle API endpoints, including delta/snapshot calls, rate limiting, and IP restrictions.

```APIDOC
## API Reference

### Rules
  1. Delta and snapshot calls are supported in `/fixtures`, `/fixtures/special` , `/odds` and `/odds/special` endpoints. Delta calls return changes since the provided `since` value. For delta calls, `since` parameter must not be set to 0 or 1, it must always be the value of the `last` property from the previous response. Snapshot calls return the current state, `since` parameter must not be provided for snapshot calls.
  2. Always issue a snapshot call first, then proceed with delta calls. This yields faster response times and smaller payloads, so your client will receive odds and fixture updates more quickly.
  3. The client must not call the `/odds` or `/fixture` eendpoints in a loop for each sport, league, or fixture. If you’re interested in certain leagues only, include all their IDs in the `leagueIds` pparameter in a single call. Likewise, if you need specific events, include all their IDs in the `eventIds` parameter together.
  4. For the `/sports` call: requests must be limited to once every 60 minutes. The list of sports rarely changes, and the “active events” count is obsolete functionality that will eventually be removed.
  5. The client must not call the `/line` endpoint in a loop. This endpoint exists solely to check a price prior to placing a bet.
  6. IP Restrictions: Access to the entire API is restricted to a maximum of 2 distinct IP addresses per client.
```

--------------------------------

### Data Format Headers

Source: https://www.pinnacle.com/en/api/manual

Required headers for specifying JSON content type and acceptance.

```http
    Accept: application/json
```

```http
    Content-Type: application/json
```

--------------------------------

### Date Time Format

Source: https://www.pinnacle.com/en/api/manual

All dates and times are provided in GMT time zone and follow the ISO 8601 format.

```APIDOC
## Date Time Format

All dates and times are in GMT time zone, ISO 8601 format
```

--------------------------------

### HTTP Basic Authentication Header

Source: https://www.pinnacle.com/en/api/manual

Required header for authenticating requests using a Base64 encoded username and password.

```http
Authorization: Basic <Base64 value of UTF-8 encoded “username:password”> 
```

```http
Authorization: Basic U03MyOT23YbzMDc6d3c3O1DQ1 
```

--------------------------------

### API Endpoint URL

Source: https://www.pinnacle.com/en/api/manual

The base URL for accessing the Pinnacle API service.

```text
api.pinnacle.com
```

--------------------------------

### Data Formats

Source: https://www.pinnacle.com/en/api/manual

Pinnacle API supports only JSON format. Ensure the correct `Accept` and `Content-Type` headers are set for requests and responses.

```APIDOC
## Data Formats

Pinnacle API supports only JSON format. HTTP header `Accept` must be set:
```
    Accept: application/json
```

POST HTTP Request must have JSON body content and `Content-Type` HTTP header must be set:
```
    Content-Type: application/json
```
```

--------------------------------

### Deduplication

Source: https://www.pinnacle.com/en/api/manual

Deduplication is automatically handled for place bet requests to prevent duplicate bets. A `uniqueRequestId` is stored for 30 minutes.

```APIDOC
## Deduplication

When a client issues a network request, it is always possible for the request to timeout or return an error status code indicating that the bet may not have been accepted. This opens up the possibility of the same request being sent more than once, which could create duplicate bets. Deduplication is a technique to avoid creating these duplicates when retrying a create request. We do the deduplication automatically for you.
If the bet is accepted, we store the `uniqueRequestId` in the system for 30 min. If you try again within that time range to place a bet with the same `uniqueRequestId`, you will get the appropriate error.
All place bet requests support deduplication.
```
Tokens:
Raw