Libraries tagged by Web Cash
abdal-security-agency/abdal-php-waf
1545 Downloads
Web Application Firewall (WAF) package to Protect the pure PHP applications
web-id-fr/matryoshka
2811 Downloads
Russian Doll Caching for Laravel.
triangle/webanalyzer
51 Downloads
Localzet WebAnalyzer is a web analysis tool that analyzes website visitors, obtaining information about their device, operating system, browser, etc. It is developed by Localzet and uses modern technologies and standards to provide detailed and accurate information.
saft/saft-querycache
14 Downloads
QueryCache package from the library Saft.
cason-web-dev/laravel-azure-ad-oauth
3 Downloads
Provides single-sign-on ability to Microsoft Azure Active Directory enabled apps.
castamir/forms
442 Downloads
Nette Forms: greatly facilitates web forms
weaving-the-web/framework-extra-bundle
29 Downloads
This bundle provides helpers to ease the use of services and database fixtures within test cases
cascadepublicmedia/pbs-api-explorer
2 Downloads
Web interface for exploring various PBS APIs.
siteparts/plates-asset
22 Downloads
Generate cache busted web assets URLs in Plates
siteparts/asset
24 Downloads
Generate cache busted web assets URLs
maciejkosiarski/jwt-keeper-bundle
590 Downloads
Bundle to keep fresh and valid json web token in cache.
a2nt/silverstripe-progressivewebapp
589 Downloads
Tools to add offline caching and the other progressive web app functionality to your silverstripe website
patrikgrinsvall/xconsole
22 Downloads
Laravel xconsole is a local development web server in pure php with file watching, powerfull cache cleaning and more..
garyjl/simpletest
30 Downloads
Unit testing, mock objects and web testing framework for PHP built around test cases.
eciboadaptech/finapi-webform
314 Downloads
The following pages give you some general information on how to use our APIs.The actual API services documentation then follows further below. You can use the menu to jump between API sections.This page has a built-in HTTP(S) client, so you can test the services directly from within this page, by filling in the request parameters and/or body in the respective services, and then hitting the TRY button. Note that you need to be authorized to make a successful API call. To authorize, refer to the 'Authorization' section of Access, or in case you already have a valid user token, just use the QUICK AUTH on the left.Please also remember that all user management functions should be looked up in Access.You should also check out the Web Form 2.0 Public Documentation as well as Access Public Documentation for more information. If you need any help with the API, contact [email protected] informationRequest IDsWith any API call, you can pass a request ID via a header with name "X-Request-Id". The request ID can be an arbitrary string with up to 255 characters. Passing a longer string will result in an error.If you don't pass a request ID for a call, finAPI will generate a random ID internally.The request ID is always returned back in the response of a service, as a header with name "X-Request-Id".We highly recommend to always pass a (preferably unique) request ID, and include it into your client application logs whenever you make a request or receive a response(especially in the case of an error response). finAPI is also logging request IDs on its end. Having a request ID can help the finAPI support team to work more efficiently and solve tickets faster.Type CoercionIn order to ease the integration for some languages, which do not natively support high precision number representations, Web Form 2.0 API supports relax type binding for the openAPI type number, which is used for money amount fields. If you use one of those languages, to avoid precision errors that can appear from float values, you can pass the amount as a string.FAQIs there a finAPI SDK?Currently we do not offer a native SDK, but there is the option to generate an SDKfor almost any target language via OpenAPI. Use the 'Download SDK' button on this page for SDK generation.Why do I need to keep authorizing when calling services on this page?This page is a "one-page-app". Reloading the page resets the OAuth authorization context. There is generally no need to reload the page, so just don't do it and your authorization will persist.