Libraries tagged by consumerr
alb/oembed
103598 Downloads
oEmbed consumer library
congressus/sepa-direct-debit
227644 Downloads
Package to create SEPA Direct Debit XML (B2C, Business to Consumer only) files conform pain.008.001.02 or pain.008.001.03.
allejo/php-soda
22303 Downloads
A PHP library for working with both the consumer and producer Socrata API
sanju-inapp/api-consumer
1238 Downloads
API consumer
samsonasik/apigility-consumer
1879 Downloads
Laminas API Tools Client API Service Consumer
nixilla/twitter-api-consumer
13073 Downloads
Twitter API consumer in PHP, supports API 1.1 and works with OAuth 1.1 as well as OAuth 2.0
mrandmrssmith/idempotent-consumer-bundle
17129 Downloads
idempotent-consumer-bundle
gurento/kafka-consumer-filament
283 Downloads
Filament UI package for gurento/kafka-consumer.
6phere/horizon-wildcard-consumer
3004 Downloads
Extended Laravel Horizon providing listening dynamically added queues matched by wildcard.
matiux/ddd-starter-pack
5181 Downloads
Basic Domain Driven Design utils
mageme/module-eu-withdrawal-hyva-checkout
1384 Downloads
Hyva Checkout compatibility for mageme/module-eu-withdrawal. Re-implements the pre-contract Annex I block and the digital-content waiver step (Art. 16(m)) for Hyva Checkout's Magewire-based runtime. Companion to mageme/module-eu-withdrawal-hyva. NOT legal advice — see README disclaimer; merchant is responsible for compliance verification.
mageme/module-eu-withdrawal-hyva
3501 Downloads
Hyva theme compatibility for mageme/module-eu-withdrawal. Re-renders the customer-facing withdrawal form (4-step SPA + lookup) and order-view integrations using pure Alpine.js + Tailwind utilities — no KO, no jQuery, no Magewire dependency. Hyva checkout integration (precontract block + waiver step) is shipped separately. NOT legal advice — see README disclaimer.
fivelab/amqp-bundle
29194 Downloads
The bundle for integrate fivelab/amqp library with Symfony application
vortos/vortos-scheduler
1289 Downloads
Vortos Scheduler — in-app leader-elected distributed scheduler. Recurring + one-shot + interval triggers, static (compile-time) and dynamic (DB-stored) schedules, agnostic LeasePort (SQL/Redis/PG-advisory), idempotent fire-to-CommandBus, misfire + overlap policies, hash-chained audit, OTel, dead-man detection, RBAC + 4-eyes, fire-queue CQRS consumer, auto-prune retention.
vitexsoftware/rbczpremiumapi
461 Downloads
##### API Overview - Accounts list and balance - Transaction overview (also for saving accounts) - Payments import - Statement list and download - FX rates ##### Authentication Before making a call to Premium API, you need to register your app at our _Developer portal_. This is where you get the **ClientID** that your application must send in the request as `X-IBM-Client-Id`. This is the key that grants your app access to the API. However, this may not be enough. Your application needs to use mTLS to call most operations here. Thus, you not only need _https_ but also a client certificate issued by us. The exception is two operations for FX rates that are accessible also without a client certificate. Each bank client/user can issue several certificates. Each certificate can permit different sets of operations (http methods) on different bank accounts. All this must be configured in Internet Banking first by each bank client/user (bank clients need to look under _Settings_ and do not forget to download the certificate at the last step). The certificate is downloaded in **PKCS#12** format as **\*.p12** file and protected by a password chosen by the bank client/user. Yes, your app needs the password as well to get use of the **\*p12** file for establishing mTLS connection to the bank. Client certificates issued in Internet Banking for bank clients/users have limited validity (e.g. **5 years**). However, **each year** certificates are automatically blocked and bank client/user must unblock them in Internet Banking. It is possible to do it in advance and prolong the time before the certificate is blocked. Your app should be prepared for these scenarios and it should communicate such cases to your user in advance to provide seamless service and high user-experience of your app. ##### Rate Limiting The number of requests in each API operation is limited to 10 per client per sliding second and 5000 per client per sliding day. The exception is the 'Download Statement' operation with the limits lowered to 5 per client per sliding second and 1500 per client per sliding day. This is because it transports potentially sizeable binary files. The consumer must be able to handle HTTP status 429 in case of exceeding these limits. Response headers `X-RateLimit-Limit-Second` and `X-RateLimit-Limit-Day` show the actual limits configured for the specific operation. Response headers `X-RateLimit-Remaining-Second` and `X-RateLimit-Remaining-Day` are returned to help prevent the limits from being exceeded. ##### Notes Be aware, that in certain error situations, API can return specific error structures along with 5xx status code, which is not explicitely defined below. ##### Quick Start Client Feel free to download a simple Java client that gives you quick access to our API.