Laravel Siasn Api Laravel Package

Product Decisions This Supports

• Buy vs. build for SIASN connectivity: This package is a thin Laravel wrapper around Indonesia's SIASN (BKN) civil-service APIs. It lets you treat "connect to SIASN" as an integration task rather than a from-scratch protocol project, which is the right call when SIASN data is a supporting capability rather than your core product.
• Feature roadmap for ASN/HR modules: Enables roadmap items that depend on authoritative civil-servant records — employee profile and identity verification, position/grade history, leave and absence workflows, promotion and pension eligibility checks, and compliance reporting for government-facing customers.
• Data-sync architecture decisions: Informs whether you build a sync/cache layer in your own domain (recommended) or query SIASN live per request. Live-per-request is a poor fit for user-facing latency and upstream availability, so this shapes your data-ownership and caching strategy.
• Customer segmentation and sales motion: Unlocks or strengthens proposals to Indonesian government agencies, regional personnel boards (BKN/BKD), and enterprises contracting with the public sector — segments that otherwise carry a long integration lead time in every deal.
• Risk and dependency decisions: This release (v2.0.21) is an annotation-only patch to the Siasn facade — no runtime behavior, no API surface change, no breaking change. It is evidence of active maintenance, not a product event. No roadmap or architecture decision should hinge on it.

When to Consider This Package

Consider it when:

• Your product is built on Laravel/PHP and you need to read or act on SIASN data; a native facade fits your conventions better than a hand-rolled HTTP client.
• You are entering the Indonesian public-sector HR domain and want to compress discovery of SIASN's auth, endpoint, and payload conventions.
• SIASN is a means, not the product — you want the integration thin and replaceable, keeping your own domain model as the source of truth.
• You need a fast feasibility spike or pilot for a government-facing feature before committing headcount to a bespoke integration.

Look elsewhere — or plan to wrap and own it — when:

• Your stack is not Laravel/PHP, or your platform team has standardized on a separate integration/gateway service.
• You need guarantees this package cannot give: SLA, security review, vendor support contract, audit trail, data-residency attestation. A community package is a dependency, not a support relationship.
• SIASN is business-critical and high-volume — you will want your own client with retry/backoff, rate-limit handling, schema validation, and observability, likely with this package as reference rather than runtime dependency.
• The upstream API changes faster than the maintainer ships releases; a single-maintainer project is real bus-factor risk for a regulated integration.
• Compliance requires certified or audited integrations with BKN.

How to Pitch It (Stakeholders)

For executives: This is a small, free open-source integration layer that shortens the path to serving Indonesian government and public-sector HR customers. It converts a multi-week integration unknown into a scoped engineering task, lowering the cost and risk of a market-entry decision. It is a dependency, not a strategic asset — we should adopt it behind our own abstraction so no customer commitment depends on its continuity. The v2.0.21 release itself is documentation-only and carries no commercial or delivery impact.

For engineering: A Laravel-native SIASN client with a facade entry point; v2.0.21 only adds method annotations to the Siasn facade for IDE/static-analysis support. No behavior change, no migration needed, no version pinning urgency — upgrade on your normal cadence. Recommended posture: consume it behind an internal repository/anti-corruption layer, keep SIASN data cached in our own store, and treat the upstream API contract as the real dependency to monitor. Watch maintainer activity and release cadence; be prepared to fork or replace with an in-house client if the package goes stale.