Weave Code
Eveapi Laravel Package
eveseat/eveapi
Laravel package for integrating EVE Online's ESI API, with authentication, token management, and convenient access to character, corporation, and alliance endpoints for SeAT applications.
SeAT EVE API Integration
Frequently asked questions about Eveapi
- How do I install eveseat/eveapi in a Laravel application?
- Install it with Composer using composer require eveseat/eveapi. Laravel service provider auto-discovery registers the package, and you should publish its configuration file so you can adjust ESI and OAuth settings. After publishing, configure your EVE developer application credentials and callback URL before running the OAuth flow.
- Which Laravel and PHP versions does eveseat/eveapi support?
- The package is built for Laravel and the 5.x line is mature, but you must verify the exact Laravel and PHP constraints in its composer.json for your chosen release. The assessment notes compatibility with Laravel 8, 9, and 10+ on PHP 8+ as a likely fit, not a guarantee. Always check the package constraints against your host application before upgrading.
- What environment variables are required for EVE SSO and ESI in eveseat/eveapi?
- You need an EVE developer application with a client ID, client secret, and callback URL, typically configured through EVE_CLIENT_ID, EVE_CLIENT_SECRET, and EVE_CALLBACK_URL. Persistent storage for OAuth tokens must also be configured. Version 5.0.37 fixes version assignment when the related environment variable is not set, so confirm any version-related variables are defined for your deployment.
- Which ESI scopes and endpoints can I access with eveseat/eveapi?
- The package provides typed endpoint access for character, corporation, and alliance ESI routes, plus a fluent client for authenticated requests. The exact scopes and endpoints are defined by EVE ESI and the package version, so review the package source and ESI documentation for the routes you need. You must request the appropriate scopes during the EVE SSO authorization flow.
- How does eveseat/eveapi handle OAuth2 token refresh and revocation?
- It manages character and corporation OAuth2 tokens for authenticated ESI requests and supports the token lifecycle needed by SeAT applications. You should still implement or verify refresh handling and graceful behavior when a token is expired or revoked. Plan for reauthorization and alerting on auth failures, because revoked or invalid tokens will break ESI calls.
- Can eveseat/eveapi manage multiple EVE characters or corporations per user?
- Yes, the package is designed for SeAT-style applications that link multiple EVE entities to application data through models and traits. Token management covers character and corporation authentication flows, so multi-character and multi-tenant scenarios are possible. You remain responsible for scoping access control, token storage, and which ESI endpoints each linked entity may call.
- Does eveseat/eveapi cache ESI responses and respect ESI rate limits?
- The package includes caching and rate-limit awareness to reduce redundant ESI calls. Caching still depends on your Laravel cache configuration and how you call endpoints, so tune cache lifetimes for volatile data. Respect ESI rate limits per token and application, and add backoff or queueing where your workload can burst.
- How should I test eveseat/eveapi and the EVE SSO token lifecycle?
- Test the OAuth callback, token storage, refresh, expiry, and revoked-token paths in a controlled environment before production. In Laravel tests, mock the ESI client or HTTP layer rather than calling live ESI endpoints for every case. Use test characters and developer applications to validate scopes, rate-limit handling, and graceful degradation.
- What are common production failure modes with eveseat/eveapi?
- Common failures include ESI downtime or breaking changes, expired or revoked tokens, refresh failures, OAuth callback misconfiguration, rate-limit exhaustion, and missing environment variables. Version 5.0.37 reduces risk from an unset version variable, but you still need alerting and graceful degradation for auth and API errors. Monitor ESI error rates and package releases, and keep token refresh and caching under operational review.
- Is eveseat/eveapi actively maintained, and what alternatives should I consider?
- It is a community-maintained package in the SeAT ecosystem, with frequent patch releases and no formal commercial SLA expected. Keep it updated, watch ESI changelogs and GitHub releases, and test major upgrades because the documented upgrade path should be verified for breaking changes. Alternatives include building your own ESI client or using other EVE API libraries, but eveseat/eveapi is a strong fit when you want Laravel service-container integration and SeAT-friendly models.
Weaver
How can I help you explore Laravel packages today?