Nestcoin ledger-beneficiaries API is one of 23 APIs that Nestcoin publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include ledger-beneficiaries. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes
8 operations
across 4 paths,
and defines 10 schemas.
It is described by OpenAPI 3.0.3, at version 3.0.2.
Requests are made against a single base URL, https://external.dev.onboardpay.co.
8 operations4 paths10 schemas2 DELETE4 GET2 POST
Metadata
The identity and technical contract details declared by the specification.
Nestcoin ledger-beneficiaries API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as x-signature (authSignature).
An API key is passed in the header as x-auth-token (authToken).
authToken — Auth Token header for inter-service communication
Paths & Operations 8
Across 4 paths, the API surfaces 8 operations — 2 DELETE, 4 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.
ledger-beneficiaries 8
POST
/ledger/fiat-beneficiaries
Customer beneficiary
saveBeneficiarybody→ 201400401403default
GET
/ledger/fiat-beneficiaries
Fetch all bank account beneficiaries and bank transfer type
The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are CreateBeneficiaryRequest (7 properties), Beneficiary (7 properties), CryptoBeneficiary (5 properties), Paging (5 properties). Each schema is shown below with its type and property counts.
CryptoBeneficiaryList
ErrorMessageDto
object
Default error object for services. This gives consistent error object that all services may use.
3 properties2 required
CreateCryptoBeneficiaryRequest
object
create crypto beneficiary for customer
4 properties2 required
Beneficiary
object
Fiat beneficiary object
7 properties5 required
BeneficiaryList
Paging
object
Base object for paginated list
5 properties
CryptoBeneficiary
object
5 properties3 required
CreateBeneficiaryRequest
object
create beneficiary for customer
7 properties6 required
StatusDto
object
Status data, check additional message field.
4 properties1 required
AccountHolderType
string
Specification
The full machine-readable OpenAPI contract behind this narrative.
