Laravel Sportmonks Soccer Laravel Package

Product Decisions This Supports

• Build vs. buy for football data integration: v2.0.0 strengthens the case for using this package as a thin Laravel-native integration layer over Sportmonks Football API v3 rather than maintaining custom HTTP/auth/pagination code. This is most relevant when the team is Laravel/PHP and does not want to own API plumbing.
• Feature scoping and roadmap: The package now aligns with API v3 and league-based live data via liveByLeagueId(). Product should plan live-score and league-centric experiences around league IDs, not season IDs for that endpoint.
• Migration planning: This is a breaking release. Any existing dependency on liveBySeasonId(), video methods, or aggregated topscorer methods must be treated as a migration workstream, not a routine upgrade. The added upgrade guide and endpoint documentation reduce delivery risk but do not remove the need for impact analysis.
• Reliability and quota planning: Pagination validation and rate-limit metadata handling support better caching, retry, and capacity decisions. PMs can use this to justify caching strategy, API budget planning, and SLA expectations for data-heavy features.
• Vendor dependency visibility: Because this package tracks a specific third-party API, roadmap decisions should account for Sportmonks API version changes, endpoint deprecations, and coverage gaps. This release is a concrete reminder that API-wrapper upgrades can create product-facing scope changes.
• Out-of-scope feature commitments: Do not promise video content or aggregated topscorer functionality through this package after v2.0.0. If those are roadmap requirements, they need a separate data source or a different integration approach.

When to Consider This Package

Consider this package when:

• The product is built on Laravel/PHP and needs football data from Sportmonks Football API v3.
• The team wants Laravel HTTP client usage, header-based authentication, pagination validation, and rate-limit metadata handling without building and maintaining that layer internally.
• The roadmap centers on supported football data use cases such as leagues, fixtures, live league data, and related endpoints covered by the package documentation.
• The team can absorb a breaking v2 migration and has a plan to audit existing usage of removed or renamed methods.
• Engineering values a maintained wrapper with an upgrade guide and API endpoint documentation over a direct, bespoke API client.

Look elsewhere or plan additional work when:

• The product requires video content or aggregated topscorer functionality through this package; those methods were removed as unsupported.
• Existing code depends on liveBySeasonId() and cannot quickly move to liveByLeagueId() or another data model.
• The product needs a provider-agnostic football data abstraction, multi-provider failover, or coverage beyond Sportmonks API v3.
• The team is not on Laravel/PHP or would rather integrate directly with Sportmonks for full control.
• The organization cannot tolerate third-party API version migrations or lacks capacity to validate endpoint coverage before committing.

How to Pitch It (Stakeholders)

Executive summary: v2.0.0 is a meaningful modernization release for this Laravel/PHP Sportmonks integration. It moves to Sportmonks Football API v3, uses Laravel’s HTTP client and header-based authentication, and adds pagination and rate-limit handling. That reduces custom integration maintenance and improves operational visibility, but it is a breaking upgrade that requires planned migration.

For engineering: Adopt v2 for new Laravel work that needs Sportmonks v3. Treat existing v1 usage as a migration project: replace liveBySeasonId() with liveByLeagueId(), remove reliance on unsupported video and aggregated topscorer methods, and validate pagination/rate-limit assumptions. Use the new upgrade guide and endpoint docs as the migration baseline.

For product: The package is a reasonable fit for league-centric football data features, but it is not a path to video or aggregated topscorer capabilities. Roadmap owners should confirm that live data requirements can be expressed by league ID and that removed methods are not part of committed scope. If they are, plan a separate solution before upgrading.

Recommendation: Approve v2.0.0 for new builds and planned migrations where Sportmonks v3 is the intended data source and the team can handle the breaking changes. Do not position it as a drop-in upgrade for products relying on removed endpoints or season-ID live data.