Skip to main content
GET
/
merchant
/
email
/
history_list
Get Email History List
curl --request GET \
  --url https://api.unibee.dev/merchant/email/history_list \
  --header 'Authorization: Bearer <token>'
{
  "code": 123,
  "data": {
    "emailHistories": [
      {
        "attachFile": "<string>",
        "content": "<string>",
        "createTime": 123,
        "email": "<string>",
        "gatewayName": "<string>",
        "id": 123,
        "merchantId": 123,
        "response": "<string>",
        "status": 123,
        "title": "<string>"
      }
    ],
    "emailHistoryStatistics": {
      "totalFail": 123,
      "totalSend": 123,
      "totalSuccess": 123
    },
    "total": 123
  },
  "merchantId": 123,
  "message": "<string>",
  "redirect": "<string>",
  "requestId": "<string>"
}

Endpoint Overview

GET https://api.unibee.dev/merchant/email/history_list Get email send history 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
searchKeystringNoSearch Key, email or title
emailstringNoFilter Email
statusarrayNostatus, 0-pending, 1-success, 2-failure
sortFieldstringNoSort Field,gmt_create|gmt_modify,Default gmt_modify
sortTypestringNoSort Type,asc|desc,Default desc
pageintegerNoPage, Start 0
countintegerNoCount Of Per Page
createTimeStartintegerNoCreateTimeStart,UTC timestamp,seconds
createTimeEndintegerNoCreateTimeEnd,UTC timestamp,seconds

Request examples

cURL

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

Sandbox

curl -X GET "https://api-sandbox.unibee.top/merchant/email/history_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.emailHistoriesarrayEmail History Object List
data.emailHistoryStatisticsobject
data.totalintegerTotal
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

searchKey
string<string>

Search Key, email or title

email
string<string>

Filter Email

status
integer<int>[]

status, 0-pending, 1-success, 2-failure

sortField
string<string>

Sort Field,gmt_create|gmt_modify,Default gmt_modify

sortType
string<string>

Sort Type,asc|desc,Default desc

page
integer<int>

Page, Start 0

count
integer<int>

Count Of Per Page

createTimeStart
integer<int64>

CreateTimeStart,UTC timestamp,seconds

createTimeEnd
integer<int64>

CreateTimeEnd,UTC timestamp,seconds

Response

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