Skip to content
API Reference
/
/
Common Response Format
Last updated

All MoreLogin API responses follow a standard JSON format.

Response Structure

{
  "code": 0,
  "msg": null,
  "data": {},
  "requestId": "unique-request-id"
}
FieldTypeDescription
codeintegerResult code. 0 = success, other values indicate errors
msgstring | nullError message. null when successful
dataobject | array | nullResponse payload. Structure varies by endpoint
requestIdstringUnique request identifier. Include this when contacting support

Success Response

{
  "code": 0,
  "msg": null,
  "data": {
    "id": 1234567890
  },
  "requestId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
}

Error Response

{
  "code": 99001,
  "msg": "Invalid parameters",
  "data": null,
  "requestId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
}

Paginated Responses

List endpoints return paginated data in this format:

{
  "code": 0,
  "msg": null,
  "data": {
    "total": 100,
    "current": 1,
    "pages": 10,
    "dataList": [
      { ... },
      { ... }
    ]
  },
  "requestId": "..."
}
FieldDescription
totalTotal number of records
currentCurrent page number
pagesTotal number of pages
dataListArray of records for the current page

HTTP Status Codes

StatusDescription
200Request processed successfully (check code field for business result)
401Unauthorized — invalid or expired access token
403Forbidden — insufficient permissions
429Too Many Requests — rate limit exceeded
500Internal Server Error — contact support

Tip: Always check the code field in the response body, not just the HTTP status code. A 200 HTTP status with code: 99001 means the request was received but failed validation.

Quickstart

Rate Limits