Libraries tagged by http POST

portrino/typo3-fractal-view

3 Favers
34 Downloads

Integrates the fractal package (https://fractal.thephpleague.com/) into TYPO3 Extbase

Go to Download


bleumi/payment-sdk-php

0 Favers
5 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


nedmas/slate

1 Favers
11 Downloads

Slate is theme for GitHub Pages or your Sculpin site. Ported from https://github.com/jasoncostello/slate

Go to Download


hariharan/open-tamil

2 Favers
0 Downloads

Open Tamil is PHP Port for https://github.com/Ezhil-Language-Foundation/open-tamil/

Go to Download


easybib/travis-artifacts

1 Favers
7 Downloads

PHP port of https://github.com/travis-ci/travis-artifacts

Go to Download


devgroup/bh

0 Favers
540 Downloads

Template engine. BEMJSON -> HTML processor. PHP port of https://github.com/bem/bh

Go to Download


wtnabe/ga-shikomi-php

1 Favers
377 Downloads

PHP port of https://github.com/wtnabe/ga-shikomi

Go to Download


rhdc/akamai-middleware

0 Favers
46 Downloads

PSR-7 HTTP client middleware for Akamai-hosted sites

Go to Download


techworker/nano

0 Favers
12 Downloads

Simple, small and fast String templating functionality ported from the original https://github.com/trix/nano.

Go to Download


hypermed/nsi-api-client

0 Favers
104 Downloads

Client for working with NSI API (https://nsi.rosminzdrav.ru/port)

Go to Download


fardus/lftp

2 Favers
245 Downloads

lftp is a file transfer program that allows sophisticated FTP, HTTP and other connections to other hosts. If site is specified then lftp will connect to that site otherwise a connection has to be established with the open command.

Go to Download


websemantics/file-icons

3 Favers
171 Downloads

File specific icons for PHP. A port of Atom File-icons, https://github.com/file-icons/atom

Go to Download


razorbacks/blackboard-rest-api-wrapper

2 Favers
210 Downloads

Lightweight wrapper for https://developer.blackboard.com/portal/displayApi

Go to Download


itrends/taecel

0 Favers
24 Downloads

Libreria de laravel para trabajar con taecel: https://taecel.com/portal/

Go to Download


fwrepae/fwrepae

0 Favers
0 Downloads

The Inter TT REST API is described using OpenAPI 3.0. The descriptor for the api can be downloaded in both [YAML](http://localhost:8080/cyclos/api/openapi.yaml) or [JSON](http://localhost:8080/cyclos/api/openapi.json) formats. These files can be used in tools that support the OpenAPI specification, such as the [OpenAPI Generator](https://openapi-generator.tech). In the API, whenever some data is referenced, for example, a group, or payment type, either id or internal name can be used. When an user is to be referenced, the special word 'self' (sans quotes) always refers to the currently authenticated user, and any identification method (login name, e-mail, mobile phone, account number or custom field) that can be used on keywords search (as configured in the products) can also be used to identify users. Some specific data types have other identification fields, like accounts can have a number and payments can have a transaction number. This all depends on the current configuration. ----------- Most of the operations that return data allow selecting which fields to include in the response. This is useful to avoid calculating data that finally won't be needed and also for reducing the transfer over the network. If nothing is set, all object fields are returned. Fields are handled in 3 modes. Given an example object `{"a": {"x": 1, "y": 2, "z": 3}, "b": 0}`, the modes are: - **Include**: the field is unprefixed or prefixed with `+`. All fields which are not explicitly included are excluded from the result. Examples: - `["a"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["+b"]` results in `{"b": 0}` - `["a.x"]` results in `{"a": {"x": 1}}`. This is a nested include. At root level, includes only `a` then, on `a`'s level, includes only `x`. - **Exclude**: the field is prefixed by `-` (or, for compatibility purposes, `!`). Only explicitly excluded fields are excluded from the result. Examples: - `["-a"]` results in `{"b": 0}` - `["-b"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["a.-x"]` results in `{"a": {"y": 2, "z": 3}}`. In this example, `a` is actually an include at the root level, hence, excludes `b`. - **Nested only**: when a field is prefixed by `*` and has a nested path, it only affects includes / excludes for the nested fields, without affecting the current level. Only nested fields are configured. Examples: - `["*a.x"]` results in `{"a": {"x": 1}, "b": 0}`. In this example, `a` is configured to include only `x`. `b` is also included because, there is no explicit includes at root level. - `["*a.-x"]` results in `{"a": {"y": 2, "z": 3}, "b": 0}`. In this example, `a` is configured to exclude only `x`. `b` is also included because there is no explicit includes at the root level. For backwards compatibility, this can also be expressed in a special syntax `-a.x`. Also, keep in mind that `-x.y.z` is equivalent to `*x.*y.-z`. You cannot have the same field included and excluded at the same time - a HTTP `422` status will be returned. Also, when mixing nested excludes with explicit includes or excludes, the nested exclude will be ignored. For example, using `["*a.x", "a.y"]` will ignore the `*a.x` definition, resulting in `{"a": {"y": 2}}`. ----------- For details of the deprecated elements (operations and model) please visit the [deprecation notes page](https://documentation.cyclos.org/4.16.3/api-deprecation.html) for this version.

Go to Download


<< Previous Next >>