GET
/
send
/
accounts
curl --request GET \
  --url https://staging-api.chip-in.asia/api/send/accounts \
  --header 'Authorization: Bearer <token>' \
  --header 'checksum: <checksum>' \
  --header 'epoch: <epoch>'
{
  "meta": {
    "pagination": {
      "current_page": 1,
      "total_count": 1,
      "total_pages": 1
    }
  },
  "results": [
    {
      "account_verification_fee": 1,
      "account_verification_fee_type": "flat",
      "convertible_balance_from_statement": 1000,
      "created_at": "2023-07-20T08:35:25.389Z",
      "currency": "MYR",
      "current_balance": 100,
      "id": 1,
      "send_fee": 1,
      "send_fee_type": "flat",
      "settlement_convert_approvals_count": 1,
      "status": "active",
      "updated_at": "2023-07-20T08:35:25.389Z"
    }
  ]
}

Use this endpoint to know:

  • Your available settlement (collection) amount that can be converted to CHIP Send Limit;
  • Current balance;
  • Send Fee;
  • Account Verification Fee;
  • No. of approvals required to convert collection balance to CHIP Send Limit

Please note that convertible_balance_from_statement will return different data depending on when you hit this endpoint. This adds flexibility and time for you to plan out your CHIP Send Budget Allocation requests, without having to send extra information.

For example:

  • Trigger today at 11.59 PM MYT will return convertible balance from today’s collection.
  • Trigger tomorrow at 12.00 AM MYT will return convertible balance from today’s collection.
  • Trigger tomorrow at 11.59 AM MYT will return convertible balance from today’s collection.
  • Trigger tomorrow at 12.00 PM MYT will return convertible balance from tomorrow’s collection.

Authorizations

Authorization
string
headerrequired

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

epoch
integer
required

Unix epoch timestamp

checksum
string
required

Refer to checksum calculation

Response

200 - application/json
meta
object
results
object[]