Saloon Laravel Package

Product Decisions This Supports

• Build vs. Buy: Buy for API integrations to avoid reinventing HTTP clients, authentication logic, and response handling. Saloon reduces dev time by 30-50% for API-heavy applications (e.g., payment gateways, SaaS tooling, or data syncs).
• Feature Roadmap:
  • API Aggregator Platforms: Accelerate integration with 3rd-party APIs (Stripe, Twilio, etc.) by standardizing connectors/requests.
  • Internal Microservices: Enforce consistent HTTP patterns across teams (e.g., auth, retries, DTOs).
  • Testing Infrastructure: Leverage built-in mocking to reduce flaky tests (e.g., assertSent, MockClient).
• Use Cases:
  • Laravel Monoliths: Replace Guzzle/HTTP clients with typed, maintainable connectors (e.g., StripeConnector).
  • Headless Services: Build lightweight SDKs for internal APIs (e.g., InventoryServiceConnector).
  • Legacy Modernization: Gradually replace spaghetti HTTP calls with structured Request classes.

When to Consider This Package

Adopt Saloon if:

• Your PHP/Laravel app relies on 5+ external APIs with complex auth (OAuth, API keys, JWT).
• You need testable HTTP layers (e.g., mocking responses without hitting live endpoints).
• Your team struggles with inconsistent HTTP patterns (e.g., mixed Guzzle/HTTP clients).
• You’re building a SDK or API wrapper for internal/external use.

Look elsewhere if:

• You’re using non-PHP stacks (Saloon is PHP-first).
• Your APIs are simple CRUD (e.g., 1-2 endpoints) → Guzzle/HTTP clients suffice.
• You need GraphQL support (Saloon focuses on REST).
• Your team lacks PHP 8.1+ (Saloon drops PHP 7.x support).

How to Pitch It (Stakeholders)

For Executives: "Saloon cuts API integration dev time by 40% while improving reliability. It standardizes how we interact with 3rd-party services—reducing bugs from inconsistent HTTP calls and enabling faster testing. For example, our Stripe payments team could build a reusable StripeConnector in hours instead of weeks, with built-in retries and mocking for CI/CD."

For Engineers: *"Saloon gives us:

• Typed Requests: Autocomplete for endpoints/methods (e.g., GetCustomerRequest).
• Mocking Superpowers: Test API calls without hitting live services (e.g., MockClient::assertSent()).
• Laravel Integration: Service providers, caching, and queue support out of the box.
• Security: Fixed CVEs (e.g., SSRF, RCE) and strict auth handling. Tradeoff: Slight learning curve for new teams, but pays off at scale."*

For QA/DevOps: *"With Saloon’s mocking, we can:

• Eliminate flaky tests caused by rate limits or API downtime.
• Validate request/response shapes early (e.g., assertResponseMatches()).
• Simulate failures for resilience testing (e.g., 500 errors, retries)."*