Weave Code
Inpost Pickup Point Bundle Laravel Package
answear/inpost-pickup-point-bundle
Symfony bundle for InPost integration that lets you find parcel machines and pickup points via the InPost API. Includes a fluent FindPointsRequestBuilder for filtering results by name, city, post code, type, functions, partner, payment availability, and update date, with paging support.
AnswearInpostBundle integrates Symfony applications with the InPost SHIPX API, letting you query parcel machines and pickup points directly from your PHP code. It provides a fluent FindPointsRequestBuilder for composing search criteria and a FindPoints command for executing requests against the API.
- Search parcel machines by name, city, post code, or province
- Filter by point type, function, partner, and payment availability
- Restrict results by update date ranges
- Paginate with
setPageandsetPerPage - Chain multiple filters fluently before calling
build()
Frequently asked questions about Inpost Pickup Point Bundle
- How do I install answear/inpost-pickup-point-bundle in a Laravel application?
- Run composer require answear/inpost-pickup-point-bundle. The package is a Symfony bundle, so Laravel will not auto-register AnswearInpostBundle the way Symfony Flex does. You must manually bind its services, commands, and dependencies in a service provider or wrap the client in your own Laravel package. Check that your application meets the PHP 8.4+ requirement before installing.
- Is answear/inpost-pickup-point-bundle compatible with Laravel 10 and newer?
- It can be adapted for Laravel 10+ as long as the PHP 8.4+ requirement is met and Symfony components resolve correctly. The bundle is Symfony-native, so compatibility depends on bridging or replacing Symfony HttpClient and Serializer services. There are no bundled tests, so evaluate repository activity and add your own integration tests before relying on it in production.
- How do I search Inpost parcel machines by name, city, or postcode in Laravel?
- Use FindPointsRequestBuilder with setName or setNames for machine names, setCity or setCities for city filters, and setPostCode or setPostCodes for postcodes. You can chain filters such as setProvince, setType, setFunction, setPaymentAvailable, and setUpdatedFrom or setUpdatedTo before calling build. Pass the built request to the FindPoints command's findPoints method and map the response into your Laravel domain objects.
- How do I filter Inpost pickup points by type, including refrigerated lockers?
- Use setType or setTypes on FindPointsRequestBuilder with the appropriate PointType values. Version 4.3.0 adds a refrigerated locker machine point type, so your Laravel wrapper should include it in a PointType enum and expose it to filtering and UI selection. If you do not map the new type explicitly, refrigerated lockers may be silently dropped from results or display logic.
- How do I configure Inpost API authentication for this bundle in Laravel?
- Inpost API authentication is not automatically wired into Laravel by this Symfony bundle. Store OAuth credentials or API keys in config/services.php and .env, then inject them into a configurable HTTP client or service provider that the bundle uses. Confirm the exact auth scheme in the Inpost API documentation and abstract it so tests can swap in fake credentials.
- Can I use Laravel's HTTP client instead of Symfony HttpClient with this bundle?
- Yes, but you need an adapter or wrapper because the bundle expects Symfony-style HttpClient and Serializer services. You can use symfony/http-client-bridge for minimal overhead or replace the client with Illuminate\Http\Client and map requests and responses carefully. Add contract tests to verify that filters, paging, and error handling still behave the same after the swap.
- How should I handle pagination, rate limits, and caching for large Inpost point searches?
- Use setPage and setPerPage to page through results instead of requesting everything at once. For 1000+ points, loop pages in a scheduled sync, cache the normalized results in Redis with a TTL, and implement retry logic with exponential backoff. Respect Inpost API rate limits and avoid calling the live API on every user request.
- How do I test Inpost pickup point search in Laravel without hitting the live API?
- Mock the Inpost API with Laravel's Http::fake or by injecting a fake client that implements the bundle's client interface. Write contract tests for FindPointsRequestBuilder filters, pagination, error responses, and the refrigerated locker type mapping. Since the bundle has no bundled tests, your own test suite is essential for reliability.
- Does answear/inpost-pickup-point-bundle support creating shipments or only pickup point search?
- The bundle is focused on read-only pickup point and parcel machine search through FindPointsRequestBuilder and FindPoints. It does not provide write operations such as shipment creation. If you need shipment creation, use the Inpost API directly with Laravel's HTTP client or supplement it with another package.
- What are alternatives to answear/inpost-pickup-point-bundle for Laravel Inpost integration?
- You can integrate the Inpost API directly using Laravel's HTTP client and build a small service or facade for pickup point search. Another option is to adapt this Symfony bundle with a Laravel wrapper that replaces Symfony dependencies and exposes a clean Inpost facade. Evaluate maintenance, test coverage, and whether you need only read operations or also shipment creation.
Weaver
How can I help you explore Laravel packages today?