差别
这里会显示出您选择的修订版和当前版本之间的差别。
| 两侧同时换到之前的修订记录 前一修订版 | 后一修订版 两侧同时换到之后的修订记录 | ||
|
im:other:errorcode:restapi [2018/12/25 09:25] she |
im:other:errorcode:restapi [2018/12/25 09:31] jk 已恢复为旧版 (2018/12/25 07:53) |
||
|---|---|---|---|
| 行 42: | 行 42: | ||
| |400|illegal_argument|"from can't be empty" |from表示消息发送者，无此字段Server会默认设置为"from":"admin"，有from字段但值为空字符串("")时请求失败，返回400| | |400|illegal_argument|"from can't be empty" |from表示消息发送者，无此字段Server会默认设置为"from":"admin"，有from字段但值为空字符串("")时请求失败，返回400| | ||
| |400|illegal_argument|"target_type can only be 'users' or 'chatgroups' or 'chatrooms'" |target_type只能为'users' or 'chatgroups' or 'chatrooms'，为其他字符串时请求失败，返回400 | | |400|illegal_argument|"target_type can only be 'users' or 'chatgroups' or 'chatrooms'" |target_type只能为'users' or 'chatgroups' or 'chatrooms'，为其他字符串时请求失败，返回400 | | ||
| - | |400|illegal_argument|"username [hxtest1@easemob.com] is not legal"|注册使用的username不合法，username(环信ID)规则文档| | + | |400|illegal_argument|"username [hxtest1@easemob.com] is not legal"|注册使用的username不合法，username(环信ID)规则见[[http://docs.easemob.com/im/server/ready/user|文档]]| |
| |400|illegal_argument|"This chatmessage request is not supported"|可能是传入的时间格式不正确，正确的格式是：YYYYMMDDHH，如要获取2018年02月09日12点到13点的聊天记录，这样设置：2018020912| | |400|illegal_argument|"This chatmessage request is not supported"|可能是传入的时间格式不正确，正确的格式是：YYYYMMDDHH，如要获取2018年02月09日12点到13点的聊天记录，这样设置：2018020912| | ||
| |400|illegal_argument|"illegal arguments: appkey: easemob-demo#chatdemoui, time: 2018020918, maybe chat message history is expired or unstored"|对应时间的聊天记录还未生成或已过期，目前聊天记录免费保存3天。| | |400|illegal_argument|"illegal arguments: appkey: easemob-demo#chatdemoui, time: 2018020918, maybe chat message history is expired or unstored"|对应时间的聊天记录还未生成或已过期，目前聊天记录免费保存3天。| | ||
| 行 57: | 行 57: | ||
| |403|forbidden_op|"new owner and old owner are the same"|转让群组返回403，error_description说明被转让的用户已经是群主。| | |403|forbidden_op|"new owner and old owner are the same"|转让群组返回403，error_description说明被转让的用户已经是群主。| | ||
| |403|forbidden_op|"forbidden operation on group owner!"|不能将群主加入黑名单。| | |403|forbidden_op|"forbidden operation on group owner!"|不能将群主加入黑名单。| | ||
| - | |403| |"can not join this group, reason：user %s has joined too many groups/chatroom!"|用户加入群组或聊天室数超过了限制。| | + | |403||"can not join this group, reason：user %s has joined too many groups/chatroom!"|用户加入群组或聊天室数超过了限制。| |
| - | |403| |"this appKey has create too many groups/chatrooms!"|appkey下创建的群组或聊天室数量以达到限制。| | + | |403||"this appKey has create too many groups/chatrooms!"|appkey下创建的群组或聊天室数量以达到限制。| |
| |404|organization_application_not_found|"Could not find application for hx/hxdeo2 from URI: hx/hxdeo2/token"|hx/hxdeo2这个设置不正确或不存在，或baseurl集群设置错误（只针对vip集群的appkey），正确的是orgname/appname，即appkey的"#"换成"/"；| | |404|organization_application_not_found|"Could not find application for hx/hxdeo2 from URI: hx/hxdeo2/token"|hx/hxdeo2这个设置不正确或不存在，或baseurl集群设置错误（只针对vip集群的appkey），正确的是orgname/appname，即appkey的"#"换成"/"；| | ||
| |404|service_resource_not_found|“Service resource not found” |URL指定的资源不存在，如用户相关接口是用户不存在，群组相关接口是群组不存在，聊天室相关接口是聊天室不存在 | | |404|service_resource_not_found|“Service resource not found” |URL指定的资源不存在，如用户相关接口是用户不存在，群组相关接口是群组不存在，聊天室相关接口是聊天室不存在 | | ||
| 行 66: | 行 66: | ||
| |413|Request Entity Too Large|“Request Entity Too Large” |请求体过大，如上传文件时文件过大；或发送消息时消息体过大，请求体如果超过5kb会导致413错误，需要拆成几个更小的请求体重试，同时用户消息+扩展字段的长度在40k字节以内 | | |413|Request Entity Too Large|“Request Entity Too Large” |请求体过大，如上传文件时文件过大；或发送消息时消息体过大，请求体如果超过5kb会导致413错误，需要拆成几个更小的请求体重试，同时用户消息+扩展字段的长度在40k字节以内 | | ||
| |415|web_application|"Unsupported Media Type" |请求体的类型不支持，请检查header是否添加"Content-Type":"application/json"，body是否符合标准的JSON格式，再确认header中是否还有非接口需要的参数，可以舍去| | |415|web_application|"Unsupported Media Type" |请求体的类型不支持，请检查header是否添加"Content-Type":"application/json"，body是否符合标准的JSON格式，再确认header中是否还有非接口需要的参数，可以舍去| | ||
| - | |429|resource_limited|"You have exceeded the limit of the community edition. Please upgrade to the enterprise edition." |说明触发了社区版限制，如您已开通企业版，请联系环信商务处理| | + | |429|resource_limited|"You have exceeded the limit of the community edition. Please upgrade to the enterprise edition." |说明触发了社区版限制，[[http://www.easemob.com/pricing/im|社区版限制介绍]]，如您已开通企业版，请联系环信商务处理| |
| - | |429|reach_limit|"This request has reached api limit" |超过接口每秒调用次数，加大调用间隔或者联系商务调整限流大小| | + | |429|reach_limit|"This request has reached api limit" |超过接口每秒调用次数，加大调用间隔或者联系商务调整限流大小，见[[http://docs.easemob.com/im/other/errorcode/restastrict|接口限流标准]]| |
| |500|no_full_text_index|“Entity ‘user’ with property named ‘username’ is not full text indexed. You cannot use the ‘contains’ operand on this field” |username不支持全文索引，不可以对该字段进行contains操作| | |500|no_full_text_index|“Entity ‘user’ with property named ‘username’ is not full text indexed. You cannot use the ‘contains’ operand on this field” |username不支持全文索引，不可以对该字段进行contains操作| | ||
| |500|unsupported_service_operation|“Service operation not supported” |请求方式不被发送请求的URL支持| | |500|unsupported_service_operation|“Service operation not supported” |请求方式不被发送请求的URL支持| | ||