Libraries tagged by api development
prem-techchef/laravel-shopify
2 Downloads
Shopify package for Laravel to aide in app development
piratepixelx/larapikit
8783 Downloads
LarapiKit is a versatile and robust Laravel API package designed to simplify and enhance your web application development process. With a focus on security time saving and easy integration, this package empowers developers to streamline their API-related tasks, saving time and effort.
php-mohamed-nabil/marrow-framework
29 Downloads
marrow is a php MVC Framwork for building php web application with a good mvc pattern structure makes development more easier
petrov-codedot/shopify-laravel-9
17 Downloads
Shopify package for Laravel to aide in app development
openspring/springphp-framework
107 Downloads
The SpringPHP framework
npabisz/laravel-shopify
1 Downloads
Shopify package for Laravel to aide in app development
nathan-degraaf/laravel-shopify
1 Downloads
Shopify package for Laravel to aide in app development
nael_d/ornata
0 Downloads
Ornata: A user-friendly meticulously crafted PHP MVC framework, empowering developers to build elegant and powerful web applications.
mikkokut/prismic-laravel
1417 Downloads
Integrates the Prismic PHP development kit with Laravel.
merchantprotocol/laravel-shopify
12 Downloads
Shopify package for Laravel to aide in app development
melodiev/laravel-shopify
22 Downloads
Shopify package for Laravel to aide in app development
magefan/laravel-shopify
23 Downloads
Shopify package for Laravel to aide in app development
mage2pro/robokassa
173 Downloads
Robokassa (Робокасса) integration with Magento 2
leibbrand-development/sdk-ebay-inventory
1 Downloads
The Inventory API is used to create and manage inventory, and then to publish and manage this inventory on an eBay marketplace. There are also methods in this API that will convert eligible, active eBay listings into the Inventory API model.
leibbrand-development/php-docker-client
22 Downloads
The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.41) is used. For example, calling `/info` is the same as calling `/v1.41/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```