Skip to content

Commit a32da0f

Browse files
authored
Merge pull request #15 from thoughtspot/main
Portal update
2 parents eac0e96 + e491093 commit a32da0f

3 files changed

Lines changed: 979 additions & 252 deletions

File tree

api-playground/APIMATIC-BUILD.json

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,13 +16,16 @@
1616
"linkColor": "#2770EF",
1717
"colors": {
1818
"C000": "#FFFFFF",
19+
"C100": "#F9FAFE",
1920
"C200": "#FFFFFF",
2021
"C300": "#C0C6CF",
2122
"C400": "#777e8b",
22-
"C600": "#1d232f",
23+
"C500": "#B0B5C9",
24+
"C600": "#FFFFFF",
2325
"C700": "#606E8A",
2426
"C800": "#1d232f",
25-
"C900": "#1C2029"
27+
"C900": "#1C2029",
28+
"C1000": "#1D2236"
2629
}
2730
},
2831
"fontSource": [],

api-playground/content/introduction.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,10 +18,10 @@ On clicking the **Try it out** button, you can view the API response. If the req
1818
## Errors
1919
The portal uses the standard HTTP response codes to indicate the success or failure of a request. The 200 response code indicates a successful request, whereas 500 and 4xx response codes indicate an error.
2020

21-
If the API response indicates an error, you can view the error details by navigating to `extensions` > `upstreamResponse` > `data` > `debug` in the error response body. You can also capture the response code by navigating to `extensions` -> `upstreamResponse` -> `status` in the error response body.
21+
If the API response indicates an error, you can view the error details by navigating to `root` > `error` > `message` > `debug` in the error response body.
2222

2323
## Authentication
2424

2525
All API requests generated from Playground are authenticated using the Bearer token included with the `Authorization` header passed along with the request. This token is generated and set each time you open the REST API Playground and navigate to an endpoint. The token is generated for the logged-in user and is valid for 24 hours.
2626

27-
If you want to use a new token, you can generate a token using the `/tspublic/rest/v2/session/gettoken` endpoint. To update the token, click **Configure** in the code explorer and edit the `AccessToken` field in the pop-up that appears.
27+
If you want to use a new token, you can generate a token using the `/api/rest/2.0/auth/token/object` endpoint. To update the token, click **Configure** in the code explorer and edit the `AccessToken` field in the pop-up that appears.

0 commit comments

Comments
 (0)