Download the PHP package daika7ana/dpd-php-sdk without Composer

DPD PHP SDK

🚀 Framework-agnostic, DPD-credential-based, fully typed with DTOs, and built for production integrations.

Table of Contents

• Features
• Requirements
• Installation
• Quick Start
• Configuration
• Authentication
• Supported Resources
• Operational Notes
• Testing
• Documentation

Features

Core Strengths

• ✅ Fully Typed DTOs — Explicit request and response objects across the implemented API surface
• ✅ Immutable Client Configuration — Optional environment bootstrapping without mutable runtime defaults
• ✅ PSR-18 HTTP Client — Guzzle wired by default with custom client seams when needed
• ✅ Mixed Response Handling — Shared JSON, binary, and CSV support for DPD's rough edges
• ✅ Typed Exception Mapping — Transport, authentication, validation, and API failures are separated cleanly
• ✅ Reference-Data Caching — Optional caching for CSV-backed location imports
• ✅ Batching Helpers — Explicit support for capped flows such as batched tracking and bulk hydration

Good Fit For

• 🎯 Laravel applications or any PHP framework
• 🎯 Standalone PHP services and worker processes
• 🎯 Integrations that need explicit shipment and location payloads instead of raw arrays
• 🎯 Teams that want predictable local verification through unit tests, static analysis, and smoke checks

Requirements

• PHP 8.3+
• PSR-7, PSR-17, and PSR-18 compatible environment

Installation

Via Composer

Quick Start

For a full end-to-end walkthrough, continue with docs/EXAMPLES.md.

Configuration

ClientConfig keeps connection settings explicit and immutable:

• baseUrl
• username
• password
• language
• clientSystemId
• timeout
• connectTimeout

Use ClientConfig::fromEnvironment() when you want configuration to come from environment variables instead of application code.

Authentication

DPD uses static credentials on every request payload instead of OAuth.

The client injects these values automatically:

• userName
• password
• language
• clientSystemId when configured

For multi-tenant or rotating-credential setups, you can inject a custom credentials provider into Client::create().

Supported Resources

• services() for service catalog and destination-aware service discovery
• shipments() for create, cancel, update, lookup, barcode, add-parcel, and handover flows
• locations() for detail lookups, capped searches, nearest-office search, and CSV-backed reference data
• printing() for PDF or ZPL labels, extended print metadata, and vouchers
• tracking() for direct tracking, batched tracking, and bulk tracking file discovery
• pickup(), validation(), calculations(), clients(), and payments() for the remaining operational endpoints

Operational Notes

• DPD credentials are attached to every request payload, so request logging should always be treated as sensitive.
• Printing endpoints may return binary documents on success and JSON errors on failure. Use printing() or sendBinary() for those flows.
• Location search endpoints are capped by DPD. Use find*() for interactive lookup and all*() for full CSV-backed datasets.
• tracking()->track() keeps the upstream 10-parcel limit visible. Use trackBatched() when you want explicit chunking.
• Non-ASCII address data may still be affected by legacy transliteration rules in DPD label and back-office tooling. Validate with real labels before rollout.

Testing

Run The Local Verification Pipeline

Run Smoke Tests Against A Live DPD Account

composer ci runs formatting, static analysis, and the unit suite. Smoke tests skip automatically when the required environment values are missing.

Documentation

Complete guides and references: