How Jentic Works
From API assessment to production deployment in four simple steps.
PLATFORM
CAPABILITIES
TOOLS
GET STARTED
COMMUNITY
Explore APIs in this category. Connect any of them to your AI agent through Jentic.
Filters
BOOK A DEMO
Browse thousands of APIs, connect in minutes via MCP, OpenClaw, or Python. One SDK, one credential — every API your agent needs.
The 1foryou API on the Flash Group flashswitch platform issues, redeems, and reverses 1FORYOU vouchers used across South African informal-sector retail. The four endpoints cover the full voucher lifecycle: purchase a new voucher, redeem (in part or whole), refund a prior redemption, and reverse a redemption inside a 90-second window. Voucher partial redemption mints a residual voucher automatically, suitable for retail point-of-sale, prepaid utility top-ups, and reseller channels.
Jentic publishes the only available OpenAPI specification for 8B World Payment API, keeping it validated and agent-ready. The 8B World Payment API is a payment processing platform interface for managing the back-office accounts that underpin merchant settlement. It exposes admin account lifecycle, settlement account configuration, settlement instrument provisioning, and contact management, all gated by an OAuth-issued bearer token. Sixteen endpoints cover authorization, account creation and updates, status changes, and listing summaries used to operate a payment program at scale.
RESTful API for interacting with ABB robot controllers. Provides access to controller configuration, I/O systems, RAPID programs, file management, event logging, mastership control, panel operations, subscriptions, system information, and user management. The API exposes 126 endpoints secured with basic authentication.
Onboard and manage marketplace account holders, sub-accounts, and their associated bank accounts and shareholders on the Adyen for Platforms classic integration. The API handles the full account lifecycle from creation through KYC verification, document upload, and suspension or closure. Each account holder can contain multiple accounts with separate balances and payout configurations.
The Equity Bank Account API allows a Merchant to fetch full/minimal transaction details for a given operative account, do Account Enquiries and Get a List of Accounts Opened. The API exposes 4 endpoints.
Information required for Cash Account Transactions. The API exposes 1 endpoints.
Online Accounting API is to be used where the accounting entry is expected to be handed off on-line to the host AND host can provide synchronous response. Typically, this would be for intra-day customer debit and credit transactions. Online API is always for a single batch, containing a single group, which in turn will contain a single accounting entry. An accounting entry will typically have both. The API exposes 1 endpoints.
This API validates an order ref number, Creates Customer and initializes subscription. The API exposes 1 endpoints secured with bearer authentication.
The IDT Beyond /v1 API exposes mobile airtime top-up and prepaid product distribution operations across IDT's global mobile operator network. Agents can check account balance, validate destination mobile numbers, list available top-up products and promotions, submit top-up transactions, and retrieve charges and topup history as JSON or CSV reports. The interface is RESTful over HTTPS with JSON request and response payloads, scoped to airtime top-up workflows.
Jentic publishes the only available OpenAPI specification for Active Documentation for /v1, keeping it validated and agent-ready. The IDT Beyond /v1 API exposes mobile airtime top-up and prepaid product distribution operations across IDT's global mobile operator network. Agents can check account balance, validate destination mobile numbers, list available top-up products and promotions, submit top-up transactions, and retrieve charges and topup history as JSON or CSV reports. The interface is RESTful over HTTPS with JSON payloads, scoped to airtime top-up workflows.
Jentic publishes the only available OpenAPI specification for Adapty server-side API, keeping it validated and agent-ready. Adapty is a mobile subscription and in-app-purchase platform; the server-side API lets backend systems manage user profiles, grant or revoke paid access levels, validate Stripe transactions, and configure the Refund Saver feature. It is the sync surface for keeping a backend in agreement with Adapty's source-of-truth on entitlement state across iOS, Android, and web purchases. Authentication uses a secret API key passed in the Authorization header.
The Adyen Balance Control API moves funds between merchant accounts that belong to the same legal entity inside one Adyen company account. It exposes a single POST /balanceTransfer endpoint that initiates a transfer with a source merchant account, destination merchant account, amount, and idempotency key. The API is designed for treasury operations on Adyen's classic platform — rebalancing settlement merchant accounts before payouts, reallocating commission, or correcting misrouted funds — and is separate from the Balance Platform Configuration API used by Adyen for Platforms customers.
The Adyen BIN Lookup API resolves card BIN (Bank Identification Number) data into actionable information for routing and authentication decisions before a payment is created. Two endpoints cover the core needs: POST /get3dsAvailability returns the 3D Secure version supported by the issuing bank for a given BIN, and POST /getCostEstimate returns Adyen's interchange and scheme fee estimate for a card. Use the API at the front of a checkout flow to choose the right authentication path and to surface processing-cost estimates to internal pricing logic.
The Adyen Checkout API is Adyen's primary surface for initiating and authorising online payments — cards (including 3D Secure), mobile wallets, local payment methods, and recurring billing. The 26 endpoints in v70 cover the full payment lifecycle: list available payment methods for a session, create payments, post payment details for redirects and 3DS challenges, capture and cancel authorisations, refund, manage payment links, handle Apple Pay sessions, support recurring stored details, and process orders for partial-method splits and donations.
Initiate and authorise online payments through Adyen's unified Checkout API, covering cards with 3D Secure, mobile wallets such as Apple Pay and Google Pay, and local payment methods like iDEAL and Sofort. The API exposes payment sessions, payment links, recurring tokens, donations, and modification operations (capture, cancel, refund) on a single integration. Version 71 of the API is reached via /v71/payments and related endpoints, with separate test and live environments.
The Adyen Configuration API is the core REST surface for Adyen for Platforms. It manages account holders, balance accounts, payment instruments, payment instrument groups, transaction rules, sweeps, network tokens, and grant accounts across a balance platform. The 56 endpoints cover creation, read, update, and lifecycle operations for every structural object Adyen for Platforms exposes — from posting a new accountHolder to retrieving the platform configuration to managing card-level transaction rules.
Automate the dispute and chargeback response cycle on Adyen by accepting or defending disputes, supplying defense documents, and retrieving the defense reasons applicable to a given dispute. The API exposes five operations covering the response side of the dispute workflow, with all calls going to /ca/services/DisputeService/v30. Suitable for merchants that want to react to chargebacks programmatically rather than through the Customer Area UI.
Manage funds within an Adyen Classic Platforms (MarketPay) marketplace by transferring money between platform accounts, paying out balances to account holders, refunding earlier transfers, and retrieving balances and transaction lists. Designed for the classic for-platforms integration; new implementations should use the modern Balance Platform APIs instead. Operates on /cal/services/Fund/v6 in test and the equivalent live endpoint.
The Adyen Payment API is the classic-integration interface for authorising, capturing, modifying, and reversing card and alternative-payment-method transactions on Adyen's payment platform. The 13 endpoints cover the full authorise-capture-refund lifecycle, plus 3D Secure 1 and 3DS2 step-up flows, donation collection, and technical cancellations by merchant reference. New integrations should use the Checkout API; the Payment API remains the right choice for legacy classic integrations and server-to-server card processing where the integrator collects the PAN.
The Adyen Payout API is the classic-integration surface for storing payout details, submitting third-party payouts, and confirming or declining them with a separate review credential, plus running instant card payouts. The six endpoints implement the dual-credential flow Adyen requires for payouts: one credential stores details and submits a payout, a second credential confirms or declines it. Adyen has deprecated this API for new integrations and recommends the Transfers API for instant bank payouts and richer webhook signalling; the Payout API remains available for existing classic integrations.
The Adyen Recurring API is the classic-integration surface for managing stored payment tokens (recurring details), permits that grant third parties limited charging rights against those tokens, and ancillary tasks such as scheduling Account Updater runs and notifying shoppers. The six endpoints cover listing stored details for a shopperReference, disabling a token, creating and revoking permits, and asking the issuer to push a payment notification to the shopper. Adyen has deprecated this API for new integrations and recommends the Checkout API stored payment methods endpoints instead; the Recurring API remains live for existing classic integrations.
The Adyen Stored Value API manages gift cards, prepaid cards, and other stored-value payment instruments issued through Adyen. The six endpoints cover card issuance, balance inquiries, loading funds onto a card, merging two card balances, voiding a previous transaction, and changing card status (for example to lock a lost card). It is the integration surface for retailers and brands running their own gift card or e-wallet programmes on Adyen rails.
The Adyen Terminal API is the JSON message protocol for in-person payments and point-of-sale interactions on Adyen-supplied terminals. The 19 endpoints cover the full POS lifecycle: login and logout, payment, card acquisition, loyalty, stored value, reversal, reconciliation, totals reporting, balance inquiry, transaction status, abort, diagnosis, and direct device interactions such as display, input, print, and card-reader APDU. Both synchronous and asynchronous transport modes are supported, and the same protocol is used for cloud and local terminal integrations.
The Adyen Transfers API v3 is the Balance Platform interface for moving money between balance accounts, third-party bank accounts, and capital grants. The nine endpoints initiate transfers, approve or cancel pending transfers, return a settled transfer, list and inspect transactions, and request or look up Adyen Capital grants. It is the modern replacement for the deprecated classic Payout API and supports instant payouts, third-party bank transfers, and dual-control approval where required.
The Adyen Transfers API v4 is the current major version of the Balance Platform interface for moving money between balance accounts, third-party bank accounts, and capital grants. The 11 endpoints initiate transfers, list and look up transfers and transactions, approve or cancel pending transfers, return a settled transfer, and request or inspect Adyen Capital grants. v4 adds GET /transfers list and GET /transfers/{id} on top of v3, enabling self-service reconciliation without polling individual transactions.
Jentic publishes the only available OpenAPI specification for Affirm API, keeping it validated and agent-ready. Affirm is a buy-now-pay-later (BNPL) platform that lets merchants offer instalment financing at checkout. Its v1 API exposes 23 endpoints covering checkouts (store, direct, update, resend), card-based virtual card flows, transactions (authorize, capture, refund, void), settlement events, dispute lifecycle including evidence upload, and supporting file storage. Authentication uses HTTP basic auth with the public_api_key as the username and the private_api_key as the password.
Jentic publishes the only available OpenAPI specification for Afterpay API, keeping it validated and agent-ready. Afterpay (also branded Clearpay in the UK) is a buy-now-pay-later checkout service that splits a purchase into four interest-free instalments. The API covers the full BNPL flow: creating checkouts, authorising and capturing orders, processing refunds, exchanging configuration data with the merchant platform, handling disputes, and managing post-purchase grants and adjustments.
Jentic publishes the only available OpenAPI specification for Airtel Africa API, keeping it validated and agent-ready. Airtel Africa runs mobile money and telecom services across more than a dozen sub-Saharan markets. The two documented endpoints accept a payment from a mobile money customer and return the current status of a previously created payment. Authentication uses an API key passed in the X-API-Key header.
Jentic publishes the only available OpenAPI specification for Alma Payments API, keeping it validated and agent-ready. Alma is a European buy-now-pay-later (BNPL) provider, and the API covers eligibility checks, payment creation, capture of deferred payments, refunds, customer records, addresses, balance transactions, data exports, and webhook configuration. The endpoint surface is comprehensive enough to run the full BNPL flow from cart eligibility through to post-purchase order updates and shipment notifications.
Jentic publishes the only available OpenAPI specification for Alma Payments API, keeping it validated and agent-ready. Alma is a European buy-now-pay-later (BNPL) provider used by merchants to offer instalment and deferred payment plans at checkout. The API covers payment creation, eligibility checks, refunds, captures, customer and order management, balance transactions, data exports, and webhook configuration across 22 endpoints. It is most often integrated by e-commerce platforms and merchant of record systems that need BNPL alongside card payment flows.
Api encargada de la operatividad via comercio electronico. The API exposes 1 endpoints secured with apiKey authentication.