Libraries tagged by json to object
johyunchol/php-gson2
19 Downloads
PHP GSON equivalent - simple entity mapper. JSON to object and object to JSON. from archangeldesign/php-gson
archangeldesign/php-gson
93 Downloads
PHP GSON equivalent - simple entity mapper. JSON to object and object to JSON
fwhat/jsonmapper
8 Downloads
json to php object
ascott/entity-transformer
8 Downloads
This is a module that applies JSON transformations to objects
porifa/jarason
7 Downloads
Laravel Json API Response to Object Mapper
lsv/fifa-worldcup-parser
14 Downloads
Parse worldcup json data to PHP objects
jarivas/php-popo-models
14 Downloads
A simple and direct way of casting json objects to models
onlyongunz/renton-php
4 Downloads
Jadwal Student Portal to JSON Object
taquillacom/gson-php
504 Downloads
Gson for PHP: Convert PHP objects to and from json
paysera/lib-normalization
17926 Downloads
Library for normalizing and denormalizing PHP objects to and from JSON structures
atiksoftware/gson-php
0 Downloads
Gson for PHP: Convert PHP objects to and from json
ajbassett539/simple-response
9 Downloads
Simple Object to Easily Create JSON Output
ttree/serializer
142 Downloads
Package for TYPO3 Flow to convert PHP object to and from JSON
rekhyt/dto
4797 Downloads
Use the JSON Schema spec to define Data Transfer Objects (DTOs)
nodeum-io/nodeum-sdk-php
0 Downloads
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 - `>