Libraries tagged by payload

A library to navigate and access arbitrary payloads in a type-safe manner

Go to Download

A ServiceProvider that helps you to export a data resource from an api that returns a Laravel pagination payload

Go to Download

Simple SQS Extended Client is a SQS driver for Laravel that supports extended payloads beyond 256kb.

Go to Download

Simple SQS Extended Client is a SQS driver for Laravel that supports extended payloads beyond 256kb.

Go to Download

Generates payload to use with Disqus SSO

Go to Download

Biblioteca para geração do payload e QR Code estático do pix com PHP.

Go to Download

Library to convert bitbucket webhook payloads to typed objects

Go to Download

MVC config object used in RenderScript API request payload

Go to Download

A data mapper ORM utilizing simple payloads to transport data.

Go to Download

A lightweight and efficient PHP library for handling, validating, and transforming incoming HTTP requests, supporting both form submissions and JSON API payloads.

Go to Download

A PHP class for formatting error payloads.

Go to Download

PHP package to decrypt PaperScorer callback payloads.

Go to Download

Key–value store with JSON payloads

Go to Download

Forked firebase/php-jwt library to encode and decode JSON Web Tokens (JWT) in PHP with empty payload support.

Go to Download

The Nodeum API makes it easy to tap into the digital data mesh that runs across your organisation. Make requests to our API endpoints and we’ll give you everything you need to interconnect your business workflows with your storage. All production API requests are made to: http://nodeumhostname/api/ The current production version of the API is v1. **REST** The Nodeum API is a RESTful API. This means that the API is designed to allow you to get, create, update, & delete objects with the HTTP verbs GET, POST, PUT, PATCH, & DELETE. **JSON** The Nodeum API speaks exclusively in JSON. This means that you should always set the Content-Type header to application/json to ensure that your requests are properly accepted and processed by the API. **Authentication** All API calls require user-password authentication. **Cross-Origin Resource Sharing** The Nodeum API supports CORS for communicating from Javascript for these endpoints. You will need to specify an Origin URI when creating your application to allow for CORS to be whitelisted for your domain. **Pagination** Some endpoints such as File Listing return a potentially lengthy array of objects. In order to keep the response sizes manageable the API will take advantage of pagination. Pagination is a mechanism for returning a subset of the results for a request and allowing for subsequent requests to “page” through the rest of the results until the end is reached. Paginated endpoints follow a standard interface that accepts two query parameters, limit and offset, and return a payload that follows a standard form. These parameters names and their behavior are borrowed from SQL LIMIT and OFFSET keywords. **Versioning** The Nodeum API is constantly being worked on to add features, make improvements, and fix bugs. This means that you should expect changes to be introduced and documented. However, there are some changes or additions that are considered backwards-compatible and your applications should be flexible enough to handle them. These include: - Adding new endpoints to the API - Adding new attributes to the response of an existing endpoint - Changing the order of attributes of responses (JSON by definition is an object of unordered key/value pairs) **Filter parameters** When browsing a list of items, multiple filter parameters may be applied. Some operators can be added to the value as a prefix: - `=` value is equal. Default operator, may be omitted - `!=` value is different - `>` greater than - `>=` greater than or equal - `=` lower than or equal - `>

Go to Download