Libraries tagged by OpenAi Sdk

bricre/amazon-selling-partner-sdk-finances

0 Favers
1 Downloads

API client generated from OpenAPI definition from Amazon Selling Partner API for Finances

Go to Download


bricre/amazon-selling-partner-sdk-feeds

0 Favers
1 Downloads

API client generated from OpenAPI definition from Amazon Selling Partner API for Feeds

Go to Download


bricre/amazon-selling-partner-sdk-fba-small-and-light

0 Favers
1 Downloads

API client generated from OpenAPI definition from Amazon Selling Partner API for FBA Small And Light

Go to Download


bricre/amazon-selling-partner-sdk-fba-inventory

0 Favers
0 Downloads

API client generated from OpenAPI definition from Amazon Selling Partner API for FBA Inventory

Go to Download


bricre/amazon-selling-partner-sdk-fba-inbound-eligibility

0 Favers
1 Downloads

API client generated from OpenAPI definition from Amazon Selling Partner API for FBA Inbound Eligibilty

Go to Download


bricre/amazon-selling-partner-sdk-catalog-items

0 Favers
0 Downloads

API client generated from OpenAPI definition from Amazon Selling Partner API for Catalog Items

Go to Download


bricre/amazon-selling-partner-sdk-authorization

0 Favers
1 Downloads

API client generated from OpenAPI definition from Amazon Selling Partner API for Authorization

Go to Download


bricre/amazon-selling-partner-sdk-aplus-content

0 Favers
0 Downloads

API client generated from OpenAPI definition from Amazon Selling Partner API for A+ Content Management

Go to Download


bleumi/payment-sdk-php

0 Favers
4 Downloads

A simple and powerful REST API to integrate Traditional (Credit/Debit Card, Alternative Payment Methods) and Crypto Currency (Bitcoin, Ethereum, Stablecoins) payments into your business or application. ### Getting Started 1. Create an account on [Bleumi](https://account.bleumi.com/signUp/?app=payment) 1. Fill up your [profile](https://account.bleumi.com/account/?app=payment&tab=profile) 1. Complete your KYC by contacting [[email protected]](mailto:[email protected]) 1. Add your preferred payment service providers in the [Bleumi Portal](https://account.bleumi.com/account/?app=payment&tab=gateway) 1. Create your API key on the [Bleumi Integration Settings](https://account.bleumi.com/account/?app=payment&tab=integration) screen ### Authentication Bleumi uses API keys to authenticate requests. You can view and manage your API keys in the [Bleumi Integration Settings](https://account.bleumi.com/account/?app=payment&tab=integration) screen. Authenticated API requests should be made with a `X-Api-Key` header. Your API key should be passed as the value. ### Payment Methods Use the [Bleumi Portal](https://account.bleumi.com/account/?app=payment&tab=gateway) to add your preferred payment service provider (e.g. Stripe, BitPay, Bleumi Pay) and configure the payment methods that buyers would be able to use to make payments.

Go to Download


be-lenka/tracify-php-sdk

0 Favers
0 Downloads

This API allows you to send events to Tracify that originate from your server.

Go to Download


bank-io/bankio-sdk-php

1 Favers
104 Downloads

# 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


ayinkellc/otito-php-sdk

1 Favers
0 Downloads

Otito PHP SDK. Generated from swagger file

Go to Download


avalara/avalara_sdk

0 Favers
0 Downloads

API for evaluating transactions against direct-to-consumer Beverage Alcohol shipping regulations. This API is currently in beta.

Go to Download


apimatic-moizgillani/swagger-petstore-3-sdk

0 Favers
0 Downloads

This is a sample Pet Store Server based on the OpenAPI 3.0 specification.

Go to Download


allenqin/mz-aliyun-php-sdk

1 Favers
103 Downloads

aliyun OSS openapi

Go to Download


<< Previous Next >>