Eveapi Laravel Package

Product Decisions This Supports

• Build vs. buy for EVE Online integrations: eveseat/eveapi is the ESI (EVE Swagger Interface) client that underpins SeAT, the dominant Laravel-based EVE Online corp/alliance management tool. If your roadmap includes EVE-adjacent features — member auth via EVE SSO, character/corp asset and wallet sync, structure and fleet tooling — this package is the shortest path to a working integration rather than building an OAuth2 + ESI client from scratch.
• Feature scoping: Supports decisions on which EVE data surfaces to expose (character info, corporation assets, industry jobs, market data) because the package’s resource wrappers map closely to ESI endpoints. Use it to estimate effort per endpoint family.
• Token lifecycle strategy: The package handles ESI token refresh, scopes, and per-character token storage — a decision input for whether to invest in your own token vault or delegate to the SeAT ecosystem.
• Deployment/observability hygiene: Release 5.0.37 fixes version assignment when an environment variable is not set, so version reporting in diagnostics/telemetry is now reliable in unconfigured or containerized deployments. Low-risk, non-breaking; supports tightening deployment standards (always set the env var explicitly) without urgent action.
• Roadmap risk posture: Confirms the package is actively patched (patch-level maintenance), which is a positive signal for keeping it on the dependency list rather than forking.

When to Consider This Package

Consider adoption when:

• You are building inside or alongside SeAT (or another Laravel app) and want first-class ESI integration with minimal glue code.
• You need EVE SSO authentication and token refresh handled for you, including multi-character and corporation-scoped tokens.
• Your team is already Laravel/PHP-native and comfortable with Eloquent, service providers, and configuration-driven packages.
• You value ecosystem alignment over generality — matching SeAT’s data model reduces integration friction with existing plugins and community tooling.
• You need a maintained, versioned dependency with responsive patch releases (5.0.37 is a small correctness fix, indicating active maintenance rather than feature churn).

Look elsewhere when:

• You are not in the EVE Online domain — this package is highly specific and adds no value as a general HTTP/API client.
• You need a standalone, framework-agnostic ESI client (e.g., Python/Go services, or non-Laravel PHP).
• You require vendor-supported SLAs or enterprise-grade long-term support; this is community-maintained and should be treated as such in risk registers.
• Your architecture cannot accept SeAT-coupled models or you need to avoid transitive dependency weight.
• You only need a handful of ESI calls and would rather implement a thin authenticated HTTP client (lower blast radius, no ecosystem lock-in).

How to Pitch It (Stakeholders)

For executives: eveseat/eveapi is a mature, actively maintained Laravel package that gives us ready-made access to EVE Online’s official API, including secure player login and data sync. Choosing it over a custom build removes weeks of integration and ongoing maintenance work, and lets us plug into SeAT, the de facto standard toolset for EVE communities — which means faster time-to-market and lower engineering cost for any EVE-facing feature. The latest release (5.0.37) is a minor bug fix improving version reporting in environments where a config variable isn’t set; it is non-breaking and safe to adopt.

For engineering: It’s the ESI client used across the SeAT ecosystem — OAuth2/SSO, token refresh, scoped endpoint wrappers, and Laravel-native service provider/config conventions. Adopt it if we’re building in Laravel and want ESI coverage without hand-rolling auth and rate-limit handling. Caveats: it’s community-maintained, EVE-specific, and couples us to SeAT’s data model. Mitigations: pin versions, set the version environment variable explicitly (per 5.0.37), and wrap the package behind a thin internal interface so we can swap to a direct ESI client if needed. 5.0.37 is a patch-level correctness fix with no migration work required — safe to upgrade in the normal cycle.