Filament Api Resources Laravel Package

Product Decisions This Supports

• API-first admin panels: Build Filament dashboards for SaaS products, third-party integrations, or legacy systems where Eloquent models aren’t feasible.
• Hybrid architecture: Combine internal Laravel resources with external APIs (e.g., Stripe, Shopify, or custom microservices) under a unified admin UI.
• Roadmap pivot: If Filament V4’s native API support matures, this package could serve as a proof-of-concept or legacy bridge for existing implementations.
• Build vs. buy: Justify custom development for niche use cases (e.g., real-time API polling, complex pagination, or custom auth flows) where off-the-shelf solutions (like Sushi) fall short.
• Multi-tenant SaaS: Dynamically switch API endpoints per tenant without duplicating Eloquent models.

When to Consider This Package

• Use this if:

  • You’re on Filament V3 and need API integration now (V4’s custom data support is beta).
  • Your API lacks Eloquent-like relationships but requires Filament’s forms, tables, and CRUD workflows.
  • You prioritize pagination, sorting, and searching over real-time updates (e.g., for analytics dashboards).
  • Your team lacks time to build a custom API adapter or wait for V4 stabilization.

• Look elsewhere if:

  • You’re using Filament V4 (native API support is superior; see docs).
  • You need GraphQL or WebSocket support (this is REST-focused).
  • Your API requires complex auth (e.g., OAuth2 with dynamic scopes) or real-time sync (consider Laravel Echo or custom events).
  • You’re evaluating Sushi (more mature, though limited to tables) or Nova API Resources (if using Laravel Nova).

How to Pitch It (Stakeholders)

For Executives:

"This package lets us build a unified admin panel for [Product X]’s API-backed services—like Stripe subscriptions or Shopify orders—without rewriting the UI from scratch. It plugs into Filament (our existing admin framework), saving dev time while keeping the polished experience users expect. Since Filament V4 is adding native API support, this is a short-term solution to avoid delays, with a clear upgrade path. The MIT license and active development (despite being archived) make it low-risk."

For Engineering:

*"This fills a gap for Filament V3 users who need API-driven resources beyond what Sushi offers. Key advantages:

• Full CRUD: Not just tables—forms, relationships, and actions work with APIs.
• Pagination/sorting: Handles edge cases Sushi struggles with (e.g., multi-level nested APIs).
• Low boilerplate: Abstracts API calls into Filament’s resource system. Tradeoff: The code is rough (as noted in the README), but it’s a starting point. If we commit, we’ll need to:

1. Vet the API adapter for our use case (e.g., rate limits, auth).
2. Plan for a V4 migration once stable.
3. Consider wrapping it in a custom trait for maintainability."*

Risk Mitigation:

• "We can treat this as a prototype and compare it to Filament V4’s custom data features once they’re production-ready."