Libraries tagged by api bindings

PHP SOAP bindings for the Visualsoft V3 API

Go to Download

PHP Binding for the FLYERALARM Reseller API.

Go to Download

Bindings and implementation of the REST side of the Copernica API

Go to Download

This library turns the Contao Core API into events.

Go to Download

VMWare vSphere API bindings for PHP

Go to Download

PHP API bindings for vSphere/vCenter

Go to Download

Simple Akismet API Bindings

Go to Download

Laravel 4.2 integration for the Stathat API

Go to Download

AtPay API bindings for PHP

Go to Download

AtPay API bindings for PHP

Go to Download

Monscierge API bindings for PHP.

Go to Download

Nette extension for the Intercom API PHP Bindings.

Go to Download

PortaOne billing and ESPF API wrappers, Guzzle bindings

Go to Download

PHP bindings for Upwork API

Go to Download

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.

Go to Download