Libraries tagged by http request
ekrouzek/pagination-filters-bundle
233 Downloads
Filtering, sorting and pagination bundle for paginated http requests.
coka/cors-bundle
1504 Downloads
Allows multi origin HTTP requests (CORS) supports
codelab/flaskhttp
5939 Downloads
FlaskHTTP - a neat and tidy HTTP request component by Codelab
beyond/supports
3928 Downloads
http request
beblife/schema-validation-laravel
10076 Downloads
Validate HTTP-requests using JSON-schema objects
altra/context
3435 Downloads
Library to filter HTTP request responses by context.
ahmadwaleed/laravel-blanket
1834 Downloads
A blanket which wraps your laravel http client, and provides dashboard to access logs, retry and debug your http requests.
stephenjude/simple-query-filter
155 Downloads
Easily filter eloquent model queries from HTTP requests
stechstudio/laravel-aws-lambda
442 Downloads
Allows php to respond to http requests on aws lambda
netglue/zf2-ssl-module
23385 Downloads
ZF2 Module that helps enforce the use of an SSL connection for HTTP requests
vira/hpropagate
2178 Downloads
Symfony bundle for propagating http headers from incoming requests to the corresponding outgoing requests automatically
1msg/one_msg_waba_sdk
2711 Downloads
[1MSG.IO](https://1msg.io/) is the perfect WhatsApp management tool for your business. With us you get full access to the official Whatsapp API/webhooks. Every API request must contain an Authorize HTTP header with a token. This is your channel token, which can be found in your channel project on your profile page. Please do not give the token to anyone or post it publicly. The authorization token must be added to each request in the GET parameter 'token' and always passed to query string (?token={your_token}). Parameters in GET queries pass query string. Parameters in POST requests — through the JSON-encoded request body. All 'send' methods (except /sendTemplate) will only work when the dialog session with the user is open. Some of our solutions simplify and avoid such limitations, but we urge you to pay more attention to this detail
lexpress/sf-web-browser-plugin
61101 Downloads
HTTP client capable of making web requests now available as service.
vitexsoftware/rbczpremiumapi
203 Downloads
##### API Overview - Accounts list and balance - Transaction overview (also for saving accounts) - Payments import - Statement list and download - FX rates ##### Authentication Before making a call to Premium API, you need to register your app at our _Developer portal_. This is where you get the **ClientID** that your application must send in the request as `X-IBM-Client-Id`. This is the key that grants your app access to the API. However, this may not be enough. Your application needs to use mTLS to call most operations here. Thus, you not only need _https_ but also a client certificate issued by us. The exception is two operations for FX rates that are accessible also without a client certificate. Each bank client/user can issue several certificates. Each certificate can permit different sets of operations (http methods) on different bank accounts. All this must be configured in Internet Banking first by each bank client/user (bank clients need to look under _Settings_ and do not forget to download the certificate at the last step). The certificate is downloaded in **PKCS#12** format as **\*.p12** file and protected by a password chosen by the bank client/user. Yes, your app needs the password as well to get use of the **\*p12** file for establishing mTLS connection to the bank. Client certificates issued in Internet Banking for bank clients/users have limited validity (e.g. **5 years**). However, **each year** certificates are automatically blocked and bank client/user must unblock them in Internet Banking. It is possible to do it in advance and prolong the time before the certificate is blocked. Your app should be prepared for these scenarios and it should communicate such cases to your user in advance to provide seamless service and high user-experience of your app. ##### Rate Limiting The number of requests in each API operation is limited to 10 per client per sliding second and 5000 per client per sliding day. The exception is the 'Download Statement' operation with the limits lowered to 5 per client per sliding second and 1500 per client per sliding day. This is because it transports potentially sizeable binary files. The consumer must be able to handle HTTP status 429 in case of exceeding these limits. Response headers `X-RateLimit-Limit-Second` and `X-RateLimit-Limit-Day` show the actual limits configured for the specific operation. Response headers `X-RateLimit-Remaining-Second` and `X-RateLimit-Remaining-Day` are returned to help prevent the limits from being exceeded. ##### Notes Be aware, that in certain error situations, API can return specific error structures along with 5xx status code, which is not explicitely defined below. ##### Quick Start Client Feel free to download a simple Java client that gives you quick access to our API.
poor-plebs/guzzle-connect-retry-decider
1927 Downloads
A guzzle retry middleware decider that re-attempts requests whenever a connection fails to be established. Always retries up to x times for GET requests and under specific conditions also for other HTTP methods.