Skip to main content

Scoutastic Connector Step

This connector step is dedicated to the Scoutastic API. It extracts data from various API routes by changing only parameters, pagination functions and the data destination.

📘 This step can run in either the Intelligence or Processing Module

Contents​

Entities​

The connector supports data extraction from these entities:

  • Appointments: Details of appointments and events, such as match schedules, training and meetings.
  • Competitions: Competition information, including name, season, participating teams and relevant statistics.
  • Managers: Manager and coach data, including personal information, management history and performance statistics.
  • Matches: Match details, including date, time, venue, teams, results and game statistics.
  • Players: Player information, including personal data, career history, performance statistics and current status.
  • Players Missed: Lists of players absent from specific events or matches, including reasons for absence.
  • Transfers History: Player transfer history between clubs, including transfer date, amounts, and source and destination clubs.
  • Teams: Team information, including squad composition, coaches, historical performance and current statistics.
  • Reports: Detailed reports on team performance, match analysis and other relevant insights.
  • Watchlists: Player or team watchlists for monitoring performance and potential future transfers.

Prerequisites​

  • Scoutastic API access token: required for authentication and data access.
  • Knowledge of the specific data assets to retrieve: understanding of the entities and data available in the Scoutastic API.
  • Python 3.x: A compatible version to run the connector. Snowflake library.
  • Requests library: To make HTTP requests to the Scoutastic API.

Configuration​

Environment Variables​

The following environment variables are required to run the step:

  • SCOUTASTIC_TOKEN: Authentication token for accessing the Scoutastic API.
  • TEAM_IDENTIFIER: Team identifier for API access (example: "sample_team").

Usage​

Configuration File (config.json)​

  • When running outside the module, provide a JSON configuration file containing the input parameters. The expected format is:
{  
  "auth_token": "Bearer \<seu_token_aqui>",  
  "team_identifier": "sample_team",  
  "player_ids": "PLAYER_ID_1,PLAYER_ID_2,PLAYER_ID_3"  
}

Passing Variables in the Module​

  • When using the module, pass parameters such as team_identifier and player_ids through its user interface (this parameter varies by step; here, players_ids retrieves data from the players/{player_id} endpoint).
    • player_ids must be a comma-separated list of player IDs to query.

Execution​

Locally (running the script directly)​

  • Use the command:
```
python players_missed.py '{"auth_token": "Bearer \<seu_token_aqui>",
"team_identifier": "sample_team", "player_ids": "PLAYER1,PLAYER2,PLAYER3"}'
```

The script collects the data and saves it to players_missed_data.json.

In the Module​

  1. Configure SCOUTASTIC_TOKEN, team_identifier and player_ids in the module interface.
  2. Run the step in the module to collect data for the chosen endpoint.

Output​

  • The connector saves extracted data in JSON files structured according to the queried entities. For example, players_missed_data.json contains absent player data.

References​

  • Consult the official Scoutastic API documentation provided by your vendor.