Get Email Template List

GET /merchant/email/template_list

Get Email Template List

cURL

curl --request GET \
  --url https://api.unibee.dev/merchant/email/template_list \
  --header 'Authorization: Bearer <token>'

200

{
  "code": 123,
  "data": {
    "emailTemplateList": [
      {
        "VariableGroups": [
          {
            "groupName": "<string>",
            "variables": [
              {
                "variableName": "<string>"
              }
            ]
          }
        ],
        "createTime": 123,
        "gatewayTemplateId": "<string>",
        "id": 123,
        "languageData": [
          {
            "content": "<string>",
            "language": "<string>",
            "title": "<string>"
          }
        ],
        "localizationVersions": [
          {
            "activate": true,
            "localizations": [
              {
                "content": "<string>",
                "language": "<string>",
                "title": "<string>"
              }
            ],
            "versionId": "<string>",
            "versionName": "<string>"
          }
        ],
        "merchantId": 123,
        "status": "<string>",
        "templateAttachName": "<string>",
        "templateContent": "<string>",
        "templateDescription": "<string>",
        "templateName": "<string>",
        "templateTitle": "<string>",
        "updateTime": 123
      }
    ],
    "total": 123
  },
  "merchantId": 123,
  "message": "<string>",
  "redirect": "<string>",
  "requestId": "<string>"
}

Endpoint Overview

GET https://api.unibee.dev/merchant/email/template_list

Get Email Template 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

Path, query, and request body parameters are defined in the schema below. Use the interactive Try it panel to see the full request structure.

Path, query, and request body parameters are defined in the schema below. Use the interactive Try it panel to see the full request structure.

---

Request examples

cURL

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

Sandbox

curl -X GET "https://api-sandbox.unibee.top/merchant/email/template_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.

Field	Type	Description
code	integer	Response code. 0 = success
data	object	Response payload
data.emailTemplateList	array	Email Template Object List
data.total	integer	Total
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.

Response

200 - application/json

code · integer<int>

data · object

Show child attributes

merchantId · integer<int64>

message · string<string>

redirect · string<string>

requestId · string<string>