Libraries tagged by post request

Sends a HTTP 410 (Gone) response to requests for trashed posts/pages.

Go to Download

The helpers allows you to Request processing. Get value for POST/GET/REQUEST method by key and set default value, check exist AJAX, POST and GET method - all this is available in this library.

Go to Download

ZN Framework Request Package

Go to Download

超级灵活，强大，可自定义的curl http请求类， 可伪装来源，agent, 伪装IP地址等等，支持POST, GET等方式

Go to Download

Allows multiple groups of posts with different filters to be obtained from the WP-API in a single request

Go to Download

PHP library for handling requests.

Go to Download

Populate given object from POST request - both from $_POST and $_FILES

Go to Download

Simple input for get request inputs (post,get,put,delete)

Go to Download

A small, lightweight utility to perform curl calls using GET, POST, PUT, PACTH, DELETE, HEAD, TRACE, OPTIONS methods...

Go to Download

`codekandis/curly-brace` is a library providing cURL wrapper interfaces and classes to handle requests and responses.

Go to Download

AsZone Component - Fake Headers

Go to Download

Interconnector is a REST-based Web-Service to integrate information systems of DPD customers, which through POST requests allows using DPD services provided. Interconnector allows to use DPD services by transmitting shipment information, requesting package pickups, printing parcel labels, etc.

Go to Download

Welcome to the Svix API documentation! Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:[email protected]) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/) # Introduction This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com). ## Main concepts In Svix you have four important entities you will be interacting with: - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint. ## Authentication Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. For more information on authentication, please refer to the [authentication token docs](https://docs.svix.com/api-keys). ## Code samples The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/). ## Idempotency Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response. To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions. Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result. Please note that idempotency is only supported for `POST` requests. ## Cross-Origin Resource Sharing This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site.

Go to Download

Create Rest Request (POST,GET,PUT,DELETE,...)

Go to Download

A simple laravel/lumen middleware for denying non-json POST and PUT requests.

Go to Download