Weave Code
Kiriminaja Php Laravel Package
kiriminaja/kiriminaja-php
PHP SDK for KiriminAja, the Indonesian multi-courier shipping aggregator. Compare rates across couriers, create orders, schedule pickups, print labels, and track shipments from one simple API wrapper that works with Laravel or any plain PHP app.
kiriminaja/kiriminaja-php is a lightweight PHP SDK for the KiriminAja shipping aggregator API, giving your application a single integration point for multiple Indonesian couriers. It wraps authentication and API responses in a clean, framework-agnostic interface that works with Laravel, Lumen, or plain PHP.
- Compare shipping rates across couriers
- Create and manage orders and pickups
- Track shipments via AWB lookup
- Query coverage areas and COD support
- Simple, chainable request helpers
Frequently asked questions about Kiriminaja Php
- How do I install and configure kiriminaja/kiriminaja-php in a Laravel app?
- Install it with composer require kiriminaja/kiriminaja-php, then add your KiriminAja API key and origin settings to .env. If the package ships a service provider and config file, publish the config and bind the client as a singleton in your own service provider. Wrap it in an internal ShippingGateway adapter so controllers and models never call the vendor client directly.
- Does kiriminaja/kiriminaja-php support Laravel 10 and Laravel 11?
- The overview does not publish a Laravel support matrix, so check the package's composer.json and Packagist before planning. The evaluation expects a modern floor such as PHP 8.1 or newer with Laravel 9 to 11, but a hard PHP 8.2 requirement would block older services. Confirm it is tested on your exact Laravel and PHP runtime.
- Can I use kiriminaja-php to check shipping rates across multiple Indonesian couriers?
- Yes, rate checking is a core use case: the client wraps KiriminAja endpoints for multi-courier shipping quotes and serviceability. Map the returned rates into your own DTOs rather than leaking vendor response arrays into domain code. Verify quote coverage for every courier and origin or destination type you actually ship.
- How do I create a pickup request and print an AWB label with this package?
- The client covers pickup requests and label printing, but pickup creation is not automatically idempotent. Supply a client-generated idempotency key or build a retry-safe workflow, because duplicate pickups create real carrier cost and operational noise. Check the exact method signatures and response handling in the repository before wiring it into order fulfillment.
- Does kiriminaja-php support webhooks for shipment tracking, or do I need polling?
- Tracking is listed as a supported area, but the overview does not state whether KiriminAja pushes status updates by webhook or requires polling. Confirm the available tracking endpoints and webhook contract before designing your shipment status flow. If only polling is supported, schedule it with backoff and cache statuses to stay within rate limits.
- Is there a sandbox for testing KiriminAja integration before production?
- Treat sandbox access as an account prerequisite, not a package feature: you need a KiriminAja account, staging key, registered origin address, and enabled couriers. Ask the vendor how faithful the sandbox is to production for rates, pickup, label, and tracking. Without contract tests against a real sandbox, a minor release can break AWB generation.
- Is kiriminaja/kiriminaja-php maintained by KiriminAja officially?
- The kiriminaja/ namespace suggests a first-party package, but verify the actual maintainers, issue triage, tags, changelog, and CI on the repository and Packagist. A low star count means limited community adoption, so fewer external users are surfacing bugs. The reported 2026 release date should be reconciled with tag history before you assume active maintenance.
- What are the production risks of using this Guzzle-based KiriminAja client?
- The main risk is single-vendor coupling: a breaking API change or courier de-listing is an outage you cannot patch around. Error semantics are also unclear from the overview, so verify whether failures raise typed exceptions, return DTOs, or silently return arrays. Centralize timeouts and retry policy in one configured client, and never blind-retry pickup or cancel calls without idempotency.
- Does kiriminaja-php include postal code and area mapping for address validation?
- Mapping is part of the package scope, covering postal codes, areas, and courier serviceability. That data is volatile as couriers enter and exit regions, so confirm whether the package caches mapping calls or fetches them live. Add your own cache layer and validation rules rather than trusting vendor mapping data directly in checkout.
- What alternatives exist if kiriminaja/kiriminaja-php is too immature for production?
- If the package proves too immature, keep the same architecture and write a small Guzzle client directly against the KiriminAja REST API behind your ShippingGateway interface. You can also evaluate other Indonesian shipping aggregators or official SDKs, but vendor onboarding and courier enablement remain the long lead-time items. Forking is reasonable only if you accept responsibility for contract tests and upstream changes.
Weaver
How can I help you explore Laravel packages today?