来自 Shopee 官方资料快照 ·
- 当前资料结构化阅读页
- 固定快照已留存，可追溯
- 官方原文可核对
资料正文
§1 Task Center Update: New Completion Rule for API Quality Tasks
Dear Developers,
To accommodate different API calling patterns, Shopee Open Platform Task Center is introducing a new completion condition for selected API quality tasks.
§2 What's New
What's New
Selected tasks will support a new Consecutive Calling Days completion condition: Only days with actual API calls that meet the target will be counted;
- No-call days may be skipped within the permitted limit. They will not be treated as a 0% success rate or interrupt task progress;
- If an actual calling day does not meet the target, the current task progress will be affected as well;
§3 Consecutive Calendar Days vs. Consecutive Calling Days
Consecutive Calendar Days vs. Consecutive Calling Days
| Comparison | Consecutive Days | Consecutive Calling Days |
|---|---|---|
| Days counted | Consecutive calendar days | Only days with actual API calls |
| No-call days | Treated as a 0% success rate and interrupt consecutive progress | Skipped within the permitted limit; not treated as 0% and do not interrupt progress |
| Completion requirement | Meet the target for X consecutive calendar days | Meet the target for the required number of calling days within the total assessment window |
§4 Consecutive Calling Days Configuration
Consecutive Calling Days Configuration
| Required Calling Days | Permitted Skippable No-call Days | Total Assessment Window |
|---|---|---|
| 7 consecutive calling days | Up to 7 days | 14 days |
| 14 consecutive calling days | Up to 10 days | 24 days |
| 30 consecutive calling days | Up to 15 days | 45 days |
The total assessment window is used to evaluate the consecutive calling-day requirement and does not represent the task completion deadline. Developers must still meet the task requirements within the completion period specified on the task details page. If the requirements are not met before the deadline, the task will be marked as failed.
§5 Key Task Update
Key Task Update
The completion condition for [Action Required] Improve API Call Success Rate for v2.logistics.ship_order will be changed from 7 Consecutive Calendar Days to 7 Consecutive Calling Days after this release.
If the task has not yet been completed, the system will evaluate and update its completion status according to the new rule.
§6 Important Notes
Important Notes
- Existing Single Day and X Consecutive Days completion conditions are not affected. Once a task is completed, its status will not be reversed due to subsequent metric fluctuations;
- Please refer to the actual rules and completion deadline displayed on the task details page in Open Platform Console.
Effective Date on Live:
Lived
§7 Task Center 更新: API 质量任务完成规则优化
亲爱的开发者:
为适配不同业务的 API 调用节奏, Shopee Open Platform Task Center 将优化部分 API 质量任务的完成规则。
§8 更新内容
更新内容
部分任务将新增“连续调用日”完成条件: 仅统计实际发生 API 调用且达到目标的日期;
- 无 API 调用日期可在规定范围内跳过,不视为成功率 0%,也不会中断进度;
- 若实际调用日未达到目标,当前任务进度仍将受到影响;
§9 “Consecutive Days”与“Consecutive Calling Days”对比
“Consecutive Days”与“Consecutive Calling Days”对比
| 对比项 | Consecutive Days | Consecutive Calling Days |
|---|---|---|
| 统计方式 | 按连续的自然日统计 | 仅统计实际发生 API 调用的日期 |
| 无调用日 | 按成功率 0% 处理,并中断连续进度 | 在允许范围内跳过,不计为 0%,也不中断连续进度 |
| 完成条件 | 连续 X 个自然日均达到目标 | 在总时间窗口内达到规定的连续调用天数,且实际调用日均满足目标 |
§10 Consecutive Calling Days配置说明
Consecutive Calling Days配置说明
| 连续调用日要求 | 允许跳过的无调用日 | 总时间窗口 |
|---|---|---|
| 连续调用 7 天 | 最多跳过 7 天 | 14 天 |
| 连续调用 14 天 | 最多跳过 10 天 | 24 天 |
| 连续调用 30 天 | 最多跳过 15 天 | 45 天 |
上述总时间窗口用于评估连续调用日的完成情况，并不代表任务完成期限。开发者仍需在任务详情页规定的完成期限内满足任务要求;超过任务完成期限仍未达标,任务将被判定为失败。
§11 重点任务说明
重点任务说明
[Action Required] Improve API Call Success Rate for v2.logistics.ship_order 的完成条件将在本次上线后,由“7 Consecutive Days”调整为“7 Consecutive Calling Days”。
如任务尚未完成,系统将按新规则评估并更新任务完成状态。
§12 注意事项
注意事项
- 现有“单日”及“连续 X 天”完成条件不受影响，已完成任务的状态不会因后续指标变化而撤销;
- 请以 Open Platform Console 中任务详情页展示的实际规则及完成期限为准。
上线时间:
Lived