Get Credit Config list

POST /merchant/credit/config_list

Get Credit Config list

cURL

curl --request POST \
  --url https://api.unibee.dev/merchant/credit/config_list \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "currency": "<string>",
  "types": [
    123
  ]
}
'

200

{
  "code": 123,
  "data": {
    "creditConfigs": [
      {
        "createTime": 123,
        "currency": "<string>",
        "description": "<string>",
        "discountCodeExclusive": 123,
        "exchangeRate": 123,
        "id": 123,
        "logo": "<string>",
        "logoUrl": "<string>",
        "merchantId": 123,
        "metaData": {},
        "name": "<string>",
        "payoutEnable": 123,
        "previewDefaultUsed": 123,
        "rechargeEnable": 123,
        "recurring": 123,
        "totalDecrementAmount": 123,
        "totalIncrementAmount": 123,
        "type": 123
      }
    ]
  },
  "merchantId": 123,
  "message": "<string>",
  "redirect": "<string>",
  "requestId": "<string>"
}

Endpoint Overview

POST https://api.unibee.dev/merchant/credit/config_list

Get Credit Config list

---

Authorization

All UniBee Merchant API requests require authentication via API key.

Header	Required	Description
Authorization	Yes	Bearer <your_api_key>
Content-Type	Yes	application/json (for request body)

---

Parameters

Parameters for this endpoint are listed below. The schema is also shown in the Try it panel.

Request body

Name	Type	Required	Description
currency	string	No	currency
types	array	No	type list of credit account, 1-main account, 2-promo credit account

---

Request examples

cURL

curl -X POST "https://api.unibee.dev/merchant/credit/config_list" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "currency": "",
  "types": []
}'

Sandbox

curl -X POST "https://api-sandbox.unibee.top/merchant/credit/config_list" \
  -H "Authorization: Bearer YOUR_SANDBOX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "currency": "",
  "types": []
}'

---

Response

Success responses return a JSON envelope with code, data, message, redirect, and requestId. code 0 indicates success.

Field	Type	Description
code	integer	Response code. 0 = success
data	object	Response payload
data.creditConfigs	array	CreditConfig List Object
message	string	Human-readable message
requestId	string	Request ID for support

---

Error handling

HTTP status	Meaning
400	Bad request — invalid or missing parameters. Check message in the body.
401	Unauthorized — missing or invalid API key.
404	Not found — invalid path or resource.
500	Server error — retry with backoff.

When code in the response body is non-zero, check message for details. Use requestId when contacting support.

Authorizations

Authorization · string · header · required

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

Body

application/json

currency · string<string>

currency

types · integer<int>[]

type list of credit account, 1-main account, 2-promo credit account

Response

200 - application/json

code · integer<int>

data · object

Show child attributes

merchantId · integer<int64>

message · string<string>

redirect · string<string>

requestId · string<string>