Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Consistent pagination with up to 200 items per page.

  • Designed using the latest technology versions.

  • Faster data retrieval and optimized resource usage.

  • Granular filtering and sorting by specific field(s) - for example by id, name, descending. Retrieve precise datasets (e.g., by sport, age category, or competition) with fewer API calls.
    You can filter based on nearly every field in the response. Additionally, we offer greater flexibility regarding the types of searches that can be used.

  • Filter by specific fields

    • For single ID filtering: Example: filter=id[equals]:1

    • For filtering by multiple IDs: Example: filter=id[in]:1,2,3

    • For stacking filters: Separate them with "~". Example: filter=id[in]:1,2,3~sportId[in]:1,2,3,4,5

    • Different filter comparators available:

      • equals: Matches exact values of all data types

      • notequals: Filters out values not matching the specified criteria

      • in: Matches values from a specified list, works only with integer and decimal values

      • nin: Excludes values from a specified list, works only with integer and decimal values

      • gte: Greater than or equal to comparator

      • lte: Less than or equal to comparator

      • contains: Matches values containing a specified substring

      • startsWith: Matches values starting with a specified substring

      • Duplications of the "filter" property are allowed only in the case of "range" filtering, such as filter=startDate[gte]:2021-07-28~startDate[lte]:2021-07-29

      • filtering by null:

        • Equal to null: filter=cityName[equals]:null

        • Not equal to null: filter=cityName[notequals]:null

  • The API maintains a uniform structure, with each endpoint offering two functionalities:

    • A listing endpoint for multiple items, enabling filtering and sorting via query parameters.

    • An endpoint dedicated to retrieving a single item using its unique identifier (ID).

  • The API doesn’t contain deleted fixtures

  • Data ingestion capabilities:

    • entity by entity

    • whole fixture hierarchy

    • whole team squad

  • New “Person” entity introduced: Person is a representation of a real-life person which can be used in specific context:

  • In the Fixtures API v2, we support rosters (also known as "Squads"), which represent a list of all players registered to a team and available for selection in each fixture. However, the API does not support lineups, which refer to specific players participating in a particular fixture.
    FAPI v2 limits:
    1000 per second
    1000000000 per month

    These enhancements lead to improved performance, more precise data retrieval, and increased flexibility for clients.

...