How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Kora Payouts API

Disbursements to bank accounts and mobile money wallets.

Kora Payouts API is one of 7 APIs that Kora publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payouts. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 5 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.korapay.com/merchant/api/v1.

5 operations 5 paths 6 schemas 2 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.korapay.com/merchant/api/v1
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Kora Payouts API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (secretKeyAuth). It accepts HTTP bearer tokens (publicKeyAuth). By default, every request must be authenticated.

  • secretKeyAuth — Secret API key passed as Authorization: Bearer sk.... Required for server-side and financial operations (payouts, balances, virtual bank accounts, refunds, con…
  • publicKeyAuth — Public API key (pk...) used from client-side code to initiate charges. Cannot access financial data.

Paths & Operations 5

Across 5 paths, the API surfaces 5 operations — 2 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Payouts 5

Disbursements to bank accounts and mobile money wallets.

POST
/transactions/disburse
Request a single payout
createPayout body → 200401
POST
/transactions/disburse/bulk
Request a bulk payout
createBulkPayout body → 200401
POST
/transactions/disburse/remittance
Request a remittance payout
createRemittancePayout body → 200401
GET
/payouts
Fetch payout history
listPayouts 4 params → 200401
GET
/payouts/availability
Check payout availability
getPayoutAvailability → 200401

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are PayoutInput (6 properties), BulkPayoutInput (5 properties), ErrorResponse (3 properties), PayoutResponse (3 properties). Each schema is shown below with its type and property counts.

PayoutInput
object
6 properties 4 required
PayoutList
object
3 properties
BulkPayoutInput
object
5 properties 3 required
Customer
object
2 properties
PayoutResponse
object
3 properties
ErrorResponse
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

korapay-payouts-api-openapi.yml Raw ↑

Other APIs Kora publishes across the network.

Kora Balances API
Kora Charges API
Kora Currency Conversion API
Kora Misc API
Kora Refunds API
Kora Virtual Bank Accounts API
Where this information came from

This is an independent, third-party profile of Kora Payouts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.