Skip to main content
GET
/
merchant
/
credit
/
config_list
Get Credit Config list
curl --request GET \
  --url https://api.unibee.dev/merchant/credit/config_list \
  --header 'Authorization: Bearer <token>'
{
  "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

GET https://api.unibee.dev/merchant/credit/config_list Get Credit Config list

Authorization

All UniBee Merchant API requests require authentication via API key.
HeaderRequiredDescription
AuthorizationYesBearer <your_api_key>
Content-TypeYesapplication/json (for request body)

Parameters

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

Query parameters

NameTypeRequiredDescription
typesarrayNotype list of credit account, 1-main account, 2-promo credit account
currencystringNocurrency

Request examples

cURL

curl -X GET "https://api.unibee.dev/merchant/credit/config_list" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json"

Sandbox

curl -X GET "https://api-sandbox.unibee.top/merchant/credit/config_list" \
  -H "Authorization: Bearer YOUR_SANDBOX_API_KEY" \
  -H "Content-Type: application/json"

Response

Success responses return a JSON envelope with code, data, message, redirect, and requestId. code 0 indicates success.
FieldTypeDescription
codeintegerResponse code. 0 = success
dataobjectResponse payload
data.creditConfigsarrayCreditConfig List Object
messagestringHuman-readable message
requestIdstringRequest ID for support

Error handling

HTTP statusMeaning
400Bad request — invalid or missing parameters. Check message in the body.
401Unauthorized — missing or invalid API key.
404Not found — invalid path or resource.
500Server 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.

Query Parameters

types
integer<int>[]

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

currency
string<string>

currency

Response

200 - application/json
code
integer<int>
data
object
merchantId
integer<int64>
message
string<string>
redirect
string<string>
requestId
string<string>