stable本次发布有变化全部展示
来自 Shopee 官方资料快照 ·
- 当前资料结构化阅读页
- 固定快照已留存,可追溯
- 官方原文可核对
资料正文
§1 v2.voucher.get_voucher
Get Voucher Detail
§2 Overview
Overview
| Field | Value |
|---|---|
| Module | Voucher |
| API type | Shop |
| HTTP method | GET |
| Path | /api/v2/voucher/get_voucher |
| Production URL | https://partner.shopeemobile.com/api/v2/voucher/get_voucher |
| Sandbox URL | https://partner.test-stable.shopeemobile.com/api/v2/voucher/get_voucher |
| Rate limit | [0, 0, 0] |
| Permission | ERP System; Seller In House System; Marketing; Customized APP; Swam ERP |
§3 Request parameters
Request parameters
| Name | Type | Required | Sample | Description |
|---|---|---|---|---|
| voucher_id | int64 | Yes | 123 | The unique identifier of a voucher used to query the voucher details. |
§4 Response parameters
Response parameters
| Name | Type | Required | Sample | Description |
|---|---|---|---|---|
| error | string | Indicate error type if hit error. Empty if no error happened. | ||
| message | string | Indicate error details if hit error. Empty if no error happened. | ||
| request_id | string | 6737e37ec1b411ebb7fbacde48001122 | The identifier of the API request for error tracking. | |
| response | object | Detailed informations you are querying. | ||
| response.voucher_id | int64 | 123 | The unique identifier of the voucher whose details are returned. | |
| response.voucher_code | string | MKTSRWE | Voucher Code | |
| response.voucher_name | string | test | Voucher Name | |
| response.voucher_type | int32 | 1 | The type of the voucher. The available values are: 1: shop voucher, 2: product voucher. | |
| response.reward_type | int32 | 1 | The reward type of the voucher. The available values are: 1: fix_amount voucher, 2: discount_percentage voucher, 3: coin_cashback voucher. | |
| response.usage_quantity | int32 | 1 | The number of times for this particular voucher could be used. | |
| response.current_usage | int32 | 0 | Up till now, how many times has this particular voucher already been used. | |
| response.start_time | timestamp | 1622198847 | The timing from when the voucher is valid; so buyer is allowed to claim and to use. | |
| response.end_time | timestamp | 1622807247 | The timing until when the voucher is still valid. Any time after this end_time, buyer is not allowed to claim or to use. | |
| response.is_admin | boolean | false | If the voucher is created by Shopee or not. | |
| response.voucher_purpose | int32 | 0 | The use case for the voucher. The available values are: 0: normal; 1: welcome, 2: referral; 3: shop_follow; 4:shop_game, 5: free_gift, 6: membership,7: Ads | |
| response.display_channel_list | int32[] | [1,2] | The FE channel where the voucher will be displayed. The available values are: 1: display_all, 2: order page, 3: feed, 4: live streaming, [] (empty - which is hidden). | |
| response.min_basket_price | float | 10.1 | The minimum spend required for using this voucher. | |
| response.percentage | int32 | 22 | The discount percentage is set for this particular voucher. Only when it is a discount percentage voucher or coins cashback voucher, api will return a value. | |
| response.max_price | float | 11.1 | The max amount of discount/value a user can enjoy by using this particular voucher. Only when it is a discount percentage voucher or coins cashback voucher, api will return a value. | |
| response.discount_amount | float | 11.0 | The discount amount set for this particular voucher. Only when it is a fix amount voucher, api will return a value. | |
| response.cmt_voucher_status | int32 | 1 | The voucher status in CMT. The available values are: 1:review, 2: approved, 3:reject. Only when this voucher is attending CMT campaign and not being rejected, api will return a value. | |
| response.item_id_list | int64[] | [123422,122311] | The list of items which is applicable for the voucher. Only return a value when it is a product type of voucher. | |
| response.display_start_time | timestamp | 162078900 | The timing of when voucher is displayed on shop pages; so buyer is allowed to claim. | |
| response.target_voucher | int32 | The field is used to mark new user voucher/ repeat buyer voucher; 1: new user voucher; 2: repeat buyer voucher: with 1 orders; 3. repeat buyer voucher: with 2 orders | ||
| response.usecase | int32 | usecase indicates a specific business scenario that the voucher is created and used for, i.e., new buyer voucher, live voucher, follow shop voucher, etc.; shop voucher:1; product voucher:2; new buyer voucher:3; repeat buyer voucher:4; private voucher:5; live voucher:6; video voucher:7; campaign voucher:8; follow prize voucher:9; membership voucher:10; game prize voucher:11; sample voucher:12 |
§5 Common parameters
Common parameters
| Name | Type | Required | Sample | Description |
|---|---|---|---|---|
| partner_id | int | 1 | Partner ID is assigned upon registration is successful. Required for all requests. | |
| timestamp | timestamp | 1610000000 | This is to indicate the timestamp of the request. Required for all requests. Expires in 5 minutes. | |
| access_token | string | c09222e3fc40ffb25fc947f738b1abf1 | The token for API access, using to identify your permission to the api. Valid for multiple use and expires in 4 hours. | |
| shop_id | int | 600000 | Shopee's unique identifier for a shop. Required param for most APIs. | |
| sign | string | e318d3e932719916a9f9ebb57e2011961bd47abfa54a36e040d050d8931596e2 | Signature generated by partner_id, api path, timestamp, access_token, shop_id and partner_key via HMAC-SHA256 hashing algorithm. More details: https://open.shopee.com/documents?module=87&type=2&id=58&version=2 |
§6 Request samples
Request samples
§7 Java
Java
{
"voucher_id": 123
}
§8 Response sample
Response sample
§9 JSON
JSON
{
"response": {
"voucher_id": 123,
"voucher_code": "MKTSRWE",
"voucher_name": "test",
"voucher_type": 1,
"reward_type": 1,
"usage_quantity": 1,
"current_usage": 0,
"start_time": 1622198847,
"end_time": 1622807247,
"is_admin": false,
"voucher_purpose": 0,
"discount_amount": 12,
"cmt_voucher_status": 1,
"min_basket_price": 20,
"display_channel_list": []
"display_start_time": 162078900
},
"request_id": "6737e37ec1b411ebb7fbacde48001122",
"error": "",
"message": ""
}
§10 Error example
Error example
§11 JSON
JSON
{
"response": "",
"request_id": "fa8eada60fc88bf60f5ae9933f6174f8",
"error": "common.error_not_found",
"message": "The information you queried is not found."
}
§12 Errors
Errors
| Error | Description | Solution |
|---|---|---|
| error_network | Inner http call failed | |
| error_data | parse data failed | |
| error_data | data not exist | |
| error_param | parameter invalid | |
| error_param | The information you queried is not found. | |
| common.error_not_found | The information you queried is not found. | |
| error_param | Wrong parameters, detail: {msg}. | |
| error_server | Something wrong. Please try later. | |
| error_shop | shopid is invalid | |
| error_param | request not from gateway |
§13 Common errors
Common errors
| Error | Description | Solution |
|---|---|---|
| error_auth | partner_id is invalid | |
| error_auth | The App is deleted, and you'll be unable to make any API call. | |
| error_auth | App developer’s permissions for authorizations have been restricted. If you’re a seller, contact the developer for more information. If you’re the developer, refer to the Open Platform Console for details. | |
| error_param | There is no partner_id in query. | |
| error_param | Invalid partner_id. | |
| error_param | no timestamp | |
| error_param | Invalid timestamp | |
| error_param | There is no sign in query. | |
| error_sign | Wrong sign. | |
| invalid_partner_id | Invalid partner_id, please have a check. | |
| error_auth | No permission to current api. | |
| error_api_call_restricted | The App permission for api call have been restricted. If you’re a seller, contact the developer for more information. If you’re the developer, refer to the Open Platform Console for details. | |
| api_suspended | The API is offline. Please call v2 API instead. | |
| error_limit | The total API call number made by your APP has reached the daily API call limit, please try again after 00: 00 (UTC+08:00) | |
| error_rate_limit | Too many requests. You have reached the rate limit. Please try again later. | |
| source_ip_undeclared | Request Source IP ({ip}) is undeclared. Please declare all your IP addresses in the Shopee Open Platform Console > App list > IP Address Whitelist | |
| error_param | Permission denied. This API is currently offline or the request path is incorrect. | |
| error_param | Partner_id is invalid, should be an integer between 0 and 4294967295. | |
| error_param | no timestamp. | |
| error_param | Timestamp is invalid, should be an integer between 0 and 4294967295. | |
| error_param | Timestamp is expired. | |
| error_partner_key_expired | Your API partner key has expired, please reset the Live API Partner Key in Console to get a new valid partner key to call open api. | |
| error_api_permission | This app type has no permission to this API. | |
| error_param | There is no access_token in query. | |
| error_auth | Invalid access_token. | |
| error_auth | Invalid partner_id or shopid. | |
| shop_no_linked | Partner and shop has no linked. | |
| shop_banned | The shop account has been banned. Permissions for shop authorization and API calls have been suspended until the shop account is restored. | |
| invalid_acceess_token | Invalid access_token, please have a check. | |
| partner_shop_no_link | Invalid partner_id or shop_id, please have a check. | |
| error_ashop_api_permission | The shop is Affiliate shop has no permission to call this API. | |
| error_kyc_auth | No permission. Please inform the seller to complete the Seller Registration on Shopee Seller Center first, then this shop can call for this API. | |
| error_auth | System error, please try again later. | |
| error_param | There is no shop_id in query. | |
| error_param | shop_id is invalid, should be an integer between 0 and 4294967295. |
§14 Update log
Update log
| Date | Change |
|---|---|
| 2024-12-13 | Add "voucher_purpose": 7 |
| 2024-05-08 | add target_voucher and usecase |
| 2022-07-27 | Add Error Example information |
| 2022-07-01 | Optimize the Sample information of Request Parameter and Response Parameter |
| 2022-03-29 | update api name |
