Libraries tagged by shipping php api

PHP client for the Czech Post (Česká pošta) B2B ZSKService API

Go to Download

Intelipost Logistics Gateway PHP SDK

Go to Download

PHP and Laravel client for the Reverb.com marketplace API: listings, orders, shipping, offers, refunds, payouts and webhooks. Not related to Laravel Reverb (WebSockets).

Go to Download

karrio Multi-carrier Shipping API PHP client library

Go to Download

Simple client library for PHP to create shipments using smartpost web service

Go to Download

PHP client for the Furgonetka.pl REST API: OAuth2, price comparison, shipments, labels, pickups, tracking, pickup points, returns, address book, notifications and webhooks. One API for DPD, InPost, DHL, UPS, GLS, FedEx, Poczta Polska, ORLEN Paczka and more.

Go to Download

API Wrapper for Fedex web services

Go to Download

Pop Shipping Component for Pop PHP Framework

Go to Download

The PHP SDK of AfterShip API

Go to Download

The PHP SDK of 51Tracking API

Go to Download

Modern PHP/Laravel client for EasyShip API with full endpoint coverage

Go to Download

Typed PHP SDK for the Ecolet Courier API.

Go to Download

PHP SDK to integrate with Aftership API

Go to Download

Royal Mail Shipping REST API Client

Go to Download

Public API documentation for Zippendo. Authenticate using your API token (Bearer token prefixed with zipp_). **Brands (sub-accounts).** An organization can be split into brands, each keeping its own orders, shipments and configuration separate. There are two ways to scope requests to one brand, and NEITHER changes any request body: 1. **Bind the token.** Create an API token with a `brandId` and every request it makes is confined to that brand — reads filtered, writes stamped. This is the recommended way to give a single brand's team its own credential. 2. **Send the `X-Zippendo-Brand` header.** An organization-wide token can scope an individual request by sending the brand's id or slug in this header. Most SDKs let you set it once on the client so every call inherits it. A brand-bound token that receives an `X-Zippendo-Brand` header naming a different brand is rejected with `403 BRAND_ACCESS_DENIED` — the binding is never widened. Omit both and requests cover the whole organization, which is the behaviour of every existing token. Records that belong to no brand carry `brandId: null`. Configuration (carriers, shipping rules, addresses) with a null brand is organization-wide and remains visible inside every brand; orders and shipments with a null brand are only visible organization-wide. List endpoints additionally take a `?brandScope=own|shared|both` parameter to narrow further within whichever brand context already applies. `own` returns only rows assigned to that brand, and requires a brand context — a brand-bound token, a resolved brand session, or the `X-Zippendo-Brand` header above — otherwise `400`. `shared` returns only the organization-wide rows (equivalent to filtering `brandId=none`). The default, `both`, keeps the existing behaviour: a brand context sees its own rows plus the organization-wide ones. Set `X-Zippendo-Brand-Scope` as a client default to apply the same choice to every request instead of repeating the query parameter on each call — an explicit `brandScope` query parameter always wins over the header, and a blank header value is ignored. Brands themselves are managed under the **Brands** tag. Retiring a brand is done with `POST /orgs/{orgId}/brands/{brandId}/archive` — permanent deletion is a dashboard-only action, since it is refused while any order, shipment, member or token still references the brand. Brands require a plan that includes them; creating one beyond your plan's limit returns `403`.

Go to Download