Libraries tagged by Sdds

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

Unofficial, unaffiliated PHP SDK for the TypeSafe AI System One API, with 1:1 parity to the official JavaScript and Python SDKs.

Go to Download

The core PHP SDK classes used by the Treblle SDKs.

Go to Download

A fluent PHP library for creating API SDKs with PSR-18, PSR-17, PSR-6 and PSR-3 support

Go to Download

php sdkSina Weibo open platform business php sdk

Go to Download

Provides SDD context for AI models.Guidelines, best practices for Symfony projects Hexagonal

Go to Download

Application to generate constrained SKDs based on JSON schemas

Go to Download

Client and mapper for REST API SDKs

Go to Download

Framework-independent event and transport core for Apirelio PHP SDKs.

Go to Download

Componente de uso comum entre SDKs para integração a partir de aplicações PHP com Restful webservices

Go to Download

阿里云SDK集合整理

Go to Download

sds

Go to Download

Integracion con API de Sirena

Go to Download

Set laravel schema default string length.

Go to Download

Collector addon for handling notifications from Microsoft SNDS

Go to Download