Simpro Php Sdk Laravel Package

Product Decisions This Supports

• Integration scope for Simpro-backed workflows: This SDK is the plumbing for any feature that reads or writes Simpro data — quotes, jobs, sites, customers, invoices, schedules. It informs the build-vs-buy call: adopt the SDK and spend engineering effort on your product's differentiation rather than on OAuth token handling, pagination, rate limiting, and resource mapping.
• Quote-to-job conversion features: Release 1.1.23 corrects how LinkedJobID is read and sent on quotes (matching Simpro's casing). That field is the link between an approved quote and the job that fulfils it, so this is a direct reliability fix for any roadmap item involving "quote accepted → job created → status sync." Worth re-validating your quote-to-job acceptance path after upgrading.
• Data fidelity / field-mapping risk: The fix is a reminder that Simpro's API has casing and naming quirks that are not always obvious from docs. A maintained SDK absorbs those quirks; a hand-rolled client means your team rediscovers them in production. This supports keeping third-party API integration behind the SDK boundary.
• Maintenance signal for roadmap confidence: Patch-level releases (1.1.23 follows 1.1.22) indicate active maintenance by the vendor (Stitch Digital) and responsiveness to real integration bugs. That's a positive input into whether to depend on this package for a multi-quarter integration roadmap.
• Release cadence as a planning input: Frequent small patches mean you should budget for routine dependency bumps per sprint, not just major-version upgrades.

When to Consider This Package

Adopt when:

• You are building a Laravel/PHP product that must read or write Simpro data (field service management: quotes, jobs, invoices, sites, customers, schedules).
• Your team is on a supported Laravel/PHP version and is comfortable with Composer-managed dependencies and semantic versioning.
• You want quote/job linkage, authentication, and pagination handled for you rather than maintained in-house.
• You anticipate ongoing Simpro integration surface area (multiple resources, webhooks, sync) where an SDK's per-resource coverage amortizes its cost.

Look elsewhere or pause when:

• You are not on Simpro. This package has no value outside that ecosystem.
• You need guarantee-level stability. This is a 1.x package with frequent patch releases; a bugfix like the LinkedJobID casing change implies prior versions had incorrect behavior on that field. Pin versions and test upgrades.
• Your integration is a single one-off call. A thin HTTP client plus Simpro's REST docs may be simpler than adding a dependency.
• You require vendor support SLAs, formal deprecation policy, or security review artifacts that a small open-source SDK does not publish.

How to Pitch It (Stakeholders)

For executives: Simpro is the system of record for our field-service customers' quoting and job data. Rather than build and maintain that integration ourselves, we can adopt an actively maintained open-source SDK that already covers authentication and the core resources. Recent releases are small, targeted bugfixes — including a correction to how quotes link to jobs — which tells us the library is being used in production and is being kept current. Recommendation: adopt with a pinned version and a routine upgrade slot each sprint; the main risk is low bus factor on a third-party library, mitigated by the fact that it's open source and the integration surface is well understood.

For engineering: Add stitch-digital/simpro-php-sdk as a Composer dependency, pin to ^1.1, and wrap it behind an internal adapter interface so we can swap it or stub it in tests. Note the 1.1.23 change: LinkedJobID is now sent and read with Simpro's casing on quote payloads — regression-test the quote-to-job linking flow on upgrade, since earlier versions may have silently dropped that field. Watch the changelog for casing/naming fixes, as those are the class of bug most likely to surface as data-sync defects rather than as exceptions.