`betsapi_upcoming`

Pack: betsapi · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/betsapi_upcoming for the schema, then POST the same URL with its arguments for the data.

Upcoming (scheduled) sport events for a sport, optionally for a given day.

Parameters

Name	Type	Required	Description
`sport_id`	string	yes	BetsAPI sport id. Common: ${SPORT_IDS}
`day`	string	no	Optional day filter in YYYYMMDD format, e.g. “20260704”
`_apiKey`	string	yes	BetsAPI key (get one at betsapi.com, from ~$10/mo)

Example call

Arguments

{
  "sport_id": "1",
  "_apiKey": "your-betsapi-api-key"
}

curl

curl -X POST https://gateway.pipeworx.io/betsapi/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"betsapi_upcoming","arguments":{"sport_id":"1","_apiKey":"your-betsapi-api-key"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('betsapi_upcoming', {
  "sport_id": "1",
  "_apiKey": "your-betsapi-api-key"
});

More examples

{
  "sport_id": "1",
  "day": "20260704",
  "_apiKey": "your-betsapi-api-key"
}

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}

Connect to just the betsapi pack

{
  "mcpServers": {
    "betsapi": {
      "url": "https://gateway.pipeworx.io/betsapi/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

betsapi_upcoming