Libraries tagged by php http service
neutrondev/new-nusoap
7 Downloads
New NuSoap
neoxygen/graphenedb-client
24 Downloads
Http Client for the GrapheneDB Neo4j as as Service
mopinion/api
22 Downloads
PHP client for the Mopinion API.
mammutgroup/pushok
28 Downloads
PHP client for Apple Push Notification Service (APNs) - Send push notifications to iOS using the new APNs HTTP/2 protocol with token-based (JWT with p8 private key) or certificate-based authentication
macleen/mcl-router
2 Downloads
Light weight php router
lelush/laravel-apn-notification-channel
2 Downloads
Apple Push Notification Service (APNs) notifications channel for Laravel 5.3+ using the new APNs HTTP/2 protocol with token-based (JWT with p8 private key)
just-core/threatcrowd
39 Downloads
PHP Wrapper for https://github.com/threatcrowd/ApiV2
joshybadev/easybroker
5 Downloads
easybroker is a PHP client library consult copy easybroker_gem
jonnyd/peggy
43 Downloads
PHP wrapper for 80legs.com API
exertis/yii2-experian-qas
17 Downloads
Experian QAS Pro On Demand Postocde lookup SOAP service integration for the Yii framework. See also http://support.qas.com/experian_qas_pro_ondemand__php_only__technical_update_2021.htm
exeerik/pushok
81 Downloads
Customized PHP client for Apple Push Notification Service (APNs) - Send push notifications to iOS using the new APNs HTTP/2 protocol with token-based (JWT with p8 private key) or certificate-based authentication
esiswag/esiswag
15 Downloads
Swag is a PHP library for interacting with the EVE ESI API.
ervinomueller/cpfcnpj-client
103 Downloads
Client wrapper for cpfcnpj.com.br service
emyu10/viber-rest
20 Downloads
A PHP wrapper around Viber REST API.
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.