站点工具

Hotfix release available: 2024-02-06a "Kaos". upgrade now! [55.1] (what's this?)
New release available: 2024-02-06 "Kaos". upgrade now! [55] (what's this?)
Hotfix release available: 2023-04-04a "Jack Jackrum". upgrade now! [54.1] (what's this?)
New release available: 2023-04-04 "Jack Jackrum". upgrade now! [54] (what's this?)
Hotfix release available: 2022-07-31b "Igor". upgrade now! [53.1] (what's this?)
Hotfix release available: 2022-07-31a "Igor". upgrade now! [53] (what's this?)
New release available: 2022-07-31 "Igor". upgrade now! [52.2] (what's this?)
New release candidate 2 available: rc2022-06-26 "Igor". upgrade now! [52.1] (what's this?)
New release candidate available: 2022-06-26 "Igor". upgrade now! [52] (what's this?)
Hotfix release available: 2020-07-29a "Hogfather". upgrade now! [51.4] (what's this?)
New release available: 2020-07-29 "Hogfather". upgrade now! [51.3] (what's this?)
New release candidate 3 available: 2020-06-09 "Hogfather". upgrade now! [51.2] (what's this?)
New release candidate 2 available: 2020-06-01 "Hogfather". upgrade now! [51.1] (what's this?)
New release candidate available: 2020-06-01 "Hogfather". upgrade now! [51] (what's this?)
Hotfix release available: 2018-04-22c "Greebo". upgrade now! [50.3] (what's this?)
Hotfix release available: 2018-04-22b "Greebo". upgrade now! [50.2] (what's this?)
Hotfix release available: 2018-04-22a "Greebo". upgrade now! [50.1] (what's this?)
New release available: 2018-04-22 "Greebo". upgrade now! [50] (what's this?)
Hotfix release available: 2017-02-19g "Frusterick Manners". upgrade now! [49.7] (what's this?)
Hotfix release available: 2017-02-19f "Frusterick Manners". upgrade now! [49.6] (what's this?)
Hotfix release available: 2017-02-19e "Frusterick Manners". upgrade now! [49.5] (what's this?)
Hotfix release available fixing CVE-2017-12979 and CVE-2017-12980: 2017-02-19d "Frusterick Manners". upgrade now! [49.4] (what's this?)
Hotfix release available fixing CVE-2017-12583: 2017-02-19c "Frusterick Manners". upgrade now! [49.3] (what's this?)
Hotfix release available fixing security token and media manager: 2017-02-19b "Frusterick Manners". upgrade now! [49.2] (what's this?)
Hotfix release available fixing install and media manager issues: 2017-02-19a "Frusterick Manners". upgrade now! [49.1] (what's this?)
New release available: 2017-02-19 "Frusterick Manners". upgrade now! [49] (what's this?)
Hotfix release available: 2016-06-26e "Elenor of Tsort". upgrade now! [48.5] (what's this?)
Hotfix release available fixing CVE-2017-12979 and CVE-2017-12980: 2016-06-26d "Elenor of Tsort". upgrade now! [48.4] (what's this?)
Hotfix release available fixing CVE-2017-12583: 2016-06-26c "Elenor of Tsort". upgrade now! [48.3] (what's this?)
Hotfix release available fixing security token: 2016-06-26b "Elenor of Tsort". upgrade now! [48.2] (what's this?)
Hotfix release available fixing authad issues: 2016-06-26a "Elenor of Tsort". upgrade now! [48.1] (what's this?)
New release available: 2016-06-26 "Elenor of Tsort". upgrade now! [48] (what's this?)
Hotfix release available: 2015-08-10a "Detritus". upgrade now! [47.1] (what's this?)
New release available: 2015-08-10 "Detritus". upgrade now! [47] (what's this?)
Hotfix release available: 2014-09-29d "Hrun". upgrade now! [46.4] (what's this?)
Hotfix release available: 2014-09-29c "Hrun". upgrade now! [46.3] (what's this?)
Hotfix release available to prevent XSS attack via SWF uploads: 2014-09-29b "Hrun". upgrade now! [46.2] (what's this?)
Hotfix release available: 2014-09-29a "Hrun". upgrade now! [46.1] (what's this?)
New release available: 2014-09-29 "Hrun". upgrade now! [46] (what's this?)
Hotfix release available: 2014-05-05e "Ponder Stibbons". upgrade now! [44.5] (what's this?)
Hotfix release available: 2014-05-05d "Ponder Stibbons". upgrade now! [44.4] (what's this?)
Hotfix release available to prevent XSS attack via SWF uploads: 2014-05-05c "Ponder Stibbons". upgrade now! [44.3] (what's this?)
Security Hotfix 2014-05-05b to prevent zero byte attacks on external auth systems is available. upgrade now! [44.2] (what's this?)
Security Hotfix 2014-05-05a for Issue 765 available. upgrade now! [44.1] (what's this?)

apush

差别

这里会显示出您选择的修订版和当前版本之间的差别。

到此差别页面的链接

Both sides previous revision 前一修订版
后一修订版
前一修订版
上一修订版 Both sides next revision
apush [2014/06/16 11:23]
106.2.171.114
apush [2014/07/23 11:01]
106.2.171.114
行 27: 行 27:
   * appkey 【热拍卖家版Android客户端的appkey为100005,iOS为100004;买家版HTML5为100001,iOS为100002,Android为100003】   * appkey 【热拍卖家版Android客户端的appkey为100005,iOS为100004;买家版HTML5为100001,iOS为100002,Android为100003】
  
-  * appoid ​     【设备的唯一ID的md5值,android手机取网卡mac地址的md5值作为唯一ID;iOS手机取OpenUDID作为唯一ID。这里的appoid不是客户端提交的原始appoid,而是原始appoid md5后的值+  * appoid ​     【设备的唯一ID的md5值,android手机取网卡mac地址的md5值作为唯一ID;iOS手机取OpenUDID的md5值作为唯一ID。】
  
   * message ​   【要推送的文本消息】   * message ​   【要推送的文本消息】
行 49: 行 49:
 ==== 2、针对目标群体用户的消息推送写入接口(服务器端PHP引用方式调用的接口) ==== ==== 2、针对目标群体用户的消息推送写入接口(服务器端PHP引用方式调用的接口) ====
  
-<?php + <?php 
-require_once("/​Data/​webapps/​m.repai.com/​m/​phpapi.php"​);​ //​PHP引用方式,需要引用的框架入口文件 + require_once("/​Data/​webapps/​m.repai.com/​m/​phpapi.php"​);​ //​PHP引用方式,需要引用的框架入口文件 
-$parameters_array["​appkey"​] = "​100005";​ + $parameters_array["​appkey"​] = "​100005";​ 
-$parameters_array["​appoid"​] = "​d19149dd97b17ce55e70abd2f9e64d3d";​ //​这里的appoid不是客户端提交的原始appoid,而是原始appoid md5后的值 + $parameters_array["​appoid"​] = "​d19149dd97b17ce55e70abd2f9e64d3d";​ //​这里的appoid不是客户端提交的原始appoid,而是原始appoid md5后的值 
-$parameters_array["​message"​] = "​这里是要推送的消息";​ + $parameters_array["​message"​] = "​这里是要推送的消息";​ 
-$parameters_array["​opensound"​] = "​1";​ //​打开声音 + $parameters_array["​opensound"​] = "​1";​ //​打开声音 
-$parameters_array["​openmode"​] = "​push";​ + $parameters_array["​openmode"​] = "​push";​ 
-$parameters_array["​openurl"​] = "​http://​www.baidu.com/";​ + $parameters_array["​openurl"​] = "​http://​www.baidu.com/";​ 
-$result = phpapi_mvc("​apush",​ "​club_put_phpapi",​ $parameters_array);​ + $result = phpapi_mvc("​apush",​ "​club_put_phpapi",​ $parameters_array);​ 
- +  
-if (empty($result["​status"​])) { + if (empty($result["​status"​])) { 
- var_dump($result);​ //​打印出返回内容 + var_dump($result);​ //​打印出返回内容 
-} else { + } else { 
- var_dump($result["​error"​]);​ //​打印出错误内容 + var_dump($result["​error"​]);​ //​打印出错误内容 
-+
-?>+ ?>
  
 === 输入参数说明: === === 输入参数说明: ===
行 87: 行 87:
  
   * 写入失败,返回布尔值 false   * 写入失败,返回布尔值 false
 +
 +----
  
 ==== 3、Android 客户端定时请求获取消息列表的接口 ==== ==== 3、Android 客户端定时请求获取消息列表的接口 ====
  
-''​https://​m.repai.com/​apush/​get_api/​appkey/​密钥编号/​appoid/​手机设备唯一编号/​timestamp/​1402307990/​token/​73191b75734ea67df90cbb824ff67811''​+''​http://​m.repai.com/​apush/​get_api/​appkey/​密钥编号/​appoid/​手机设备唯一编号/​timestamp/​1402307990/​token/​73191b75734ea67df90cbb824ff67811''​ 
 + 
 +为了节省流量,此接口使用 HTTP 协议,而非 HTTPS 协议。
  
 === 输入参数说明: === === 输入参数说明: ===
行 106: 行 110:
   * JSON格式输出,错误时,status值为false,reason值为错误原因文本信息,示例如下:   * JSON格式输出,错误时,status值为false,reason值为错误原因文本信息,示例如下:
  
-''​{+ {
  "​reason":​ "​TOKEN验证未通过,非法请求!",​  "​reason":​ "​TOKEN验证未通过,非法请求!",​
  "​status":​ false  "​status":​ false
-}''​+ }
  
   * JSON格式输出,无推送消息时,status值也为false,示例如下:   * JSON格式输出,无推送消息时,status值也为false,示例如下:
  
-''​{+ {
  "​reason":​ "​无消息列表。",​  "​reason":​ "​无消息列表。",​
  "​status":​ false  "​status":​ false
-}''​+ }
  
   * JSON格式输出,有消息时,status值为true,示例如下:   * JSON格式输出,有消息时,status值为true,示例如下:
  
-''​{+ {
  "​list":​ [  "​list":​ [
  {  {
行 142: 行 146:
  "​reason":​ "​获取到消息列表。",​  "​reason":​ "​获取到消息列表。",​
  "​status":​ true  "​status":​ true
-}''​+ } 
 + 
 +备注:如果有多条消息(最多5条),客户端循环显示。 
 + 
 +---- 
 + 
 +相关接口:[[uid_appoid|根据用户rp_uid查询手机设备唯一编号appoid接口]]
  
 [[start|返回首页]] [[start|返回首页]]
apush.txt · 最后更改: 2021/11/19 16:58 由 5.188.211.26