Common errors
When making API requests, ensuring the correct structure and format is key to smooth communication with TikTok Shop's servers. This topic covers cross-domain errors related to the request query, header, and body format. These fundamental errors occur before business logic processing and must be resolved for a request to be processed successfully.
📌 Note: 0 in the response code indicates that the request was successfully processed.
General errors
| Code | Error message | Details and guidance |
|---|---|---|
| 36009002 | Too many requests. You've made too many requests in a short period of time. | Please wait and try again. Refer to Rate limits for details. |
| 36009007 | Request timeout. The request to the endpoint timed out. | Please try again, or consider splitting it into smaller requests. |
| 36009009 | Invalid path. The specified path does not match any available endpoint. | Refer to the API documentation for details. |
| 36009010 | Invalid method. The HTTP method used is not supported by this endpoint. | Refer to the API documentation for details. |
| 36009021 | Invalid file size. The uploaded file size exceeds the maximum limit. | Refer to the API documentation for details. |
| 36009022 | Invalid request format. The request body format must be application/json for structured data or multipart/form-data for binary files. | Refer to the API documentation for details. |
| 36009023 | Invalid request format. The value of the content-type header must be multipart/form-data. | Refer to the API documentation for details. |
Authorization errors
| Code | Error message | Details and guidance |
|---|---|---|
| 101000 | Invalid query or header. The category_asset_cipher query parameter or x-tts-access-token header is invalid. | For category_asset_cipher, ensure you retrieve the correct value from the Get Authorized Category Assets endpoint. |
For x-tts-access-token, possible causes include:
- The token has an invalid
user_typefor this endpoint. - The token is not associated with a shop, or the associated shop does not match the provided
shop_cipherquery parameter.
Refer to the authorization guide for details. | | 105005 | Access denied. The app is not authorized to access the endpoint because the access scopes granted for the app or the access token do not contain the required access scope for the endpoint. | Suggested checks:
- Check the granted scopes for the app in Partner Center > App & Service > Manage API. If the required scope is missing, apply or enable it in Partner Center.
- Check the granted scopes for the token in the
granted_scopesfield of the Get Access Token response. If the required scope is missing, request the user to reauthorize the required scope, and then generate a new token accordingly. | | 36009033 | Access denied. Your IP address is not in the IP allow list configured for this app. | Add your IP address in Partner Center > App & Service. |
Authentication errors
| Code | Error message | Details and guidance |
|---|---|---|
| 105002 | Expired credentials. The access_token or x-tts-access-token header has expired. | Refresh your token by using the Get Refresh Token endpoint. |
| 106001 | Invalid credentials. The sign query parameter is invalid. | Ensure you generate a valid signature by referring to the guide on signing your request. |
| 36009004 | Missing credentials. The request does not include a required signature in the query. | Generate a signature by referring to the guide on signing your request. |
| 36009004 | Invalid credentials. The access_token header is invalid. | Please pass in the access_token you obtained from the Get Access Tokenendpoint. |
| 36009004 | Invalid credentials. The x-tts-access-token header is invalid. | Please pass in the access_token you obtained from the Get Access Tokenendpoint. |
| 36009004 | Invalid credentials. Invalid app_key query parameter. | Possible reasons include an invalid key format, the app not being found, the app being disabled or deleted, or there was an error in retrieving the required authorization. Ensure you are retrieving the correct value from the App details page in Partner Center. |
| 36009004 | Invalid timestamp. The value of the timestamp query parameter must not be lesser than 0. | Timestamps must lie within the range of 5 minutes before to 30 seconds beyond the current time. |
| 36009004 | Invalid timestamp. The value of the timestamp query parameter must not be earlier than 5 minutes before the current time. | Timestamps must lie within the range of 5 minutes before to 30 seconds beyond the current time. |
| 36009004 | Invalid timestamp. The value of the timestamp query parameter must not exceed the current time by more than 30 seconds. | Timestamps must lie within the range of 5 minutes before to 30 seconds beyond the current time. |
Parameter errors
| Code | Error message | Details and guidance |
|---|---|---|
| 106013 | Missing identifier. The shop_cipher query parameter is required to identify the target shop. | Retrieve this value from the Get Authorized Shops endpoint. |
| 36009004 | Unexpected identifier. The shop_cipher query parameter is not required for this request. | Remove it and try again. Refer to the API documentation for details on the identifier required. |
| 36009004 | Unexpected identifier. The category_asset_cipher query parameter is not required for this request. | Remove it and try again. Refer to the API documentation for details on the identifier required. |
| 36009004 | Invalid identifier. The shop_id query parameter is invalid. | Retrieve the correct value from the Get Authorized Shops endpoint. |
| 36009004 | Invalid API version. The version query parameter is invalid. | Refer to the API documentation to find out the valid API versions. |
| 36004004 | Invalid auth code | The auth_code has already been used, is expired, or is invalid. |