Libraries tagged by endpoints

Creates Endpoint for the WordPress Plugin ElasticPress to make use of the Autosuggest feature

Go to Download

A simple endpoint providing XLIFF translations as string

Go to Download

Wordpress custom endpoints helper and class generator.

Go to Download

Query anything you want from the WordPress database using a single REST API endpoint.

Go to Download

Laravel routes new (fast) experience

Go to Download

Drush commandfile for use with drupal/drupal-driver.

Go to Download

Plugin for netz98 Magerun2 to list all API endpoints

Go to Download

Wires app for the Elefant CMS auto-connects Alpine.js for easy single-page app development

Go to Download

Kirby 3 Plugin to call Instagram API Endpoints

Go to Download

Restrict/Disabled Rest API Endpoints.

Go to Download

A Laravel package for securely presigning actions on any entity, enabling controlled access and authorization without requiring users to share their passwords.

Go to Download

Prevent Laravel from using stale config or route cache after deployment changes, with Composer autoload integration and in-app auto repair for shared hosting.

Go to Download

Run pbmedia/laravel-ffmpeg jobs on a remote ffmpeg-api endpoint (verygoodffmpeg.com or a self-hosted instance) instead of the local ffmpeg binary, with automatic local fallback.

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

A minimal IndieAuth compatible token endpoint.

Go to Download