Libraries tagged by binning

A binding component for PHP applications, enabling efficient registration and resolution of abstract types.

Go to Download

A lightweight, flexible string processing and template engine for PHP with function chaining support.

Go to Download

LibSDL3 Bindings for The PHP SDL3 Extension

Go to Download

OpenGL Bindings for The PHP OpenGL Extension

Go to Download

MPSSE SPI/I2C/GPIO helpers extending the FTDI package

Go to Download

macOS Metal + AppKit Bindings for The PHP Metal Extension

Go to Download

LibGLFW Bindings for The PHP GLFW Extension

Go to Download

libFTDI Bindings for The PHP FTDI Extension

Go to Download

This library provides simple access to the public transportation association KVV in Karlsruhe. It is based on unofficial data sources which are therefore subject to change without notice.

Go to Download

Laravel Sqids (next-gen Hashids) package for encoding and decoding database IDs with route model binding support

Go to Download

Use auto generated UUID slugs to identify and retrieve your Eloquent models.

Go to Download

Vmware vSphere bindings for PHP

Go to Download

Laravel validation rule to check if a custom route key exists.

Go to Download

Laravel Package Bindify is a package that helps you to bind your classes to the Laravel service container

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