Libraries tagged by dingding chat
exewen/robot-chat
4 Downloads
A robot-chat component for Exewen.
jumoshen/ding-bot
1279 Downloads
Send message to dingding`s group chat
calchen/laravel-dingtalk-robot-notification
24199 Downloads
钉钉智能群助手 Laravel/Lumen 消息通知扩展包(Dingtalk robot message notifications for Laravel/Lumen)
wantp/laravel-dingtalk-notification-channel
47 Downloads
Ding talk Notification Channel for laravel.
dev-lucid/factory
44 Downloads
A loader for dividing up code into 5 categories: models, views, controllers, rulesets, and helpers. Models are provided by Paris (https://packagist.org/packages/j4mie/paris). Views, controllers, and helpers are basically empty classes waiting for you to add your own functionality. Rulesets provide a way to validate data both client side and server side.
aura/sql
1672534 Downloads
A PDO extension that provides lazy connections, array quoting, query profiling, value binding, and convenience methods for common fetch styles. Because it extends PDO, existing code that uses PDO can use this without any changes to the existing code.
prinsfrank/arithmetic-operations-floating-point
8351 Downloads
Floating point math implementation for the prinsfrank/arithmetic-operations interface that provides basic arithmetic operations (addition, subtraction, power, dividing, etc...)
macropage/sdk-ebay-rest-browse
2722 Downloads
The Browse API has the following resources: item_summary: Lets shoppers search for specific items by keyword, GTIN, category, charity, product, or item aspects and refine the results by using filters. (Experimental) search_by_image: Lets shoppers search for specific items by image. You can refine the results by using URI parameters and filters. item: Lets you retrieve the details of a specific item or all the items in an item group, which is an item with variations such as color and size. This resource also provides a bridge between the eBay legacy APIs, such as Trading and Finding, and the RESTful APIs, such as Browse, which use different formats for the item IDs. You can use the Browse API to retrieve the basic details of the item and the RESTful item ID using a legacy item ID. (Experimental) shopping_cart: Provides the ability for eBay members to see the contents of their eBay cart, and add, remove, and change the quantity of items in their eBay cart. *Note:* This resource is not available in the eBay API Explorer. The item_summary, search_by_image, and item resource calls require an Application access token. The shopping_cart resource calls require a User access token.
meysampg/yii2-intldatebehavior
7258 Downloads
Automatic Change Date System of an ActiveRecord After finding It
loeper/kvv
9 Downloads
This library provides simple access to the public transportation association KVV in Karlsruhe. It is based on unofficial data sources which are therefore subject to change without notice.
zae/bigmath
6 Downloads
Easily work with big numbers with late static binding and chaining.
prinsfrank/arithmetic-operations-bcmath
0 Downloads
BCMath implementation for the prinsfrank/arithmetic-operations interface that provides basic arithmetic operations (addition, subtraction, power, dividing, etc...)
numerogeek/ebay-browse-api
2 Downloads
The Browse API has the following resources: item_summary: Lets shoppers search for specific items by keyword, GTIN, category, charity, product, image (Experimental Method), or item aspects and refine the results by using filters, such as aspects, compatibility, and fields values, or UI parameters. item: Lets you retrieve the details of a specific item or all the items in an item group, which is an item with variations such as color and size and check if a product is compatible with the specified item, such as if a specific car is compatible with a specific part. Provides a bridge between the eBay legacy APIs, such as Finding, and the RESTful APIs, which use different formats for the item IDs. The item_summary, search_by_image, and item resource calls require an Application access token.
nogrod/ebay-buy-browse-php-sdk
2 Downloads
The Browse API has the following resources:item_summary:Allows shoppers to search for specific items by keyword, GTIN, category, charity, product, image (Experimental Method), or item aspects and refine the results by using filters, such as aspects, compatibility, and fields values, or UI parameters.item:Allows shoppers to retrieve the details of a specific item or all items in an item group, which is an item with variations such as color and size and check if a product is compatible with the specified item, such as if a specific car is compatible with a specific part.This resource also provides a bridge between the eBay legacy APIs, such as the Finding, and the RESTful APIs, which use different formats for the item IDs.The item_summary, search_by_image, and item resource calls require an Application access token.
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.