From 21b79de40194f191beb49bf457970c7128377843 Mon Sep 17 00:00:00 2001
From: Ayon Ghosh <ayon.ghosh@thoughtspot.com>
Date: Fri, 5 Feb 2021 10:58:12 +0530
Subject: [PATCH] Move asciidoc files to docs/src/asciidocs

---
 docs/src/asciidocs/about-rest-apis.adoc    |   5 +
 docs/src/asciidocs/authentication.adoc     | 122 +++++
 docs/src/asciidocs/calling-rest-api.adoc   | 110 +++++
 docs/src/asciidocs/customize-style.adoc    |  95 ++++
 docs/src/asciidocs/embed-a-viz.adoc        |  60 +++
 docs/src/asciidocs/embed-pinboard.adoc     |  57 +++
 docs/src/asciidocs/embed-search.adoc       |  68 +++
 docs/src/asciidocs/full-embed.adoc         | 142 ++++++
 docs/src/asciidocs/getting-started.adoc    |  56 +++
 docs/src/asciidocs/group-api.adoc          | 112 +++++
 docs/src/asciidocs/index.adoc              |  42 ++
 docs/src/asciidocs/metadata-api.adoc       | 225 +++++++++
 docs/src/asciidocs/rest-api-reference.adoc | 522 +++++++++++++++++++++
 docs/src/asciidocs/search-data-api.adoc    | 249 ++++++++++
 docs/src/asciidocs/visual-embed-sdk.adoc   | 135 ++++++
 15 files changed, 2000 insertions(+)
 create mode 100644 docs/src/asciidocs/about-rest-apis.adoc
 create mode 100644 docs/src/asciidocs/authentication.adoc
 create mode 100644 docs/src/asciidocs/calling-rest-api.adoc
 create mode 100644 docs/src/asciidocs/customize-style.adoc
 create mode 100644 docs/src/asciidocs/embed-a-viz.adoc
 create mode 100644 docs/src/asciidocs/embed-pinboard.adoc
 create mode 100644 docs/src/asciidocs/embed-search.adoc
 create mode 100644 docs/src/asciidocs/full-embed.adoc
 create mode 100644 docs/src/asciidocs/getting-started.adoc
 create mode 100644 docs/src/asciidocs/group-api.adoc
 create mode 100644 docs/src/asciidocs/index.adoc
 create mode 100644 docs/src/asciidocs/metadata-api.adoc
 create mode 100644 docs/src/asciidocs/rest-api-reference.adoc
 create mode 100644 docs/src/asciidocs/search-data-api.adoc
 create mode 100644 docs/src/asciidocs/visual-embed-sdk.adoc

diff --git a/docs/src/asciidocs/about-rest-apis.adoc b/docs/src/asciidocs/about-rest-apis.adoc
new file mode 100644
index 000000000..76ba324fd
--- /dev/null
+++ b/docs/src/asciidocs/about-rest-apis.adoc
@@ -0,0 +1,5 @@
+== REST APIs
+ThoughtSpot APIs are documented in the ThoughtSpot Documentation.  You can also find details about the APIs and test many of them using Swagger.  To access Swagger, first, login as a user with Administrator credentials.  Then navigate to https://<your-thoughtspot.com>/external/swagger.  You will get a list of all publicly available services.   
+
+
+You can click on a header to expand and get the list of services.  Clicking on a service name provides more details about the service.  
diff --git a/docs/src/asciidocs/authentication.adoc b/docs/src/asciidocs/authentication.adoc
new file mode 100644
index 000000000..1c2f69af6
--- /dev/null
+++ b/docs/src/asciidocs/authentication.adoc
@@ -0,0 +1,122 @@
+== Authentication
+:toc: true
+
+You can control which type of authentication you use between your client application and ThoughtSpot.
+
+=== No Authentication
+
+You can simply not set up authentication.
+This would require the user to be _already logged into ThoughtSpot_, before interacting with the client application.
+This approach is for testing the client.
+Do not use this in a production environment.
+
+=== SAML SSO
+
+To avoid showing the ThoughtSpot login page in the iFrame and provide a seamless login experience, you should configure SSO so that your users are automatically authenticated to ThoughtSpot, and the pages are loaded immediately.
+
+Before you can embed all or part of ThoughtSpot, you must authenticate to ThoughtSpot using SAML with the public REST API call.
+
+////
+For more information, see  https://cloud-docs.thoughtspot.com/admin/ts-cloud/authentication-integration.html[Managing authentication with SAML].
+Note that this does not assign the user to any groups, which must be managed manually or via the APIs.
+
+After authentication, a URL is provided to call the desired visualization, and populate it into an `<iframe>` element.
+
+You must link:{{ site.baseurl}}/admin/setup/configure-SAML-with-tscli.html[configure SAML] on your ThoughtSpot instance before using this method.
+
+////
+
+=== Trusted authentication service
+
+A ThoughtSpot installation can enable support for token-based authentication service.
+This allows an installation to use a central authentication service rather than using ThoughtSpot to authenticate.
+In this architecture, ThoughtSpot provides the service with a token that allows it to authenticate on behalf of users.
+
+A trusted authenticator application or service obtains a token from ThoughtSpot.
+This token is used to obtain trust from other third-party client applications that need access to ThoughtSpot.
+In the following scenario, the trust authenticator forwards requests for ThoughtSpot data from client applications to ThoughtSpot.
+
+==== Enable Trusted Authentication
+
+If you are using Trusted Authentication, enable this capability from the command line:
+[source,console]
+----
+$ tscli tokenauthentication enable
+----
+This command turns on trusted authentication and returns something like the following:
+[source,console]
+----
+Token generated. Copy the GUID in the box.
+
+ ########################################
+ # b0cb26a0-351e-40b4-9e42-00fa2265d50c #
+ ########################################
+
+ Override added successfully
+----
+
+The key inside the hashes is the ThoughtSpot secret key.  This key is needed to make calls to get a token for an individual user.  
+
+To disable trusted authentication, run the following command at the command line:
+
+[source,console]
+----
+
+ $ tscli tokenauthentication disable
+
+----
+
+This command disables token authentication and the secret token.
+
+For more information, see
+https://docs.thoughtspot.com/6.3/app-integrate/embedding-viz/trusted-authentication.html[Configure trusted authentication].
+////
+==== Trusted Authentication Workflow
+
+. The user will log into the web application using the customer provided authentication capabilities.  
+. The trusted authentication service  calls the ThoughtSpot service to log in, using a service account that has admin privileges. This step creates a session for the next call. 
+. After establishing a session, the token service will make calls to ThoughtSpot to get a token for the user using the +session/login/token +service.  
+. On success,  the token service returns a unique token for future calls on behalf of the user.
+The user is now authenticated, though the calls take a special format as described below.
+
+
+
+A user who is already logged into client-application interacts with a ThoughtSpot embed point, which initiates the following processes:
+
+. The client-side application requests a user token from the trusted authenticator.
+. The trusted authenticator requests a user token from ThoughtSpot.
+. ThoughtSpot verifies the authenticator and returns a user token.
+. The authenticator returns the user token to the client.
+. The client forwards the user token to ThoughtSpot.
+. ThoughtSpot validates the token and returns information commensurate with that authenticated user's authorization.
+
+== Cross-origin HTTP Requests (CORS)
+
+Collecting user credentials from one application (domain) and sending them to another application (such as ThoughtSpot) can present security vulnerabilities.
+Cross-origin or cross-domain verification prevents such security risks.
+
+When embedding, you must enable CORS between your client application domain and the ThoughtSpot domain.
+This protects your data, so that another actor cannot use the same URL to embed the visualization in its own Web pages.
+
+
+== Decide if you need to change the feedback email
+
+ThoughtSpot has an automated feature that collects feedback from users and sends it to ThoughtSpot Support.
+Depending on what and how you embed, user actions with your embedded application can trigger feedback.
+You can continue to forward feedback in this manner or direct the feedback to another email.
+To learn how to change the feedback email, see link:{{site.baseurl }}/admin/setup/work-with-ts-support.html#manage-the-feedback-contact[Manage the feedback contact].
+
+== Remove the ThoughtSpot branded footer
+
+The ThoughtSpot footer appears by default in the ThoughtSpot application.
+It also appears with an embed application that encompasses an individual Pinboard, or a full application.
+In embed applications that are have a single visualization, you can ask your ThoughtSpot support engineer to disable the footer.
+
+
+To embed with the navigation bar, call: +https://<thoughtspot-url>?embedApp=false#/+ +
+To embed without the navigation bar, call: +https://<thoughtspot-url>?embedApp=true#/+ 
+
+If you use +embedApp=true+ with this link, you will get the home page with no navigation bar, so you will need to provide navigation to use ThoughtSpot.  
+
+
+////
diff --git a/docs/src/asciidocs/calling-rest-api.adoc b/docs/src/asciidocs/calling-rest-api.adoc
new file mode 100644
index 000000000..f51de0793
--- /dev/null
+++ b/docs/src/asciidocs/calling-rest-api.adoc
@@ -0,0 +1,110 @@
+= Calling the Data REST API
+:last_updated: 11/18/2019
+
+
+Learn how to call the Data REST API.
+
+To call the Data REST API, you can specify a URL using the POST method, passing the ID numbers of the objects from which you want to obtain data.
+
+== Specify the pinboard or visualization example
+
+For a pinboard, you can append the ID of your pinboard as a parameter, like this example:
+
+----
+https://<thoughtspot_server>/callosum/v1/tspublic/v1/pinboarddata?id=7752fa9e-db22-415e-bf34-e082c4bc41c3
+----
+
+To retrieve data from a specific visualization within a pinboard, you would append the ID number of the visualization using the vizid parameter:
+
+----
+https://<thoughtspot_server>/callosum/v1/tspublic/v1/pinboarddata?id=7752fa9e-db22-415e-bf34-e082c4bc41c3&vizid=%5B1e99d70f-c1dc-4a52-9980-cfd4d14ba6d6%5D
+----
+
+*Remember:* You must add brackets around the vizid parameter.
+The URL encoding for open bracket is `%5B`, and the URL encoding for close bracket is `%5D`.
+
+== Object Format for Returned Data
+
+When you parse the returned JSON data you can see that there is one object for every viz on the pinboard.
+The objects are named according to the corresponding vizid.
+
+image::parsed_json_data.png[]
+
+If you make a call to a specific viz on a pinboard, it will return just one object.
+The JSON object format for the data that is returned from ThoughtSpot is:
+
+----
+{
+vizId1 : {
+         name: “Viz name”,
+         :[[2-d array of data values], [], [] …..[]],
+         columnNames:[col1, col2, …. ],
+         samplingRatio: n
+         },
+vizId2 : {
+         .
+         }
+}
+----
+
+Each object contains four components:
+
+. An array of column headers.
+. An array of data.
+. The name given to the specific viz.
+. And a sampling ratio.
+The sampling ratio tells you the percentage of total data returned.
+`1` would mean all data in the viz was returned in the API call.
+
+The `columnNames` array contains a list of all column headers.
+And the `data` array contains a list of other arrays.
+Each sub array represents a new row of data.
+
+image::columnnames_and_data_arrays.png[]
+
+The REST API supports filtering the data returned through parameters that you pass within the URL.
+These are called link:{{ site.baseurl }}/app-integrate/runtime-filters/about-runtime-filters.html#[Runtime Filters].
+
+== Example
+
+The following example shows a JavaScript function that calls the REST API, gets the results back, and retrieves a single value from the JSON results:
+
+----
+/**
+ * Generates headline by making a data API call.
+ *
+ * @param void
+ * @return void
+ */
+function generateHeadline(filters) {
+    var pinboardId = "0aa0839f-5d36-419d-b0db-10102131dc37";
+    var vizId = "67db30e8-06b0-4159-a748-680811d77ceb";
+    var myURL = "";
+
+    if (filters === void 0) {
+        myURL = "http://192.168.2.55:443/callosum/v1/tspublic/v1/" +
+                "pinboarddata?id=" + pinboardId + "&" +
+                "vizid=%5B" + vizId + "%5D";
+    } else {
+        var query = getQueryString(filters);
+        myURL = "http://192.168.2.55:443/callosum/v1/tspublic/v1/" +
+                "pinboarddata?id=" + pinboardId + "&" + +
+                "vizid=%5B" + vizId + "%5D&" + query;
+    }
+
+    var jsonData = null;
+    var xhr = new XMLHttpRequest();
+    xhr.open("POST", myURL, true);
+    xhr.withCredentials = true;
+    xhr.onreadystatechange = function() {
+        var headline = document.getElementById("embeded-headline");
+        if (xhr.readyState == 4 && xhr.status == 200) {
+            jsonData = JSON.parse(xhr.responseText);
+            headline.innerHTML = jsonData[vizId].data[0][0];
+        } else {
+            headline.innerHTML = "Error in getting data !!!";
+        }
+    };
+    xhr.send();
+}
+----
diff --git a/docs/src/asciidocs/customize-style.adoc b/docs/src/asciidocs/customize-style.adoc
new file mode 100644
index 000000000..94f608ddb
--- /dev/null
+++ b/docs/src/asciidocs/customize-style.adoc
@@ -0,0 +1,95 @@
+= Customize look and feel
+:toc: true
+
+
+You can brand the ThoughtSpot application for your company.
+
+You can customize the look and feel of the ThoughtSpot application for your company.
+Configuring these settings sets system-wide defaults for all your users.
+
+Style customization is enabled by default.
+You can configure your cluster to disable this functionality.
+
+////
+Contact https://community.thoughtspot.com/customers/s/contactsupport[ThoughtSpot Support] about disabling this feature.
+
+////
+
+== Customize styles
+
+To customize the styles, look and feel of the ThoughtSpot application components, you must be an authorized user with administrative privileges.
+
+To access style customization:
+
+. Go to the SpotDev portal.
+. Sign in with your ThoughtSpot user credentials.
+. Under *Configuration*, click *Style Customization*.
+
+== General guidelines for customization
+
+Your changes take effect either immediately, or after you refresh the browser.
+You can revert your changes by using the *Reset* button that appears when you move your cursor to the right of the setting.
+
+
+You can configure these style customizations:
+
+* Application Logo (Default) & Favicon
+* Font style for chart labels
+* Set the background for the embedded ThoughtSpot component
+* Set the default palette for all charts.
+  
+////
+
+  Sets a default application and favicon logo.
+This should be 140 pixels square.+++</dlentry>++++++<dlentry>+++Application Logo (Wide)::::  This logo should be 440 x 100 pixels.+++</dlentry>++++++<dlentry>+++Chart Visualization Fonts::::
+
+You can specify any Web Open Font Format (`WOFF`) file.+++</dlentry>++++++<dlentry>+++Table Visualization Fonts::::
+Set a font for table labels.
+You can specify any Web Open Font Format (`WOFF`) file.+++</dlentry>++++++<dlentry>+++Embedded Application Background::::
+Set the background for an embedded ThoughtSpot instance.
+This is only used if you are embedding ThoughtSpot in another application.+++</dlentry>++++++<dlentry>+++Chart Color Palettes::::
+Set the default palette for all charts.
+To set a value, however over a color value and enter a HEX value or select one from the chart.
+Individual users can still customize their own chart colors.
+They can use the *Reset colors* option on a chart to clear their changes.+++</dlentry>++++++<dlentry>+++Footer text::::  Define a footer to appear with the ThoughtSpot application.+++</dlentry>++++++<dlentry>+++Page title::::  Sets the title for the browser tab.+++</dlentry>+++
+
+////
+
+== How to specify fonts
+
+You can set your systems default fonts by specifying either or both of the *Chart Visualization Fonts* and *Table Visualization Fonts* values.
+To set this values, your font must be defined in a Web Open Font Format (`WOFF`) file.
+
+Changes to chart and table defaults apply only to charts and features created _after_ you configure a value.
+If you change table fonts, older tables retain their previous fonts.
+Some settings can be overridden on a per-object level.
+Users cannot configure their own defaults.
+
+. Make sure you have a WOFF file available for your font.
+. Select the label you want to change.
+. Click the *+* button.
++
+The system displays the *Custom Font* dialog.
+
+. Click the *Custom Font* field.
++
+The system displays the file finder.
+
+. Add the `WOFF` file you want.
++
+The file appears in the font dialog
+
+. Click *Save* to change the font.
+
+== How to specify the behavior or clickable links in data
+
+There is a system-wide setting which determines what happens when a user clicks on a link within the data.
+When your data includes URLs, they display as clickable links in ThoughtSpot tables.
+By default, clicking on a link opens the URL in a separate tab.
+But there is a system-wide setting that can be changed to open the links within the context of where they appear.
+
+Consider how the links open, by type:
+
+* Link in search result table in ThoughtSpot-Same browser tab as ThoughtSpot application
+* Link in table embedded in an <iframe> - Same <iframe> that contains the table
+* Link in full ThoughtSpot application embedded in an <iframe> - Same <iframe> that contains the application
diff --git a/docs/src/asciidocs/embed-a-viz.adoc b/docs/src/asciidocs/embed-a-viz.adoc
new file mode 100644
index 000000000..425e44a1e
--- /dev/null
+++ b/docs/src/asciidocs/embed-a-viz.adoc
@@ -0,0 +1,60 @@
+= Embed charts and tables  
+:toc: true
+
+This page explains, through an example, how to embed either a ThoughtSpot visualization (table or chart) in your Web page, portal, or application.
+////
+To build this sample, you must have access to a text editor and a ThoughtSpot instance with a visualization.
+Experience working with Javascript also helps.
+////
+=== Import the SDK Library
+
+[source,javascript]
+----
+<add codeblock>
+----
+
+=== Initialize the SDK
+
+[source,javascript]
+----
+<add codeblock>
+----
+=== Construct the embed content
+ 
+[source,JavaScript]
+----
+ var protocol = "THOUGHTSPOT_PROTOCOL";
+ var hostPort = "HOST_PORT";
+
+ var vizualizationId = "VIZUALIZATON_ID";
+----
+
+. Edit each variable in the section and replace it with the IDs you copied from the pinboard.
+
+For example, your URL may look similar to the following:
+
+----
+http://172.18.202.35:8088/#/embed/viz/061457a2-27bc-43a9-9754-0cd873691bf0/9985fccf-b28d-4262-b54b-29619a38348e+`
+
+----
+This is a link copied from an individual visualization, the result in the file is:
+
+
+[source,JavaScript]
+----
+ var protocol = "http";
+ var hostPort = "172.18.202.35:8088";
+
+ var pinboardId = "061457a2-27bc-43a9-9754-0cd873691bf0";
+ var vizualizationId = "9985fccf-b28d-4262-b54b-29619a38348e";
+----
+
+
+=== Configure Events
+
+<Add information on events>
+ 
+
+== Verify the embed connection
+<Add steps to test visualization embedding>
+
diff --git a/docs/src/asciidocs/embed-pinboard.adoc b/docs/src/asciidocs/embed-pinboard.adoc
new file mode 100644
index 000000000..98887d9e7
--- /dev/null
+++ b/docs/src/asciidocs/embed-pinboard.adoc
@@ -0,0 +1,57 @@
+= Embed Pinboards
+
+:toc: true
+
+This page explains, through an example, how to embed a ThoughtSpot Pinboard in your Web page, portal, or application.
+
+=== Import the SDK Library
+
+[source,javascript]
+----
+<add codeblock>
+----
+
+=== Initialize the SDK
+
+[source,javascript]
+----
+<add codeblock>
+----
+=== Construct the embed content
+ 
+[source,JavaScript]
+----
+ var protocol = "THOUGHTSPOT_PROTOCOL";
+ var hostPort = "HOST_PORT";
+ 
+ var pinboardId = "PINBOARD_ID";
+----
+
+. Edit each variable in the section and replace it with the IDs you copied from the pinboard.
+
+For example, your URL may look similar to the following:
+
+----
+http://172.18.202.35:8088/#/embed/viz/061457a2-27bc-43a9-9754-0cd873691bf0/9985fccf-b28d-4262-b54b-29619a38348e+`
+
+----
+This is a link copied from an individual visualization, the result in the file is:
+
+
+[source,JavaScript]
+----
+ var protocol = "http";
+ var hostPort = "172.18.202.35:8088";
+
+ var pinboardId = "061457a2-27bc-43a9-9754-0cd873691bf0";
+----
+
+
+=== Configure events
+
+<Add information on events>
+ 
+
+=== Verify the embed connection
+<Add steps to test visualization embedding>
+
diff --git a/docs/src/asciidocs/embed-search.adoc b/docs/src/asciidocs/embed-search.adoc
new file mode 100644
index 000000000..c1e5eaf99
--- /dev/null
+++ b/docs/src/asciidocs/embed-search.adoc
@@ -0,0 +1,68 @@
+== Embed Search
+:toc: true
+This procedure shows how to embed the ThoughtSpot search function using the Visual Embed SDK.  
+
+////
+The Embedded Search API enables searching directly from an external application or web page to pull data from ThoughtSpot.
+This feature was introduced in ThoughtSpot 5.0.
+When using it, you can access data stored in ThoughtSpot directly.
+You do not have to save a search result to a pinboard and then reference it using the visualization's URL.
+
+////
+
+This embedded search is useful when you want to allow an application to pull data directly from ThoughtSpot in an ad hoc fashion.
+
+=== Import the SDK Library
+
+Import the SearchEmbed SDK library to your application environment:
+
+[source,javascript]
+----
+<add codeblock>
+----
+
+=== Initialize the SDK
+
+[source,javascript]
+----
+<add codeblock>
+----
+=== Construct the embed content
+
+[source,javascript]
+----
+<add codeblock>
+----
+ 
+=== Configure events
+
+<Add information on events>
+
+////
+
+Data retrieved using the Embedded Search API is returned as JSON (JavaScript Object Notation).
+You must parse the JSON to get the data values you need, generally using JavaScript in the receiving application.
+
+Use this procedure to construct the call to the Embedded Search API:
+
+. link:{{ site.baseurl }}/app-integrate/JSAPI/enable-JS-API.html#[Enable the JavaScript API (JS API)] on the receiving page of the target application.
+. link:{{ site.baseurl }}/app-integrate/JSAPI/about-JS-API.html#[Authenticate to ThoughtSpot] on the receiving page of the target application.
+. link:{{ site.baseurl }}/app-integrate/embedding-viz/about-full-embed.html#[Embed the ThoughtSpot application] in your own web page or application.
+. To subscribe to results for all the searches the user does in the embedded ThoughtSpot application, use the API JavaScript function subscribeToData( ).
+This will allow your page to listen for data coming from ThoughtSpot.
++
+
+////
+
+=== Perform a Search
+
+////
+Now when a user searches, the <iframe> sends data to the subscription.
+The parent web page or application receives the data as JSON, and can do whatever you want with it.
+
+. You can set up your web page or application to display or otherwise act on the data it receives from the subscription.
+
+////
+To verify the integration, perform a search using the ThoughtSpot search bar embedded in your application.
+
+ 
\ No newline at end of file
diff --git a/docs/src/asciidocs/full-embed.adoc b/docs/src/asciidocs/full-embed.adoc
new file mode 100644
index 000000000..55165aa65
--- /dev/null
+++ b/docs/src/asciidocs/full-embed.adoc
@@ -0,0 +1,142 @@
+= Embed Full Application
+:toc: true
+
+Full embedding allows users to create ThoughtSpot content in an embedded environment. Fully embedding ThoughtSpot content gives your users the ability to perform many essential tasks:
+
+* create Answers and Pinboards
+* share objects with other users
+* upload data, and refresh uploaded data
+* relate uploaded data to existing worksheets
+
+This is useful for supplying the full search experience into an `iframe` with different navigation views and toggle options.
+////
+== Limitations of full embedding
+
+There are some limitations;
+users in a fully  embedded applications cannot perform the following tasks:
+
+* create worksheets or views
+* modify profiles
+* view the Help Center
+
+Before committing to fully embed the application, review the article link:{{ site.baseurl }}/app-integrate/embedding-viz/about-embedding-viz.html[Understand embedding].
+////
+=== Import the SDK Library
+
+Import the SearchEmbed SDK library to your application environment:
+
+[source,javascript]
+----
+<add codeblock>
+----
+
+=== Initialize the SDK
+
+[source,javascript]
+----
+<add codeblock>
+----
+=== Construct the embed content
+
+[source,javascript]
+----
+<add codeblock>
+----
+ 
+=== Configure events
+
+<Add information on events>
+== Example of full application embedding
+
+The following sample demonstrates how you can fully embed an application.
+
+----
+<!doctype html>
+<html lang="en" style="height: 100%; width: 100%">
+   <head>
+      <meta http-equiv="X-UA-Compatible" content="IE=edge"/>
+      <meta name="viewport" content="width=device-width">
+      <meta charset="utf-8">
+      <title>ThoughtSpot Embed App</title>
+      <script type="text/javascript" src="api/api.min.js"></script>
+      <script type="text/javascript">
+         function updateIframeUrl(id) {
+         var iframeUrl = "/?embedApp=true#/";
+         if (id === 'homepage') {
+         iframeUrl = "/?embedApp=true#/";
+         } else if (id === 'search') {
+         iframeUrl = "/?embedApp=true#/answer";
+         } else if (id === 'answerList') {
+         iframeUrl = "/?embedApp=true#/answers";
+         } else if (id === 'pinboardList') {
+         iframeUrl = "/?embedApp=true#/pinboards";
+         } else if (id === 'data') {
+         iframeUrl = "/?embedApp=true#/data/tables";
+         }
+         document.getElementById('ts-embed').setAttribute('src', iframeUrl);
+         }
+
+         function onCallback(event) {
+         console.log(event.data);
+         }
+         window.thoughtspot.subscribeToAlerts("http://localhost:8000", onCallback);
+
+      </script>
+   </head>
+   <body style="height: 100%; width: 100%">
+      <button onclick="updateIframeUrl('homepage')">Homepage</button>
+      <button onclick="updateIframeUrl('search')">Search</button>
+      <button onclick="updateIframeUrl('answerList')">Answer list</button>
+      <button onclick="updateIframeUrl('pinboardList')">Pinboard list</button>
+      <button onclick="updateIframeUrl('data')">Data</button>
+      <iframe id="ts-embed" allow=“fullscreen” src="/?embedApp=true#/" height="80%" width="80%"></iframe>
+   </body>
+</html>
+----
+
+The function `updateIframeUrl(id)` contains the logic to change the src URL of the `<iframe>` when your users click  navigation buttons.
+
+== Showing applications in a full screen
+
+To have an embedded ThoughtSpot application show in a full screen, the `<iframe>` element must have the `allow="fullscreen"` parameter or its analogues.
+
+=== Browser support for full screen embedding
+
+Note the following support across browsers:
++++<dlentry>+++Supported desktop browsers::::  Chrome, Edge, Firefox, and Opera+++</dlentry>++++++<dlentry>+++Supported mobile browsers::::  Android webview, Chrome for Android, Firefox for Android, Opera for Android, and Samsung Internet+++</dlentry>++++++<dlentry>+++NOT supported desktop browsers::::  Internet Explorer, Safari+++</dlentry>++++++<dlentry>+++NOT supported mobile browser::::  Safari on iOS+++</dlentry>+++
+
+=== Framework support for full screen embedding
+
+Additionally, consider the following framework factors:
++++<dlentry>+++allowfullscreen::::
+This attribute is the legacy precursor of `allow="fullscreen"`, and may still work with some browsers.
++ Set to `true` if the `<iframe>` can activate fullscreen mode by calling the `requestFullscreen()` method.
++ We strongly recommend that you update your embedding scripts to use the new approach inside the `<iframe>` tag.+++</dlentry>++++++<dlentry>+++Spring MVC::::  This framework supports the `allowfullscreen="true"` parameter inside the `iframe` tag.+++</dlentry>++++++<dlentry>+++React::::  This framework is case sensitive, and uses the attribute `allowFullScreen` inside the `iframe` tag.+++</dlentry>+++
+
+== Hide the ThoughtSpot navigation bar
+
+To hide the primary navigation, configure these:
+
+* Ensure the app is in an `<iframe/>` .
+* Set the `embedApp` flag to `true` to specify that the application is embedded.
+* Set the `primaryNavHidden` flag to `true` (the default) to specify that navigation visibility is off.
+
+If either flag is `false`, primary navigation appears.
+
+== Error messages and full embed
+
+In ThoughtSpot, you can disable error messages within the ThoughtSpot `iframe`.
+We provide APIs so you can access error messages and display them in your application's UI appropriately.
+
+This approach suppressing error messages inside the `<iframe>`, and uses the `window.postMessage` function to passes them through to the parent application, which acts as the listener.
+
+You can view these 'hidden' messages in the console logs.
+Contact ThoughtSpot Support to enable this feature.
+
+== Additional notes
+
+Here are some additional notes about the full embed feature:
+
+* Call `thoughtspot.<customerURL>.com/#/answer` and use that to access the search functionality.
+* Call `thoughtspot.<customerURL>.com/#/pinboards` and use that to access saved pinboards.
+* Use SAML for authentication against ThoughtSpot within the `<iframe>`.
diff --git a/docs/src/asciidocs/getting-started.adoc b/docs/src/asciidocs/getting-started.adoc
new file mode 100644
index 000000000..3d9124473
--- /dev/null
+++ b/docs/src/asciidocs/getting-started.adoc
@@ -0,0 +1,56 @@
+= Getting Started
+:toc: true
+== Download the Visual Embed SDK
+<add instructions on how to download SDK>
+
+== Install the Visual Embed SDK
+The preferred way to install the Visual Embed SDK for Node.js is to use npm, the Node.js package manager. To do so, type this at the command line:
+
+----
+npm install ts-embed-sdk
+----
+
+== Import the Visual SDK Library
+
+To use the Visual Embed SDK, include SDK Javascript library in your host page using a <script> HTML tag:
+
+----
+<script src=".....js></script>`
+----
+
+
+== Configuring Cross-Origin HTTP Requests
+
+When embedding ThoughtSpot into web pages, you must enable Cross-Origin HTTP Requests (CORS) between the client application domain and the ThoughtSpot domain. This protects your data, so that another application cannot use the same URL to embed the visualization in its Web pages.
+
+*<Question to dev team - Should CORS, same-site access, and content security settings be enabled via CLI or the dev portal > cluster settings page?)>*
+
+=== Enable CORS from the command line
+
+From the ThoughtSpot command line, run the following command with the appropriate values: 
+
+[source,console]
+----
+ $ echo "https?://(mythoughtspot1.mycompany.com|.*:443|.*:8080|.*:80)" | tscli --adv config set --key "/config/nginx/corshosts"
+----
+
+
+=== Enable CORS from the Developer Portal
+
+*<Add instructions>*
+
+== Enable Same-Site Access
+
+If you want to enable same-site access, run the following command:
+
+[source,console]
+----
+$ tscli --adv service add-gflag nginx.nanny nginx_cookie_flag 'Secure SameSite=None'
+----
+
+
+=== Enable Content Security
+
+<TBD>
+
+ 
\ No newline at end of file
diff --git a/docs/src/asciidocs/group-api.adoc b/docs/src/asciidocs/group-api.adoc
new file mode 100644
index 000000000..779f236a1
--- /dev/null
+++ b/docs/src/asciidocs/group-api.adoc
@@ -0,0 +1,112 @@
+= Group API
+:last_updated: 11/18/2019
+
+
+The Group APIs enable you to set or remove a privilege to or from a group or multiple groups.
+
+== Add a privilege
+
+Use this API to add a `DATADOWNLOADING` or `USERDATAUPLOADING` privilege to the system default `ALL_GROUP` group.
+All users in the system are always a part of the `ALL_GROUP` group.
+By default, this group does not have either permission.
+
+All the data sources which the `ALL_GROUP` group has permissions to are downloadable when `DATADOWNLOADING` is applied.
+
+=== Resource URL
+
+`post` /tspublic/v1/group/addprivilege
+
+=== Request Parameters+++<table>++++++<colgroup>++++++<col style="width:20%">++++++</col>+++
+   +++<col style="width:15%">++++++</col>+++
+   +++<col style="width:65%">++++++</col>++++++</colgroup>+++
+   +++<thead>++++++<tr>++++++<th>+++Form Parameter+++</th>+++
+         +++<th>+++Data Type+++</th>+++
+         +++<th>+++Description+++</th>++++++</tr>++++++</thead>+++
+   +++<tbody>++++++<tr>++++++<td>++++++<code>+++privilege+++</code>++++++</td>+++
+         +++<td>+++string+++</td>+++
+         +++<td>+++Specifies a privilege type to add. Valid values are +++<code>+++DATADOWNLOADING+++</code>+++ or +++<code>+++USERDATAUPLOADING+++</code>+++ privilege.+++</td>++++++</tr>+++
+      +++<tr>++++++<td>++++++<code>+++groupNames+++</code>++++++</td>+++
+         +++<td>+++string+++</td>+++
+         +++<td>+++Specifies a group name to add the privilege to. Valid value is +++<code>+++ALL_GROUP+++</code>+++ group.+++</td>++++++</tr>++++++</tbody>++++++</table>+++
+
+=== Request Example
+
+.cURL
+----
+curl -X POST --header 'Content-Type: application/x-www-form-urlencoded' --header 'Accept: application/json' --header 'X-Requested-By: ThoughtSpot' -d 'privilege=DATADOWNLOADING&groupNames=ALL_GROUP' 'https://<instance>/callosum/v1/tspublic/v1/group/addprivilege'
+----
+
+.Request URL
+----
+https://<instance>/callosum/v1/tspublic/v1/group/addprivilege
+----
+
+=== Response Example
+
+----
+Not applicable
+204 - Success
+----
+
+== Remove a privilege
+
+Use this API to delete a `DATADOWNLOADING` or `USERDATAUPLOADING` privilege from the system default ``ALL_GROUP``group.
+
+=== Resource URL
+
+`post` /tspublic/v1/group/removeprivilege
+
+=== Request Parameters+++<table>++++++<colgroup>++++++<col style="width:20%">++++++</col>+++
+   +++<col style="width:15%">++++++</col>+++
+   +++<col style="width:65%">++++++</col>++++++</colgroup>+++
+   +++<thead>++++++<tr>++++++<th>+++Form Parameter+++</th>+++
+         +++<th>+++Data Type+++</th>+++
+         +++<th>+++Description+++</th>++++++</tr>++++++</thead>+++
+   +++<tbody>++++++<tr>++++++<td>++++++<code>+++privilege+++</code>++++++</td>+++
+      +++<td>+++string+++</td>+++
+      +++<td>+++Specifies a privilege type to delete. Valid values are +++<code>+++DATADOWNLOADING+++</code>+++ or +++<code>+++USERDATAUPLOADING+++</code>+++ privilege.+++</td>++++++</tr>+++
+   +++<tr>++++++<td>++++++<code>+++groupNames+++</code>++++++</td>+++
+      +++<td>+++string+++</td>+++
+      +++<td>+++Specifies a group name to delete the privilege from. Valid value is +++<code>+++ALL_GROUP+++</code>+++ group.+++</td>++++++</tr>++++++</tbody>++++++</table>+++
+
+=== Request Example
+
+.cURL
+----
+curl -X POST --header 'Content-Type: application/x-www-form-urlencoded' --header 'Accept: application/json' --header 'X-Requested-By: ThoughtSpot' -d 'privilege=USERDATAUPLOADING&groupNames=ALL_GROUP' 'https://<instance>/callosum/v1/tspublic/v1/group/removeprivilege'
+----
+
+.Request URL
+----
+https://<instance>/callosum/v1/tspublic/v1/group/removeprivilege
+----
+
+=== Response Example
+
+----
+Not applicable
+204 - Success
+----
+
+////
+## Error Codes
+
+<table>
+   <colgroup>
+      <col style="width:20%" />
+      <col style="width:60%" />
+      <col style="width:20%" />
+   </colgroup>
+   <thead class="thead" style="text-align:left;">
+      <tr>
+         <th>Error Code</th>
+         <th>Description</th>
+         <th>HTTP Code</th>
+      </tr>
+   </thead>
+   <tbody>
+    <tr> <td><code>10003</code></td>  <td>Authentication token of type could not be authenticated by any configured realms.  Use valid realm that can authenticate these tokens.</td> <td><code>401</code></td></tr>
+
+  </tbody>
+</table>
+////
diff --git a/docs/src/asciidocs/index.adoc b/docs/src/asciidocs/index.adoc
new file mode 100644
index 000000000..f9ffc4e3e
--- /dev/null
+++ b/docs/src/asciidocs/index.adoc
@@ -0,0 +1,42 @@
+= ThoughtSpot Embedded Analytics
+:toc: true
+ß
+The ThoughtSpot embedded analytics capability empowers you to embed ThoughtSpot functionality and infuse search-driven data and insights into your applications, products, websites, or portals. 
+ThoughtSpot provides a suite of APIs, SDK, and developer tools to  embed search analytics, pinboards, visualizations, and even the entire ThoughtSpot application within  the context of your  application, and thus provide a consistent and seamless experience to your users.
+
+== Types of Embedding
+The type of embedding your business requires can help you determine what type of embedding to use.
+For example, you may simply need a single chart displayed as a  wallboard, or you may want your customers to access reports on their own data.
+The first example could require modifying a single HTML page, while the later example may require working with a development team and several different workflows in a browser application.
+
+Based on your integration requirements, you can use one of the following embedding approaches.
+
+* Full-application embedding - You can embed the entire ThoughtSpot application is embedded into a host application. Application users can navigate to the ThoughtSpot UI through a tab or a link. 
+* Page-level embedding - You can embed a ThoughtSpot page and hide  the navigation bar, help, and profile links. The client applications can allow page-to-page navigation.
+* Object-level embedding - You can embed a specific component like search, pinboard, or charts.
+
+
+== Embedding Methods
+
+You can use one of the following methods to embed ThoughtSpot functionality into your application:
+
+* *Using iFrames via ThoughtSpot UI*- In this method, you can copy the embed link for a pinboard or visualization from the ThoughtSpot UI and add it your webpage or an HTML file. For more information, see Embedding a Pinboard or Visualization.
+* *Using the Visual Embed SDK* - In this method, you can install the Visual Embed SDK, import the Javascript library, and programmatically integrate ThoughtSpot components or application. <Add a link to visual embed sdk topic>
+* *Using REST APIs* - In this method, you can make calls to ThoughtSpot application using REST APIs to programmatically fetch data and customize data. <Add a link to REST API content>
+
+== Embed Content Services
+
+The ThoughtSpot embedded content services can be grouped into four categories:
+
+* Search
+* Visualizations (Charts and Tables)
+* Pinboards
+* Full application
+
+== Customization and Rebranding
+
+If you are an existing ThoughtSpot application user, you can customize the styles, look and feel of the ThoughtSpot components embedded in an application. You can also configure custom actions for ThoughtSpot visualization widgets and pinboards.  
+For more information, see the following pages:
+
+* Customize Styles
+* Configure Custom Action
diff --git a/docs/src/asciidocs/metadata-api.adoc b/docs/src/asciidocs/metadata-api.adoc
new file mode 100644
index 000000000..37497adf4
--- /dev/null
+++ b/docs/src/asciidocs/metadata-api.adoc
@@ -0,0 +1,225 @@
+= Metadata API
+:last_updated: 11/18/2019
+
+
+The Metadata APIs allow you to fetch metadata for ThoughtSpot objects.
+
+The Metadata APIs enable you to fetch metadata details for various objects in the ThoughtSpot system.
+For example, you may want to see the visualization headers of a particular answer or a pinboard.
+
+== Get visualization headers
+
+Use this API to list the visualization headers from the ThoughtSpot system.
+The expected output includes a list of objects, each with information about the visualizations of the given pinboard or an answer.
+
+=== Resource URL
+
+`get` /tspublic/v1/metadata/listvizheaders
+
+=== Request Parameters+++<table>++++++<colgroup>++++++<col style="width:20%">++++++</col>+++
+   +++<col style="width:15%">++++++</col>+++
+   +++<col style="width:65%">++++++</col>++++++</colgroup>+++
+   +++<thead class="thead" style="text-align:left;">++++++<tr>++++++<th>+++Query Parameter+++</th>+++
+         +++<th>+++Data Type+++</th>+++
+         +++<th>+++Description+++</th>++++++</tr>++++++</thead>+++
+   +++<tbody>++++++<tr>++++++<td>++++++<code>+++id+++</code>++++++</td>+++
+      +++<td>+++string+++</td>+++
+      +++<td>+++ID of a particular answer or a pinboard.+++</td>++++++</tr>++++++</tbody>++++++</table>+++
+
+=== Request Example
+
+.cURL
+----
+curl -X GET --header 'Accept: application/json' --header 'X-Requested-By: ThoughtSpot' 'https://<instance>/callosum/v1/tspublic/v1/metadata/listvizheaders?id=97begg839e-71b6-42ad-a980-20c38b4d6db5'
+----
+
+.Request URL
+----
+https://<instance>/callosum/v1/tspublic/v1/metadata/listvizheaders?id=97be839e-71b6-42ggad-a980-20c38b4d6db5
+----
+
+=== Response Example
+
+----
+[
+  {
+    "id": "dd7f5467-99c3-4278-998b-6dd0c4346cd4",
+    "name": "Headline Viz answer book guid max timestamp answer book guid != {null} sort by max timestamp descending today last 180 days",
+    "author": "67e15c06-d153-4924-a4cd-ff615393b60f",
+    "created": 1536179170172,
+    "modified": 1536179170172,
+    "modifiedBy": "67e15c06-d153-4924-a4cd-ff615393b60f",
+    "owner": "ec718bc5-4608-4ea9-93e2-c1f82e9f2b31"
+  },
+  {
+    "id": "fcb65fdb-3965-4f56-8bda-e5e3c2a127a7",
+    "name": "Filter Viz answer book guid max timestamp answer book guid != {null} sort by max timestamp descending today last 180 days Row: 1",
+    "author": "67e15c06-d153-4924-a4cd-ff615393b60f",
+    "created": 1536179170172,
+    "modified": 1536179170172,
+    "modifiedBy": "67e15c06-d153-4924-a4cd-ff615393b60f",
+    "owner": "ec718bc5-4608-4ea9-93e2-c1f82e9f2b31"
+  },
+  {
+    "id": "0f6e7220-5088-4a0e-8122-50b637c356fc",
+    "name": "Table Viz answer book guid max timestamp answer book guid != {null} sort by max timestamp descending today last 180 days",
+    "author": "67e15c06-d153-4924-a4cd-ff615393b60f",
+    "created": 1536179170172,
+    "modified": 1536179170172,
+    "modifiedBy": "67e15c06-d153-4924-a4cd-ff615393b60f",
+    "owner": "ec718bc5-4608-4ea9-93e2-c1f82e9f2b31"
+  }
+]
+----
+
+== Get object headers
+
+Use this API to fetch a comprehensive list of metadata headers of a specific object type in the Thoughtspot system.
+
+=== Resource URL
+
+`get` /tspublic/v1/metadata/listobjectheaders
+
+=== Request Parameters+++<table>++++++<colgroup>++++++<col style="width:20%">++++++</col>+++
+   +++<col style="width:15%">++++++</col>+++
+   +++<col style="width:65%">++++++</col>++++++</colgroup>+++
+   +++<thead class="thead" style="text-align:left;">++++++<tr>++++++<th>+++Query Parameter+++</th>+++
+         +++<th>+++Data Type+++</th>+++
+         +++<th>+++Description+++</th>++++++</tr>++++++</thead>+++
+   +++<tbody>++++++<tr>++++++<td>++++++<code>+++type+++</code>++++++</td>+++
+      +++<td>+++string+++</td>+++
+      +++<td>+++Specifies the metadata object type. Valid values are:
+         +++<ul>++++++<li>++++++<code>+++QUESTION_ANSWER_BOOK+++</code>++++++</li>+++
+         +++<li>++++++<code>+++PINBOARD_ANSWER_BOOK+++</code>++++++</li>+++
+         +++<li>++++++<code>+++QUESTION_ANSWER_SHEET+++</code>++++++</li>+++
+         +++<li>++++++<code>+++PINBOARD_ANSWER_SHEET+++</code>++++++</li>+++
+         +++<li>++++++<code>+++LOGICAL_COLUMN+++</code>++++++</li>+++
+         +++<li>++++++<code>+++LOGICAL_TABLE+++</code>++++++</li>+++
+         +++<li>++++++<code>+++LOGICAL_RELATIONSHIP+++</code>++++++</li>+++
+         +++<li>++++++<code>+++TAG+++</code>++++++</li>+++
+         +++<li>++++++<code>+++DATA_SOURCE+++</code>++++++</li>++++++</ul>++++++</td>++++++</tr>+++
+    +++<tr>++++++<td>++++++<code>+++subtypes+++</code>++++++</td>+++
+      +++<td>+++string+++</td>+++
+      +++<td>+++Specifies the sub-types of metadata object. Valid values are:
+      +++<ul>++++++<li>++++++<code>+++ONE_TO_ONE_LOGICAL+++</code>++++++</li>+++
+      +++<li>++++++<code>+++WORKSHEET+++</code>++++++</li>+++
+      +++<li>++++++<code>+++PRIVATE_WORKSHEET+++</code>++++++</li>+++
+      +++<li>++++++<code>+++USER_DEFINED+++</code>++++++</li>+++
+      +++<li>++++++<code>+++AGGR_WORKSHEET+++</code>++++++</li>++++++</ul>+++
+      +++<b>+++Note:+++</b>+++ This parameter only applies to the +++<code>+++LOGICAL_TABLE+++</code>+++ type.+++</td>++++++</tr>+++
+    +++<tr>++++++<td>++++++<code>+++category+++</code>++++++</td>+++
+      +++<td>+++string+++</td>+++
+      +++<td>+++Specifies the metadata object category. Valid values are:
+      +++<ul>++++++<li>++++++<code>+++ALL+++</code>++++++</li>+++
+      +++<li>++++++<code>+++MY+++</code>++++++</li>+++
+      +++<li>++++++<code>+++FAVORITE+++</code>++++++</li>+++
+      +++<li>++++++<code>+++REQUESTED+++</code>++++++</li>++++++</ul>++++++</td>++++++</tr>+++
+    +++<tr>++++++<td>++++++<code>+++sort+++</code>++++++</td>+++
+      +++<td>+++string+++</td>+++
+      +++<td>+++Sort order of returned headers. Valid values are:
+          +++<ul>++++++<li>++++++<code>+++DEFAULT+++</code>++++++</li>+++
+          +++<li>++++++<code>+++NAME+++</code>++++++</li>+++
+          +++<li>++++++<code>+++DISPLAY_NAME+++</code>++++++</li>+++
+          +++<li>++++++<code>+++AUTHOR+++</code>++++++</li>+++
+          +++<li>++++++<code>+++CREATED+++</code>++++++</li>+++
+          +++<li>++++++<code>+++MODIFIED+++</code>++++++</li>++++++</ul>++++++</td>++++++</tr>+++
+    +++<tr>++++++<td>++++++<code>+++sortascending+++</code>++++++</td>+++
+      +++<td>+++boolean+++</td>+++
+      +++<td>+++A flag to specify the sort order. A null value defines the default order.
+      +++<ul>++++++<li>+++Choose +++<code>+++true+++</code>+++ to set ascending order+++</li>+++
+      +++<li>+++Choose +++<code>+++false+++</code>+++ to set descending order+++</li>++++++</ul>++++++</td>++++++</tr>+++
+    +++<tr>++++++<td>++++++<code>+++offset+++</code>++++++</td>+++
+      +++<td>+++integer+++</td>+++
+      +++<td>+++The batch offset to fetch the page headers. The system default is +++<code>+++-1+++</code>+++ that implies first page.+++</td>++++++</tr>+++
+    +++<tr>++++++<td>++++++<code>+++batchsize+++</code>++++++</td>+++
+      +++<td>+++integer+++</td>+++
+      +++<td>+++The batch size of the object. A value of +++<code>+++-1+++</code>+++ implies no pagination.+++</td>++++++</tr>+++
+    +++<tr>++++++<td>++++++<code>+++tagname+++</code>++++++</td>+++
+      +++<td>+++string+++</td>+++
+      +++<td>+++A JSON array containing a set of tag names to filter headers by.+++</td>++++++</tr>+++
+    +++<tr>++++++<td>++++++<code>+++pattern+++</code>++++++</td>+++
+      +++<td>+++string+++</td>+++
+      +++<td>+++A pattern to match for object name. Use +++<code>+++%+++</code>+++ for wildcard match.+++</td>++++++</tr>+++
+    +++<tr>++++++<td>++++++<code>+++skipids+++</code>++++++</td>+++
+      +++<td>+++string+++</td>+++
+      +++<td>+++IDs of metadata objects to exclude.+++</td>++++++</tr>+++
+    +++<tr>++++++<td>++++++<code>+++fetchids+++</code>++++++</td>+++
+      +++<td>+++string+++</td>+++
+      +++<td>+++IDs of metadata objects to fetch.+++</td>++++++</tr>+++
+    +++<tr>++++++<td>++++++<code>+++auto_created+++</code>++++++</td>+++
+      +++<td>+++boolean+++</td>+++
+      +++<td>+++A flag that indicates whether to list auto-created objects only. A value of null signifies return all.+++</td>++++++</tr>++++++</tbody>++++++</table>+++
+
+=== Request Example
+
+.cURL
+----
+curl -X GET --header 'Accept: application/json' --header 'X-Requested-By: ThoughtSpot' 'https://<instance>/callosum/v1/tspublic/v1/metadata/listobjectheaders?type=PINBOARD_ANSWER_BOOK&subtypes=WORKSHEET&category=ALL&sort=CREATED&offset=-1'
+----
+
+.Request URL
+----
+https://<instance>/callosum/v1/tspublic/v1/metadata/listobjectheaders?type=PINBOARD_ANSWER_BOOK&subtypes=WORKSHEET&category=ALL&sort=CREATED&offset=-1
+----
+
+=== Response Example
+
+----
+[
+  {
+    "id": "7752fa9e-db22-415e-bf34-e082c4bc41c3",
+    "name": "Basic Pinboard 1",
+    "description": "This pinboard contains one TPCH based visualization",
+    "author": "59481331-ee53-42be-a548-bd87be6ddd4a",
+    "created": 1450823023991,
+    "modified": 1504281997165,
+    "modifiedBy": "59481331-ee53-42be-a548-bd87be6ddd4a",
+    "owner": "7752fa9e-db22-415e-bf34-e082c4bc41c3",
+    "isAutoCreated": false,
+    "isAutoDelete": false
+  },
+  {
+    "id": "6715f768-8930-4180-9a3d-1efdbfaa8e7f",
+    "name": "Headline Pinboard",
+    "author": "59481331-ee53-42be-a548-bd87be6ddd4a",
+    "created": 1519940021267,
+    "modified": 1519945210514,
+    "modifiedBy": "59481331-ee53-42be-a548-bd87be6ddd4a",
+    "owner": "6715f768-8930-4180-9a3d-1efdbfaa8e7f",
+    "isAutoCreated": false,
+    "isAutoDelete": false
+  },
+  {
+    "id": "601be8e5-140e-477c-8812-843795306438",
+    "name": "Pinboard Filter - datatypes",
+    "author": "59481331-ee53-42be-a548-bd87be6ddd4a",
+    "created": 1519943239150,
+    "modified": 1519944533160,
+    "modifiedBy": "59481331-ee53-42be-a548-bd87be6ddd4a",
+    "owner": "601be8e5-140e-477c-8812-843795306438",
+    "isAutoCreated": false,
+    "isAutoDelete": false
+  }
+]
+----
+
+////
+## Error Codes
+<table>
+   <colgroup>
+      <col style="width:20%" />
+      <col style="width:60%" />
+      <col style="width:20%" />
+   </colgroup>
+   <thead class="thead" style="text-align:left;">
+      <tr>
+         <th>Error Code</th>
+         <th>Description</th>
+         <th>HTTP Code</th>
+      </tr>
+   </thead>
+   <tbody>
+    <tr> <td><code>10002</code></td>  <td>Bad request. Invalid parameter values i.e., wrong pinboard ID.</td> <td><code>400</code></td></tr>
+  </tbody>
+</table>
+////
diff --git a/docs/src/asciidocs/rest-api-reference.adoc b/docs/src/asciidocs/rest-api-reference.adoc
new file mode 100644
index 000000000..07996cb9b
--- /dev/null
+++ b/docs/src/asciidocs/rest-api-reference.adoc
@@ -0,0 +1,522 @@
+[[_pinboarddata]]
+=== Pinboard Data API
+
+Retrieves data for a pinboard or other visualization from the ThoughtSpot system.
+
+This API lets you fetch the following data:
+
+* All the visualization objects on a pinboard.
+* A specific visualization or a group of visualizations on a pinboard.
+
+
+
+==== Request URL
+....
+POST /tspublic/v1/pinboarddata
+....
+
+
+==== Parameters
+
+[options="header", cols=".^2a,.^3a,.^9a,.^4a,.^2a"]
+|===
+|Type|Name|Description|Data Type |Default
+|**Query**|**batchsize** +
+__optional__|The batch size for loading of pinboard objects.|integer (int32)|`-1`
+|**Query**|**formattype** +
+__optional__|Json format type. Valid values are FULL and COMPACT.|string|`"COMPACT"`
+|**Query**|**id** +
+__optional__|GUID ID of the pinboard.|string|
+|**Query**|**offset** +
+__optional__|Offset.|integer (int32)|`-1`
+|**Query**|**pagenumber** +
+__optional__|PageNumber. Alternate way to set offset. This is 1-based indexingOffset = (pageNumber - 1) * batchSize.|integer (int32)|`-1`
+|**Query**|**vizid** +
+__optional__|GUID IDs of visualizations. Use this parameter to fetch a specific visualization on a pinboard. |string|
+|===
+
+==== Example Request
+
+===== cURL
+----
+curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'X-Requested-By: ThoughtSpot' 'https://<instance>/callosum/v1/tspublic/v1/pinboarddata?id=f4533461-caa5-4efa-a189-13815ab86770&batchsize=-1&pagenumber=-1&offset=-1&formattype=COMPACT'
+----
+
+===== Request URL
+----
+https://<instance>/callosum/v1/tspublic/v1/pinboarddata?id=f4533461-caa5-4efa-a189-13815ab86770&batchsize=-1&pagenumber=-1&offset=-1&formattype=COMPACT
+----
+
+
+
+==== Responses
+
+
+===== Example Response 
+
+----
+{
+  "4fdf9d2c-6f34-4e3b-9fa6-bd0ca69676e1": {
+    "name": "Sample Name",
+    "columnNames": [
+      "Opportunity Stage",
+      "Opportunity Owner Name",
+      "Total Amount"
+    ],
+    "data": [
+      [
+        "s3 alignment with eb",
+        "jeff cameron",
+        1102272
+      ],
+      [
+        "s4 validation",
+        "brian mcquillan",
+        59150
+      ]
+    ],
+    "samplingRatio": 1,
+    "totalRowCount": 14,
+    "rowCount": 14,
+    "pageSize": 10,
+    "offset": 0
+  }
+}
+----
+===== Response Messages
+
+[options="header", cols=".^2a,.^14a,.^4a"]
+|===
+|HTTP Code|Description|Schema
+|**200**|gets the data of a pinboard/visualization|string
+|**400**|invalid pinboard id|No Content
+|===
+
+
+
+//==== Produces
+
+//* `application/json`
+
+
+//==== Tags
+
+//* tspublic/v1
+
+
+[[_searchdata]]
+=== Search API
+Search data from a specific data source in thoughtspot system
+
+=== Request URL
+....
+POST /tspublic/v1/searchdata
+....
+
+////
+==== Description
+Search data from a specific data source in thoughtspot system
+////
+
+==== Parameters
+
+[options="header", cols=".^2a,.^3a,.^9a,.^4a,.^2a"]
+|===
+|Type|Name|Description|Schema|Default
+|**Query**|**batchsize** +
+__optional__|Batch size|integer (int32)|`-1`
+|**Query**|**data_source_guid** +
+__optional__|Guid of the data source (ex: worksheet/table|string|
+|**Query**|**formattype** +
+__optional__|Json format type. Values allowed are FULL and COMPACT|string|`"COMPACT"`
+|**Query**|**offset** +
+__optional__|Offset|integer (int32)|`-1`
+|**Query**|**pagenumber** +
+__optional__|PageNumber. Alternate way to set offset. This is 1-based indexingOffset = (pageNumber - 1) * batchSize|integer (int32)|`-1`
+|**Query**|**query_string** +
+__optional__|Query string|string|
+|===
+
+
+==== Responses
+
+[options="header", cols=".^2a,.^14a,.^4a"]
+|===
+|HTTP Code|Description|Schema
+|**200**|gets the data from the data source|string
+|**400**|invalid query/data source|No Content
+|===
+
+
+[[_listobjectheaders]]
+=== Metadata object headers API
+List of metadata object headers in the repository
+
+=== Request URL
+....
+GET /tspublic/v1/metadata/listobjectheaders
+....
+
+////
+==== Description
+List of metadata object headers in the repository
+////
+
+==== Parameters
+
+[options="header", cols=".^2a,.^3a,.^9a,.^4a,.^2a"]
+|===
+|Type|Name|Description|Schema|Default
+|**Query**|**auto_created** +
+__optional__|List auto created objects only. null signifies return all.|boolean|
+|**Query**|**batchsize** +
+__optional__|Batch size; Unspecified implies system default; -1 implies no pagination|integer (int32)|
+|**Query**|**category** +
+__optional__|Category of metadata object. Valid values - ALL, MY, FAVORITE, REQUESTED|string|`"ALL"`
+|**Query**|**fetchids** +
+__optional__|GUID Ids of metadata objects to fetch|string|
+|**Query**|**offset** +
+__optional__|Batch offset to fetch page of headers; -1 implies first page|integer (int32)|`-1`
+|**Query**|**pattern** +
+__optional__|Pattern to match for object names (use '%' for wildcard match|string|
+|**Query**|**skipids** +
+__optional__|GUID Ids of metadata objects to exclude|string|
+|**Query**|**sort** +
+__optional__|Sort order of returned headers. Valid values - DEFAULT, NAME, DISPLAY_NAME, AUTHOR, CREATED, MODIFIED|string|`"DEFAULT"`
+|**Query**|**sortascending** +
+__optional__|Flag for direction of sorting (null signifies default order, true signifies ascending order and false signifies descending order)|boolean|
+|**Query**|**subtypes** +
+__optional__|List of sub-Types of metadata object. Applies for LOGICAL_TABLE type with valid values - ONE_TO_ONE_LOGICAL, WORKSHEET, PRIVATE_WORKSHEET, USER_DEFINED, AGGR_WORKSHEET|string|
+|**Query**|**tagname** +
+__optional__|Set of tag names to filter headers by; JSON Array of name Strings|string|
+|**Query**|**type** +
+__optional__|Type of metadata object. Valid values - QUESTION_ANSWER_BOOK, PINBOARD_ANSWER_BOOK, QUESTION_ANSWER_SHEET, PINBOARD_ANSWER_SHEET, LOGICAL_COLUMN, LOGICAL_TABLE, LOGICAL_RELATIONSHIP, TAG, DATA_SOURCE|string|`"PINBOARD_ANSWER_BOOK"`
+|===
+
+
+==== Responses
+
+[options="header", cols=".^2a,.^14a,.^4a"]
+|===
+|HTTP Code|Description|Schema
+|**200**|Metadata Headers JSON|string
+|===
+
+
+
+[[_getvisualizationheaders]]
+=== Metadata visualization header API
+....
+GET /tspublic/v1/metadata/listvizheaders
+....
+
+
+==== Description
+Get the visualization headers from the ThoughtSpot system.
+
+
+==== Parameters
+
+[options="header", cols=".^2a,.^3a,.^9a,.^4a"]
+|===
+|Type|Name|Description|Schema
+|**Query**|**id** +
+__optional__|GUID of the reportbook|string
+|===
+
+
+==== Responses
+
+[options="header", cols=".^2a,.^14a,.^4a"]
+|===
+|HTTP Code|Description|Schema
+|**200**|gets the visualization headers|string
+|**400**|invalid pinboard GUID|No Content
+|===
+
+
+==== Produces
+
+* `application/json`
+
+
+==== Tags
+
+* tspublic/v1/metadata
+
+[[_login]]
+=== Session Login
+....
+POST /tspublic/v1/session/login
+....
+
+
+==== Description
+Authenticate and login a user
+
+
+==== Parameters
+
+[options="header", cols=".^2a,.^3a,.^9a,.^4a,.^2a"]
+|===
+|Type|Name|Description|Schema|Default
+|**FormData**|**password** +
+__optional__|Password|string|
+|**FormData**|**rememberme** +
+__optional__|Flag to indicate if user session should be remembered|boolean|`"false"`
+|**FormData**|**username** +
+__optional__|Username|string|
+|===
+
+
+==== Responses
+
+[options="header", cols=".^2a,.^14a,.^4a"]
+|===
+|HTTP Code|Description|Schema
+|**200**|No response was specified|No Content
+|**204**|Successful login|No Content
+|**401**|Login failure/unauthorized|No Content
+|===
+
+
+
+
+[[_logout]]
+=== Session Logout
+....
+POST /tspublic/v1/session/logout
+....
+
+
+==== Description
+Logout current user
+
+
+==== Responses
+
+[options="header", cols=".^2a,.^14a,.^4a"]
+|===
+|HTTP Code|Description|Schema
+|**200**|No response was specified|No Content
+|**204**|Successful logout|No Content
+|**401**|Logout failure/unauthorized|No Content
+|===
+
+
+==== Tags
+
+* tspublic/v1/session
+
+
+[[_list]]
+=== Fetch users and groups
+....
+GET /tspublic/v1/user/list
+....
+
+
+==== Description
+Api to get all users, groups and their inter-dependencies
+
+
+==== Responses
+
+[options="header", cols=".^2a,.^14a,.^4a"]
+|===
+|HTTP Code|Description|Schema
+|**200**|Description was not specified|string
+|===
+
+
+
+
+[[_synchronizeprincipals]]
+=== Synchronize Principals
+....
+POST /tspublic/v1/user/sync
+....
+
+
+==== Description
+Api to synchronize principal from external system with ThoughtSpot system
+
+
+==== Parameters
+
+[options="header", cols=".^2a,.^3a,.^4a,.^2a"]
+|===
+|Type|Name|Schema|Default
+|**FormData**|**applyChanges** +
+__optional__|boolean|`"false"`
+|**FormData**|**password** +
+__optional__|string|
+|**FormData**|**principals** +
+__optional__|string|
+|**FormData**|**removeDeleted** +
+__optional__|boolean|`"true"`
+|===
+
+
+==== Responses
+
+[options="header", cols=".^2a,.^14a,.^4a"]
+|===
+|HTTP Code|Description|Schema
+|**200**|Description was not specified|string
+|===
+
+
+==== Consumes
+
+* `multipart/form-data`
+
+
+==== Produces
+
+* `application/json`
+
+
+==== Tags
+
+* tspublic/v1/user
+
+
+[[_transferownership]]
+=== Transfer ownership of all objects from one user to another
+....
+POST /tspublic/v1/user/transfer/ownership
+....
+
+
+==== Description
+Api to transfer ownership of all objects from one user to another
+
+
+==== Parameters
+
+[options="header", cols=".^2a,.^3a,.^4a"]
+|===
+|Type|Name|Schema
+|**Query**|**fromUserName** +
+__optional__|string
+|**Query**|**toUserName** +
+__optional__|string
+|===
+
+
+==== Responses
+
+[options="header", cols=".^2a,.^14a,.^4a"]
+|===
+|HTTP Code|Description|Schema
+|**200**|if ownership of all objects are successfully transferred|No Content
+|**400**|In case of invalid fromName and toName or for given username there is no user present.|No Content
+|===
+
+
+
+
+[[_changepassword]]
+=== Change password of user
+....
+POST /tspublic/v1/user/updatepassword
+....
+
+
+==== Description
+Api to change password of a user.
+
+
+==== Parameters
+
+[options="header", cols=".^2a,.^3a,.^9a,.^4a"]
+|===
+|Type|Name|Description|Schema
+|**FormData**|**currentpassword** +
+__optional__|Current password of the logged in user|string
+|**FormData**|**name** +
+__optional__|Name of the user whose password needs to be updated/|string
+|**FormData**|**password** +
+__optional__|New password of the logged in user|string
+|===
+
+
+==== Responses
+
+[options="header", cols=".^2a,.^14a,.^4a"]
+|===
+|HTTP Code|Description|Schema
+|**200**|If the password of the user is changed successfully.|No Content
+|===
+
+
+[[_addprivilege]]
+=== Add Privilege
+....
+POST /tspublic/v1/group/addprivilege
+....
+
+
+==== Description
+Add privilege to groups
+
+
+==== Parameters
+
+[options="header", cols=".^2a,.^3a,.^4a"]
+|===
+|Type|Name|Schema
+|**FormData**|**groupNames** +
+__optional__|string
+|**FormData**|**privilege** +
+__optional__|string
+|===
+
+
+==== Responses
+
+[options="header", cols=".^2a,.^14a,.^4a"]
+|===
+|HTTP Code|Description|Schema
+|**200**|No response was specified|No Content
+|**204**|Success|No Content
+|**401**|Failure/Unauthorized|No Content
+|===
+
+
+
+[[_removeprivilege]]
+=== Remove Privilege
+....
+POST /tspublic/v1/group/removeprivilege
+....
+
+
+==== Description
+Remove privilege from groups
+
+
+==== Parameters
+
+[options="header", cols=".^2a,.^3a,.^4a"]
+|===
+|Type|Name|Schema
+|**FormData**|**groupNames** +
+__optional__|string
+|**FormData**|**privilege** +
+__optional__|string
+|===
+
+
+==== Responses
+
+[options="header", cols=".^2a,.^14a,.^4a"]
+|===
+|HTTP Code|Description|Schema
+|**200**|No response was specified|No Content
+|**204**|Success|No Content
+|**401**|Failure/Unauthorized|No Content
+|===
+
+
diff --git a/docs/src/asciidocs/search-data-api.adoc b/docs/src/asciidocs/search-data-api.adoc
new file mode 100644
index 000000000..b4d1d3363
--- /dev/null
+++ b/docs/src/asciidocs/search-data-api.adoc
@@ -0,0 +1,249 @@
+= Search Data API
+last_updated: 4/21/2020
+To use the data retrieved from a search query programmatically, you can first query this data using the ThoughtSpot Search Data API.
+
+It is often difficult to programmatically use the result set of a query that runs in the ThoughtSpot UI search  bar.  To use the data that we retrieve from a query programmatically, you can use ThoughtSpot Search Data API.
+
+When issuing a query through the ThoughtSpot UI, users make selections to disambiguate a query. Because selection is not possible with an API approach, we modified the API query language to include query disambiguation. See <<Components of a search query>>.
+
+== Resource URL
+
+`post/tspublic/v1/searchdata`
+
+== Request Parameters
+
+[width="100%",options="header",cols="20%,20%,60%
+|====================
+| Query Parameter | Data Type | Description
+| `query_string` | string | The data search query.
+
+See <<Components of a search query>>.
+|`data_source_guid`  | string | The GUID of the data source, either a worksheet, a view, or a table.
+
+Example: 4fdf9d2c-6f34-4e3b-9fa6-bd0ca69676e1
+|`batchsize`  | integer | The batch size for loading search objects.
+
+The system default is -1.
+| pagenumber | integer | Alternate way to specify 1-based offset:
+
+`indexingOffset = (pageNumber - 1) * batchSize`
+
+The system default is -1.
+| offset | integer | Specify a 1-based offset.
+
+The system default is -1.
+| `formattype` | string | The format of the data.
+
+Valid values are `COMPACT` (default) or `FULL` JSON.
+|====================
+
+[id="components
+== Components of a search query
+
+In ThoughtSpot Query Language, we classify components of a query into various types of tokens: xref:Column[Column], xref:Operator[Operator], xref:Value[Value], xref:Date-Bucket[Date Bucket], xref:Keyword[Keyword], and xref:Calendar[Calendar]:
+
+[#Column]
+Column:: Columns must be enclosed in square brackets, [ ].
+
+*Example* In the query revenue by ship mode, both revenue and ship mode are columns. A valid query for the API is:
+
+```
+[revenue] by [ship mode]
+```
+[#Operator]
+Operator:: ThoughtSpot supports various operators such as =, !=, >, >=, <=, <, contains, not contains, and so on. Use these operators in the API query in the same manner as in the UI.
++
+*Example* Specify revenue over 1000, and limit ship mode to 'air':
++
+```
+[revenue] > 1000 [ship mode] = ‘air’
+```
+[#Value]
+Value:: String (text) and date values must be enclosed within quotes, ’ ’. Do not use quotes for numeric values, except for dates.
++
+When using multiple values, separate them by a comma, ,.
++
+*Example* When a ThoughtSpot UI query is revenue top 2 ship mode, the equivalent API query is:
++
+```
+[revenue] top 2 [ship mode]
+```
++
+*Example* When a ThoughtSpot UI query is revenue ship mode = air, the equivalent API query is:
++
+```
+[revenue] [ship mode] = ‘air’
+```
+[#Date-Bucket]
+Date Bucket:: In the ThoughtSpot UI, when there are several date columns, users can bind date bucket tokens to a specific column. When using the API, this binding between the date column and the date bucket must be made explicit. The column with which the date bucket is bound, and the date bucket token, must be separated by a period, ..
++
+Single word date buckets can be expressed as is. Multi-word date buckets must be enclosed within quotes.
++
+*Example* When a ThoughtSpot UI query is revenue commit date monthly, and if monthly is bound to commit date, the equivalent API query is:
++
+```
+[revenue] [commit date].monthly
+```
++
+*Example* When a ThoughtSpot UI query is revenue day of week = 5, and if day of week is bound to commit date, the equivalent API query is:
++
+```
+[revenue] [commit date].'day of week' = 5
+```
+Keyword:: Use keywords in the API query in the same manner as in the UI.
++
+*Example* When a ThoughtSpot UI query uses keywords growth of and sort by, the equivalent API query is:
++
+```
+growth of [revenue] by [commit date]
+```
+Calendar:: You can specify a custom calendar in the query. Use the calendar.calendar_name format explicitly.
++
+When the calendar name contains multiple words, these words must be enclosed in single quotes.
++
+*Example* When a ThoughtSpot UI query is revenue by commit date fiscal, where the name of the calendar is fiscal, the equivalent API query is:
++
+```
+[revenue] by [commit date] calendar.fiscal
+```
++
+Example When a ThoughtSpot UI query is revenue by commit date my calendar, where the name of the calendar is my calendar, the equivalent API query is:
++
+```
+[revenue] by [commit date] calendar.'my calendar'
+```
+== Request example
+
+=== cURL - COMPACT
+
+```
+curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'X-Requested-By: ThoughtSpot' 'https://<instance>/callosum/v1/tspublic/v1/searchdata?query_string=%5Bsales%5D%20%5Bstore%20region%5D&data_source_guid=06517bd1-84c0-4bc6-bd09-f57af52e8316&batchsize=-1&pagenumber=-1&offset=-1&formattype=COMPACT'
+```
+
+=== Request URL - COMPACT
+
+```
+https://<instance>/callosum/v1/tspublic/v1/searchdata?query_string=%5Bsales%5D%20%5Bstore%20region%5D&data_source_guid=06517bd1-84c0-4bc6-bd09-f57af52e8316&batchsize=-1&pagenumber=-1&offset=-1&formattype=COMPACT
+```
+
+=== cURL - FULL
+
+```
+curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'X-Requested-By: ThoughtSpot' 'https://<instance>/callosum/v1/tspublic/v1/searchdata?query_string=%5Bsales%5D%20%5Bstore%20region%5D&data_source_guid=06517bd1-84c0-4bc6-bd09-f57af52e8316&batchsize=-1&pagenumber=-1&offset=-1&formattype=FULL’
+```
+
+=== Request URL - FULL
+```
+https://<instance>/callosum/v1/tspublic/v1/searchdata?query_string=%5Bsales%5D%20%5Bstore%20region%5D&data_source_guid=06517bd1-84c0-4bc6-bd09-f57af52e8316&batchsize=-1&pagenumber=-1&offset=-1&formattype=FULL
+```
+
+== Response example
+
+```
+{
+  "columnNames": [
+    "Store Region",
+    "Total Sales"
+  ],
+  "data": [
+    [
+      "east",
+      18934491.05134509
+    ],
+    [
+      "midwest",
+      29157090.327609923
+    ],
+    [
+      "south",
+      25484693.074720126
+    ],
+    [
+      "southwest",
+      34241076.52103955
+    ],
+    [
+      "west",
+      30848491.458509445
+    ]
+  ],
+  "samplingRatio": 1,
+  "totalRowCount": 5,
+  "rowCount": 5,
+  "pageSize": 100000,
+  "offset": 0
+}
+```
+
+== Using the Search Data API
+
+To test the search query API, follow these steps:
+
+[#"get-guid
+=== Determine the GUID of the data source
+
+. In a Web Browser tab, navigate to the following address, and log in as admin user:
+
+   ```
+   https://<instance>/
+   ```
+
+. In the top navigation, click **Data**.
+
+   Alternatively, navigate to the following address:
+
+   ```
+   https://<instance>/#/data/tables/
+   ```
+
+. Select a data source that you plan to query: a worksheet, a table, or a view.
+
+. In the address bar of the Web Browse, note the GUID of the selected data source; it is the last string of the address.  For example, in the following address string, the GUID is `9d93a6b8-ca3a-4146-a1a1-e908b71b963f`:
+
+    ```
+    https://<instance>/#/data/tables/9d93a6b8-ca3a-4146-a1a1-e908b71b963f
+    ```
+
+. Copy and save the GUID.
+
+=== Run the Search Data API
+
+. In another browser, navigate to the following address:
+
+  ```
+  https://<instance>/external/swagger/#!/tspublic%2Fv1/searchData
+  ```
+
+. Click on `POST /tspublic/v1/searchdataTS`.
+
+   The parameter interface appears.
+
+. In the **Parameters** interface, enter the values for the following:
+
+    - `query_string` is the actual search query. See [Components of a search query](#components).
+    - `data_source_guid` is the identifier you  obtained earlier, in [Determine the GUID of the data sources](#get-guid).
+
+    You can leave other parameters at their default value.
+
+. Click **Try it out!**, and note the results.
+
+   You may wish to check that the same query, when you run it in the ThoughtSpot UI search bar (with slightly different syntax), returns the same data.
+
+== Limitations of Search Query API
+
+- To avoid join path ambiguities, a query can use only a **single data source**.
+
+- Search execution of query strings is **case insensitive**.
+
+- All Column names in the data source must have **unique names** that also pass the "case insensitivity" test.
+
+  For example, Columns `[Revenue]` and `[revenue]` are not unique.
+- Column names cannot contain square brackets, `[` or `]`.
+
+- Values must be enclosed in quotes, `‘’`, but they cannot contain quotes.
+
+- The API does not support **in-query formula** definitions. To use a formula, first create it on the worksheet or a table using the ThoughtSpot UI, and then use the named formula inside the API query.
+
+- Users must be **authenticated** and have **read access** to the data source.
+
+- Your browser locale must be `en-US`. Swagger does not accept other variations of English, such as British English, or other languages. Your search keywords must also be in American English. Your column names and other data values do **not** need to be in American English. You can change your preferred locale to `en-US` in your browser settings.
diff --git a/docs/src/asciidocs/visual-embed-sdk.adoc b/docs/src/asciidocs/visual-embed-sdk.adoc
new file mode 100644
index 000000000..f7435a649
--- /dev/null
+++ b/docs/src/asciidocs/visual-embed-sdk.adoc
@@ -0,0 +1,135 @@
+= What is Visual Embed SDK
+:toc: true
+The Visual Embed SDK provides a set of APIs delivered as a Javascript library to programatically embed ThoughtSpot elements in a host application.
+
+You can use the Visual Embed SDK to:
+
+* Embed specific components of ThoughtSpot application. For example, search bar, search answers page, pinboards, charts, and tables.
+* Render full ThoughtSpot application within the host application.
+* Render charts, visualizations, and pinboards.
+
+== Visual Embed SDK Libraries
+
+The Visual Embed SDK for Javascript bundles the following TypeScript definition files:
+
+* `base.ts`
+* `search.ts`
+* `pinboard.ts`
+* `app.ts`
+
+=== Embed Search
+The Visual Embed SDK includes the `search.ts` definition file to help you integrate the search bar and search answers page. Users can select data sources and search for the required data. The JavaScript library for search does not add the ThoughtSpot navigation bar, so users will not be able to navigate to other parts of the ThoughtSpot application.
+
+For information on embedding the ThoughtSpot search functionality, see *<add a link to the embed search tutorial page>*
+
+=== Embed Pinboards and Visualizations
+
+The Visual Embed SDK includes the `pinboard.ts` definition file to help you embed pinboards in the iframes elements of your application.
+
+*<add a link to the embed pinboard tutorial page>*
+
+=== Embed the Full ThoughtSpot Application
+
+You can embed the full application with or without the navigation bar. The `app.ts` definition file helps you embed the full application and load the entire ThoughtSpot application, including menu bars.
+ 
+*<add a link to the full application tutorial page>*
+
+
+////
+
+
+You can also use the ThoughtSpot data APIs to request data from ThoughtSpot.
+
+=== Configuration requirements for embedding
+
+Only Extended Enterprise installation can use ThoughtSpot's embed functionality.
+ThoughtSpot Enterprise installations must also work with ThoughtSpot Support to enable embed before using this functionality.
+
+=== Optional settings for embedding
+
+There are some settings that apply to embedding which ThoughtSpot Support or your other ThoughtSpot technical contact can make for you.
+
+One of these involves what happens when a user clicks on a link within the data.
+When your data includes URLs, they display as clickable links in ThoughtSpot tables.
+By default, clicking on a link opens the URL in a separate tab.
+But there is a system-wide setting that can be changed to open the links within the context in which they appear.
+
+Changing this setting opens the links.
+Consider the possible link types, and how they open:
++++<dlentry>+++Link in search result table in ThoughtSpot::::  Same browser tab as ThoughtSpot application+++</dlentry>++++++<dlentry>+++Link in table embedded in an `<iframe>`::::  Same `<iframe>` that contains the table+++</dlentry>++++++<dlentry>+++Link in full ThoughtSpot application embedded in an `<iframe>` element::::  Same `<iframe>` that contains the application+++</dlentry>+++
+
+== Choose an authentication methodology
+
+You can control which type of authentication you use between your client application and ThoughtSpot.
+
+=== No Authentication
+
+You can simply not set up authentication.
+This would require the user to be _already logged into ThoughtSpot_, before interacting with the client application.
+This approach is for testing the client.
+Do not use this in a production environment.
+
+=== SAML
+
+Before you can embed all or part of ThoughtSpot, you must authenticate to ThoughtSpot using SAML with the public REST API call.
+After authentication, a URL is provided to call the desired visualization, and populate it into an `<iframe>` element.
+
+You must link:{{ site.baseurl}}/admin/setup/configure-SAML-with-tscli.html[configure SAML] on your ThoughtSpot instance before using this method.
+
+=== Trusted authentication service
+
+A ThoughtSpot installation can enable support for token-based authentication service.
+This allows an installation to use a central authentication service rather than using ThoughtSpot to authenticate.
+In this architecture, ThoughtSpot provides the service with a token that allows it to authenticate on behalf of users.
+
+A trusted authenticator application or service obtains a token from ThoughtSpot.
+This token is used to obtain trust from other, third-party client applications that need access to ThoughtSpot.
+In the following scenario, the trust authenticator forwards requests for ThoughtSpot data from client applications to ThoughtSpot.
+
+image::authentication.png[]
+
+A user who is already logged into client-application interacts with a ThoughtSpot embed point, which initiates the following processes:
+
+. The client-side application requests a user token from the trusted authenticator.
+. The trusted authenticator requests a user token from ThoughtSpot.
+. ThoughtSpot verifies the authenticator and returns a user token.
+. The authenticator returns the user token to the client.
+. The client forwards the user token to ThoughtSpot.
+. ThoughtSpot validates the token and returns information commensurate with that authenticated user's authorization.
+
+== Plan for cross-origin HTTP Requests (CORS)
+
+Collecting user credentials from one application (domain) and sending them to another application (such as ThoughtSpot) can present security vulnerabilities.
+Cross-origin or cross-domain verification prevents such security risks.
+
+When embedding, you must enable CORS between your client application domain and the ThoughtSpot domain.
+This protects your data, so that another actor cannot use the same URL to embed the visualization in its own Web pages.
+
+== Decide if you need to change the feedback email
+
+ThoughtSpot has an automated feature that collects feedback from users and sends it to ThoughtSpot Support.
+Depending on what and how you embed, user actions with your embedded application can trigger feedback.
+You can continue to forward feedback in this manner or direct the feedback to another email.
+To learn how to change the feedback email, see link:{{site.baseurl }}/admin/setup/work-with-ts-support.html#manage-the-feedback-contact[Manage the feedback contact].
+
+== Remove the ThoughtSpot branded footer
+
+The ThoughtSpot footer appears by default in the ThoughtSpot application.
+It also appears with an embed application that encompasses an individual Pinboard, or a full application.
+In embed applications that are have a single visualization, you can ask your ThoughtSpot support engineer to disable the footer.
+////
+
+
+////
+To embed with the navigation bar, call: +https://<thoughtspot-url>?embedApp=false#/+ +
+To embed without the navigation bar, call: +https://<thoughtspot-url>?embedApp=true#/+ 
+
+If you use +embedApp=true+ with this link, you will get the home page with no navigation bar, so you will need to provide navigation to use ThoughtSpot.  
+
+=== Embed a ThoughtSpot Page
+
+You can also embed particular pages, such as search, pinboards, etc.  The format for this call is: +https://<thoughtspot-url>?embedApp=true#/answer+
+
+This call shows the search page with no navigation bar.  Users can select data sources and search against the data, but not navigate to other parts of the application.
+
+////