HTTP 200 does not guarantee success
Code 0 is success and 20001 is partial success. A different business code can still mean failure.
TikTok API for Business · Free lookup tool
TikTok API Error Code Lookup
Enter a return code or error keyword, or paste a full JSON response to get the status, meaning, common causes, and next triage step.
74 business return codes
Processed in your browser
No sign-in or TikTok API call
Look up TikTok API return codes
Search the local records, or parse a full response while keeping message and request_id intact.
74 records
Local only
Exact codes, keywords, and error-message fragments are filtered as you type.
Narrow by category
Common examples
Before triage: HTTP status and system errors
HTTP 200: transport succeeded, but the business result still depends on code.
Codes beginning with 5: system service errors; use message and request_id for detail.
HTTP 404: often means a wrong method or path; also check for a missing trailing /.
Your input stays in this browser and is not uploaded to Tec-Pulse or TikTok.
Reads code, message, and request_id. Invalid input stays in place so you can correct it.
Shortcut: ⌘/Ctrl + Enter to parse
Before triage: HTTP status and system errors
HTTP 200: transport succeeded, but the business result still depends on code.
Codes beginning with 5: system service errors; use message and request_id for detail.
HTTP 404: often means a wrong method or path; also check for a missing trailing /.
Your input stays in this browser and is not uploaded to Tec-Pulse or TikTok.
Local return-code records
Lookup result
01 · Key checks
Read the business code before choosing the next step
TikTok API for Business can return a business failure inside HTTP 200. Keep code, message, and request_id together.
Keep message and request_id
They help identify the field, reproduce the request, and give support a traceable reference.
Unknown codes stay unknown
The tool does not invent a cause for a code outside the local catalog; it points you to official escalation.
02 · Useful for integration, campaign operations, and tickets
Useful for integration, campaign operations, and tickets
Use the lookup as a local reference layer, not as a replacement for the official API documentation.
Integration and regression checks
Paste a test response, confirm code, message, and request_id, then return to the endpoint docs.
Campaign operations
Filter rate limits, authorization, files, or advertiser errors to choose the next operational check.
Support-ticket preparation
Keep the full response and include request_id, request path, and API version when escalating.
03 · Workflow
Keep a reviewable path from response to action
The tool does not retry your endpoint. Carry the result into your debugging, monitoring, or support flow.
Keep the full response
Preserve the complete JSON instead of copying only one message line.
Confirm business status
Read code first, then compare HTTP status and API version.
Apply the handling note
Correct parameters, tokens, rate, assets, files, or request paths.
Keep evidence for escalation
Save message and request_id before contacting official support.
04 · FAQ
Practical questions before and after lookup
Success detection, HTTP status, unknown codes, and local processing.
How does the tool decide whether a call succeeded?
It reads the business return code first: 0 is success, 20001 is partial success, and other codes are not labeled as success.
Why can HTTP 200 still mean failure?
HTTP status describes transport, while the TikTok business return code describes business processing.
What happens when a code is unknown?
The tool preserves the original message and request_id, then points to official docs and support instead of inventing a cause.
Where is my input sent?
Nowhere. Search and JSON parsing run in this browser; the page does not call the TikTok API.
From API evidence to campaign decisions
Need to connect errors with performance signals?
Tec-Pulse helps TikTok Shop GMV Max merchants monitor and explain performance. Using this tool does not change its local-processing boundary.