Libraries tagged by query scope

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

Global query scopes for Doctrine2

Go to Download

Laravel query scoping library for dynamic filtering

Go to Download

Simple, explicit permission checks and row-level query scopes constraining what data a user can access

Go to Download

Query criteria scopes by OOP.

Go to Download

Simple API query string scope recognizer

Go to Download

Scopes are used to execute query limits.

Go to Download

A package to simply query your datasets.

Go to Download

Adds sorting, filtering and other options as query parameters to Laravel apps.

Go to Download

Add some custom scopes on models to make a better selection via requests

Go to Download

Behaviors for Yii2

Go to Download

Configurable district-based query scoping and access control for Laravel applications.

Go to Download

Symfony bundle for dynamic filtering, pagination and user-scoped queries with Doctrine ORM

Go to Download

Generate Eloquent Builder class for enhanced query building and model scope management.

Go to Download

Query builder for models and entities.

Go to Download