Libraries tagged by github_hook

The Docusign package makes integrating Docusign into your apps and websites a super fast and painless process. The library is open sourced on GitHub, look for the docusign-maestro-php-client repository.

Go to Download

The DocuSign PHP library makes integrating DocuSign into your websites a super fast and painless process. The library is open sourced on GitHub, look for the docusign-php-client repository. Join the eSign revolution!

Go to Download

a small framework to handle PHP projects. Look for more details on github at https://github.com/TrueArrowSoftware/TASLibPHP

Go to Download

Symfony bundle for implementing Cookie Consent to comply to AVG/GDPR. Based on https://github.com/Harborn-digital/cookie-consent-bundle and adapted to meet symfony 6.4 requirements.

Go to Download

Responsive cookie consent plugin for Contao. The plugin provides different cookie privacy settings for the visitor. Google Analytics is only loaded when the visitor agrees to enable statistics. The plugin supports OnePages - no need to reload page after setting privacy settings. Installation instructions: https://github.com/ckarisch/ContaoCookieConsentBundle

Go to Download

My book library

Go to Download

This is rewriten [https://github.com/bastianallgeier/gantti] Gantt Class to fit my needs Eg. To show multiple events (bookings) per resource and Laravel 4 compatibility

Go to Download

Parses strings for docBlock like portions and then extracts the annotations, descriptions, and optional document content. This should not be used as an annotation parser for PHP code, at least not on it's own. If you're looking to do something with the docBlocks you might want to use something like https://github.com/schmittjoh/metadata better. This is more for if you're trying to get metadata from a plain text file. Look through the tests for examples.

Go to Download

SDK for API https://github.com/xandrman/booking-api

Go to Download

Api wrapper for https://github.com/Chubik/phpdevtest/

Go to Download

just a wrapper of itune open api. https://github.com/ijanerik/PHP-iTunes-API

Go to Download

Package to create and stream e-books in the ePub 2.0 and 3.0 formats. forked from Grandt/PHPePub https://github.com/Grandt/PHPePub

Go to Download

A Laravel Package for nearly 2500 Bible versions available across over 1600 languages, powered by API.Bible.

Go to Download

This is rewriten [https://github.com/bastianallgeier/gantti] Gantt Class to fit my needs Eg. To show multiple events (bookings) per resource and Laravel 5.3 compatibility

Go to Download

# Summary The **NextGenPSD2** *Framework Version 1.3.6* (with errata) offers a modern, open, harmonised and interoperable set of Application Programming Interfaces (APIs) as the safest and most efficient way to provide data securely. The NextGenPSD2 Framework reduces XS2A complexity and costs, addresses the problem of multiple competing standards in Europe and, aligned with the goals of the Euro Retail Payments Board, enables European banking customers to benefit from innovative products and services ('Banking as a Service') by granting TPPs safe and secure (authenticated and authorised) access to their bank accounts and financial data. The possible Approaches are: * Redirect SCA Approach * OAuth SCA Approach * Decoupled SCA Approach * Embedded SCA Approach without SCA method * Embedded SCA Approach with only one SCA method available * Embedded SCA Approach with Selection of a SCA method Not every message defined in this API definition is necessary for all approaches. Furthermore this API definition does not differ between methods which are mandatory, conditional, or optional. Therefore for a particular implementation of a Berlin Group PSD2 compliant API it is only necessary to support a certain subset of the methods defined in this API definition. **Please have a look at the implementation guidelines if you are not sure which message has to be used for the approach you are going to use.** ## Some General Remarks Related to this version of the OpenAPI Specification: * **This API definition is based on the Implementation Guidelines of the Berlin Group PSD2 API.** It is not a replacement in any sense. The main specification is (at the moment) always the Implementation Guidelines of the Berlin Group PSD2 API. * **This API definition contains the REST-API for requests from the PISP to the ASPSP.** * **This API definition contains the messages for all different approaches defined in the Implementation Guidelines.** * According to the OpenAPI-Specification [https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.1.md] "If in is "header" and the name field is "Accept", "Content-Type" or "Authorization", the parameter definition SHALL be ignored." The element "Accept" will not be defined in this file at any place. The elements "Content-Type" and "Authorization" are implicitly defined by the OpenApi tags "content" and "security". * There are several predefined types which might occur in payment initiation messages, but are not used in the standard JSON messages in the Implementation Guidelines. Therefore they are not used in the corresponding messages in this file either. We added them for the convenience of the user. If there is a payment product, which needs these fields, one can easily use the predefined types. But the ASPSP need not to accept them in general. * **We omit the definition of all standard HTTP header elements (mandatory/optional/conditional) except they are mentioned in the Implementation Guidelines.** Therefore the implementer might add these in his own realisation of a PSD2 comlient API in addition to the elements defined in this file. ## General Remarks on Data Types The Berlin Group definition of UTF-8 strings in context of the PSD2 API has to support at least the following characters a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 0 1 2 3 4 5 6 7 8 9 / - ? : ( ) . , ' + Space

Go to Download