Geovane
07/22/2026, 8:02 PMAnswer Overflow
07/22/2026, 8:02 PMspotter-code
07/22/2026, 8:02 PM10003 and 10452 to their meanings.
What the official docs do expose are:
- HTTP response codes for APIs
- specific REST endpoint error responses
- Visual Embed SDK error enums such as EmbedErrorCodes for embed scenarios, which are named constants rather than numeric server error catalogs.
Docs:
- REST API HTTP codes: https://developers.thoughtspot.com/docs/rest-api-getstarted#_http_status_codes
- Embed SDK error enums: https://developers.thoughtspot.com/docs/Enumeration_EmbedErrorCodes
So if you're looking for a general lookup table for backend/internal numeric codes like 10003 and 10452, I don’t see an official public page for that in the current developer docs/reference.
Best path:
1. Check the exact API/feature context where the code appeared.
2. Look at the full response payload or server log message around that code.
3. Open a ThoughtSpot Support case with:
- cluster version
- exact endpoint / UI workflow
- full error payload
- timestamp / request ID if available
If you want, paste the full error response here and I can help narrow down what subsystem those codes likely came from.
Suggestions:
- The newer public developer docs are better starting points than the legacy reference URL:
- https://developers.thoughtspot.com/docs
- For REST APIs, the interactive v2 playground is also useful:
- https://try-everywhere.thoughtspot.cloud/v2/#/everywhere/api/rest/playgroundV2_0
- If these codes came from an embed error event, check whether they are actually SDK error enums instead of server numeric codes.
- If they came from a REST API response, the surrounding JSON often matters more than the numeric code alone.
Docs:
- ThoughtSpot Developer Docs: https://developers.thoughtspot.com/docsspotter-code
07/22/2026, 8:02 PMpallav
07/22/2026, 10:06 PM