Structure description of successful return

{
    success: true,
    content: Return content，{}/[]
}

Structure description of failedreturn

{
    success: false,
    errorLevel:['info’, 'warn’, 'error’, 'fault’],
    errorCode:errorCode,
    errorMsg:error information description
}

Failed example of structure return：

{
    "Code":"MissingParameter",
    "HostId":"domain name",
    "Message":"",
    "_RequestId":"",
    "errorCode":100,
    "errorLevel":"error",
    "errorMsg":"",
    "success":false
}

accessToken Return structure description of verification failure

{
    "AccessToken":"",
    "IsAccess":false,
    "errorCode":1206,
    "errorLevel":"error",
    "errorMsg":"",
    "success":false
}

Field description of error code

Description of business error code：
Business domain－functional domain－priority-error type－specific code

1）Business domain
It is used to distinguish error codes from those of other systems. Generally, OPF refers to gateway errors, and the others are internal application errors.
2）Function domain
BXXX: business dimension; SXXX: system dimension; AXXX: security dimension
3）Priority
From high to low, internal 01-05, external 10-15
4）Error classification

errorCode错误码字段说明

应用服务返回结果不符合规范的修改建议与示例

对于调用 API 无需关注，此规定是规范 API 提供方。

• 服务返回结果没有包装类，建议单独定义 API，返回结果按格式规约进行包装。
• 服务返回结果已经包装，但是字段没有全部匹配，可以在网关控制台应用服务配置页面进行自行补充格式。举例说明
  如果应用服务返回的数据格式如下

{
"success":true,
      "data":{
      "success":true,
      "content":{},
      "errorLevel":"",
      "errorCode":"",
      "bizErrorCode":"",
      "errorMsg":""
      },
}

控制台上配置方法如下

如果应用服务返回的数据格式如下

{
    "isSuccess":true,
    "content":{},
    "code":"",
    "bizErrorCode":"",
    "message":""
}

控制台上配置方法如下

业务 API 错误码：