Ibanera Customer API
Customer Portal
  • Overview
  • Terminology
    • Exchanges of Assets
    • Payees
    • Personal Customers
    • Business Customers
      • Managees
    • Enumerations, Codes and Definitions
      • Source of Funds Types
      • Transfer Purpose Codes Reference
  • Getting Started
    • Access the API
    • API Principal Account
    • Common Response Format
    • First API Call
    • Authentication & Authorization
      • Generating a Time-Based One-Time Password (TOTP) with a Shared Secret
  • API Endpoints
    • Accounts
    • Business Onboarding
    • Cards
    • Crypto Exchanges
    • Foreign Currency Exchange
    • Payees (Beneficiaries)
    • Transfers
    • Transaction Cancellation
    • Managees
    • Information Requests (RFIs)
    • Quick Buy
    • Simulated Testing
  • Callbacks
    • Managee Jumio Completed
    • Cryptocurrency Transfers
    • Exchange Status Updated
    • Fiat Deposit Received
    • Managee Card Approval Updated
    • Managee KYC Updated
    • Transaction Status Updated
    • Information Requests
  • QuickBuy
    • QuickBuy Callback
    • QuickBuy Front End Implementation
    • Validating the Webhook Signature
    • QuickBuy Pro
      • Visual Customization
      • Getting Started / Authentication
      • API Endpoints
        • Create Payment
        • Retrieve Payments
        • Delete Payment
      • Callbacks
        • Payment Captured
        • Cryptocurrency Transferred
Powered by GitBook
On this page
  • Response Body Parameters
  • Example Responses
  • Successful Response for an Object
  • Successful Response for an Array
  • Error Response
  1. Getting Started

Common Response Format

Most responses from the Customer API use a common format, with slight differences depending on whether the data returned is a JSON object or an array.

Response Body Parameters

Refer to the following table for parameters produced in response to the Customer API.

Body Parameter
Type
Description

id

Integer

Identity of entity modified, or 0 if unused.

details

Object or Array

Detailed response, or null if response is not success.

pageSize

Integer

Requested number of detail entries per page (fewer than pageSize items may be returned on the last page).

pageNumber

Integer

Requested page of data, if details is an array. Default is 1.

errors

Array

Details of errors that occurred.

errors.fieldName

String

Request item or step in handling the request that caused of the error.

errors.messageCode

String

Code identifying the error.

status

String

• “1” indicates success

• “0” indicates an error

Example Responses

Successful Response for an Object

{
    "id": 0,
    "details": {
        ... object content ...
    },
    "status": "1",
    "errors": []
}

Successful Response for an Array

{
    "id": 0,
    "details": [
        ... array content ...
    ],
    "pageSize": 10,
    "pageNumber": 1,
    "status": "1",
    "errors": []
}

Error Response

{
    "id": 0,
    "details": null,
    "status": "0",
    "errors": [
        {
            "fieldName": "...",
            "messageCode": "..."
        }
    ]
}
PreviousAPI Principal AccountNextFirst API Call

Last updated 1 year ago