- How do I install and configure the Sportmonks Football API package in Laravel?
- Install it with Composer, publish the package config file, and set your SPORTMONKS_API_TOKEN environment variable. Then call the provided facade or endpoint methods to fetch leagues, fixtures, teams, players, standings, and similar resources. No database, migrations, or queue workers are required by the package itself, so a spike against a real token takes hours rather than days.
- Does this package pass through arbitrary include and filter parameters for Sportmonks v3?
- This is a critical question to verify before adopting, because Sportmonks v3 includes drive both payload shape and request cost. Check the source to see whether it forwards any include and filter combination or hardcodes a subset of endpoints and parameters. If it hardcodes, you may hit a wall as soon as your data model needs nested relations.
- Which Laravel and PHP versions does this package support?
- Verify the support matrix directly in the package composer.json before committing, since the provided overview does not state it. It is built on Laravel's HTTP client and config conventions, which suggests a native fit for Laravel 10 and newer, but confirm 10, 11, and 12 plus PHP 8.2 and above. Also verify release tags against Packagist, because the supplied release metadata contains a future date and cannot be trusted.
- Is this package safe to use in production?
- It has a bus factor of one, roughly 26 stars, zero dependents, and no evidence of production use, so treat it as unvalidated. The exposure is not abandonment, which is cheap to fix given the MIT license and thin surface area, but silent divergence from Sportmonks v3 as the API evolves. Wrap it behind an interface you own and pin an exact version with a lock file rather than a caret range.
- How does the package handle rate limits and 429 or 403 responses?
- The overview does not document error handling, so inspect the code to see whether it surfaces rate-limit headers and distinguishes 429 from 403 or collapses everything into a generic exception. This matters most for livescore polling, where per-entity buckets and retry behavior affect reliability. Plan your own retry and backoff logic in the adapter layer either way.
- Does it support the livescores inplay endpoint and separate rate-limit buckets?
- Check the endpoint coverage in the source before relying on it, since inplay paths and their rate-limit buckets are often treated separately from main endpoints. Also confirm your Sportmonks plan entitlements, because inplay, odds, and predictions may require different tiers or token scopes. The package likely does not model entitlement differences for you.
- Should I use this package, the official Sportmonks SDK, or raw Guzzle?
- For a Laravel 10+ monolith or a Laravel-based data service, this package offers the lowest-friction option because it follows framework HTTP and config conventions. Outside Laravel, use Guzzle or Sportmonks' own SDK instead of pulling in Laravel's container for a config wrapper. Given the small surface area, a hand-written 200-line replacement is also a realistic alternative.
- Does the package return typed DTOs or raw arrays?
- This is not stated in the overview and should be confirmed from the source. If it returns raw arrays, your application code will bind to upstream JSON shapes, which is the failure mode to design against. Normalize responses into your own DTOs inside a single adapter class so the rest of your code never sees Sportmonks payload structure.
- Can I cache or redistribute the football data this package fetches?
- The MIT license covers only the PHP code, not the football data. Redistribution, caching duration, and display rights are governed by your Sportmonks contract, making data licensing the highest-severity compliance risk in this integration. Review your agreement before persisting responses beyond short-lived caching.
- How do I migrate away from this package if it becomes unmaintained?
- The integration is additive and reversible, so the recommended shape is an internal FootballDataProvider interface in your domain with a single adapter class that is the only place importing the facade. Migrating then means rewriting that one class against raw HTTP or the official SDK and deleting it. Enforce the boundary with an architecture test or a PHPStan rule so the facade never leaks elsewhere.