/api-sports

name: api-sports
description: |
  API Sports integration. Manage Sports. Use when the user wants to interact with API Sports data.
compatibility: Requires network access and a valid Membrane account (Free tier supported).
license: MIT
homepage: https://getmembrane.com
repository: https://github.com/membranedev/application-skills
metadata:
  author: membrane
  version: "1.0"
  categories: ""

API Sports

API Sports provides real-time sports data and statistics. It's used by sports websites, mobile apps, and fantasy sports platforms to provide up-to-date information to their users.

Official docs: https://www.api-sports.io/documentation/

API Sports Overview

• **Leagues**
• **Seasons**
• **Teams**
• **Players**
• **Venues**

Working with API Sports

This skill uses the Membrane CLI to interact with API Sports. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

Install the CLI

Install the Membrane CLI so you can run `membrane` from the terminal:

npm install -g @membranehq/cli@latest

Authentication

membrane login --tenant --clientName=<agentType>

This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.

**Headless environments:** The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:

membrane login complete <code>

Add `--json` to any command for machine-readable JSON output.

**Agent Types** : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness

Connecting to API Sports

Use `membrane connection ensure` to find or create a connection by app URL or domain:

membrane connection ensure "https://api-sports.io/" --json

The user completes authentication in the browser. The output contains the new connection id.

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has `state: "READY"`, skip to **Step 2**.

1b. Wait for the connection to be ready

If the connection is in `BUILDING` state, poll until it's ready:

npx @membranehq/cli connection get <id> --wait --json

The `--wait` flag long-polls (up to `--timeout` seconds, default 30) until the state changes. Keep polling until `state` is no longer `BUILDING`.

The resulting state tells you what to do next:

• **`READY`** — connection is fully set up. Skip to **Step 2**.
• **`CLIENT_ACTION_REQUIRED`** — the user or agent needs to do something. The `clientAction` object describes the required action:
• `clientAction.type` — the kind of action needed:
• `"connect"` — user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections.
• `"provide-input"` — more information is needed (e.g. which app to connect to).
• `clientAction.description` — human-readable explanation of what's needed.
• `clientAction.uiUrl` (optional) — URL to a pre-built UI where the user can complete the action. Show this to the user when present.
• `clientAction.agentInstructions` (optional) — instructions for the AI agent on how to proceed programmatically.

After the user completes the action (e.g. authenticates in the browser), poll again with `membrane connection get <id> --json` to check if the state moved to `READY`.

• **`CONFIGURATION_ERROR`** or **`SETUP_FAILED`** — something went wrong. Check the `error` field for details.

Searching for actions

Search using a natural language description of what you want to do:

membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json

You should always search for actions in the context of a specific connection.

Each result includes `id`, `name`, `description`, `inputSchema` (what parameters the action accepts), and `outputSchema` (what it returns).

Popular actions

| Name | Key | Description | |---|---|---| | Get Leagues | get-leagues | Get the list of available leagues and cups. | | Get Teams | get-teams | Get the list of available teams. | | Get Players | get-players | Get player statistics. | | Get Fixtures | get-fixtures | Get football fixtures/matches. | | Get Standings | get-standings | Get standings/league tables for a league and season. | | Get Predictions | get-predictions | Get AI predictions for a fixture including win probability and advice. | | Get Coaches | get-coaches | Get information about coaches/managers. | | Get Venues | get-venues | Get information about stadiums/venues. | | Get Player Squads | get-player-squads | Get current squad/roster for a team. | | Get Fixture Events | get-fixture-events | Get events for a fixture (goals, cards, substitutions, VAR, etc.). | | Get Fixture Lineups | get-fixture-lineups | Get lineups for a fixture including starting XI and substitutes. | | Get Fixture Statistics | get-fixture-statistics | Get statistics for a fixture (shots, possession, corners, fouls, etc.). | | Get Team Statistics | get-team-statistics | Get statistics for a team in a given league and season. | | Get Top Scorers | get-top-scorers | Get the top 20 scorers for a league and season. | | Get Top Assists | get-top-assists | Get the top 20 assist providers for a league and season. | | Get Injuries | get-injuries | Get injury information for players. | | Get Transfers | get-transfers | Get transfer history for a player or team. | | Get Odds | get-odds | Get pre-match betting odds for fixtures. | | Get Live Odds | get-live-odds | Get live/in-play betting odds for ongoing fixtures. | | Get Countries | get-countries | Get the list of available countries for the leagues endpoint. |

Running actio