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

Nomba Transfers API

Endpoints for bank lookups, account verification, and initiating domestic fund transfers to bank accounts and between wallets.

Nomba Transfers API is one of 14 APIs that Nomba publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against 2 base URLs: https://api.nomba.com, https://sandbox.nomba.com.

4 operations 4 paths 5 schemas 1 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.nomba.com
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

Nomba Transfers API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — OAuth2 bearer token obtained from the Nomba Authentication API.

Paths & Operations 4

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

Transfers 4

Endpoints for bank lookups, account verification, and initiating domestic fund transfers to bank accounts and between wallets.

GET
/v1/transfers/banks
Fetch bank codes and names
fetchBankCodes 1 param → 200401
POST
/v1/transfers/bank/lookup
Perform bank account lookup
performBankAccountLookup 1 param body → 200400401
POST
/v1/transfers/bank
Transfer to a bank account
transferToBank 1 param body → 200400401
POST
/v1/transfers/wallet
Transfer between Nomba accounts
transferBetweenAccounts 1 param body → 200400401

Schemas 5

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

BankAccountLookupResponse
object
3 properties
TransferResponse
object
3 properties
ErrorResponse
object
3 properties
BankListResponse
object
3 properties
Bank
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nomba-transfers-api-openapi.yml Raw ↑

Other APIs Nomba publishes across the network.

Nomba Checkout SDK
Nomba Accounts API
Nomba Authentication API
Nomba Card Charge API
Nomba Checkout Orders API
Nomba Corridors API
Nomba Exchange Rates API
Nomba Order Management API
Nomba Payouts API
Nomba Saved Cards API
Nomba Tokenized Cards API
Nomba Transactions API
Where this information came from

This is an independent, third-party profile of Nomba Transfers 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.