Libraries tagged by json generator

The Pi-hole API is organized around [REST](http://en.wikipedia.org/wiki/Representational_State_Transfer). Our API has predictable resource-oriented URLs, accepts and returns reliable UTF-8 [JavaScript Object Notation (JSON)-encoded](http://www.json.org/) data for all API responses, and uses standard HTTP response codes and verbs. Most (but not all) endpoints require authentication. API endpoints requiring authentication will fail with code `401 Unauthorized` when used outside a valid session.

Go to Download

# Code of Conduct Please don't abuse the API, and please report all feature requests and issues to https://support.atlassian.com/contact # Rate Limiting Each API token is limited to 1 request / second as measured on a 60 second rolling window. To get this limit increased, please contact us at https://support.atlassian.com/contact Error codes 420 or 429 indicate that you have exceeded the rate limit and the request has been rejected. # Basics ## HTTPS It's required ## URL Prefix In order to maintain version integrity into the future, the API is versioned. All calls currently begin with the following prefix: https://api.statuspage.io/v1/ ## RESTful Interface Wherever possible, the API seeks to implement repeatable patterns with logical, representative URLs and descriptive HTTP verbs. Below are some examples and conventions you will see throughout the documentation. * Collections are buckets: https://api.statuspage.io/v1/pages/asdf123/incidents.json * Elements have unique IDs: https://api.statuspage.io/v1/pages/asdf123/incidents/jklm456.json * GET will retrieve information about a collection/element * POST will create an element in a collection * PATCH will update a single element * PUT will replace a single element in a collection (rarely used) * DELETE will destroy a single element ## Sending Data Information can be sent in the body as form urlencoded or JSON, but make sure the Content-Type header matches the body structure or the server gremlins will be angry. All examples are provided in JSON format, however they can easily be converted to form encoding if required. Some examples of how to convert things are below: // JSON { "incident": { "name": "test incident", "components": ["8kbf7d35c070", "vtnh60py4yd7"] } } // Form Encoded (using curl as an example): curl -X POST https://api.statuspage.io/v1/example \ -d "incident[name]=test incident" \ -d "incident[components][]=8kbf7d35c070" \ -d "incident[components][]=vtnh60py4yd7" # Authentication

Go to Download

Laravel AI-Native API Framework - Générez des APIs Laravel complètes à partir de schémas JSON

Go to Download

A PHP report generator that work in symfony

Go to Download

This package helps generate HTML Forms from JSON

Go to Download

Simple configuration generator for PHP projects

Go to Download

A fluent builder Schema.org types and ld+json generator

Go to Download

A fluent builder Schema.org types and ld+json generator

Go to Download

Twig and JSON static site generator. Includes watcher for view file changes in frontend development and an API for other pure frontend projects.

Go to Download

A blazing-fast static site generator that uses JSON content files and the Laravel blade templating engine

Go to Download

A Laravel command that helps generate your models and migrations from a json file created with ifriqiya generator

Go to Download

Sitemap generator in XML, CSV, JSON

Go to Download

Simple CRUD generator for Laravel framework bwith json files

Go to Download

Symfony bundle generator from swagger interface (yml or json)

Go to Download

Laravel Generator , For api base CRUD , Management request , handler response with JSON.

Go to Download