How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

ThoughtSpot Schedules API

The Schedules API from ThoughtSpot — 4 operation(s) for schedules.

ThoughtSpot Schedules API is one of 29 APIs that ThoughtSpot publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Schedules. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, and authentication docs.

This API exposes 4 operations across 4 paths, and defines 23 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, {base-url}.

4 operations 4 paths 23 schemas 4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://my.thoughtspot.cloud/api/rest/2.0
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

ThoughtSpot Schedules API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 4 POST. Each is listed below with its method, path, parameters, and response codes.

Schedules 4
POST
/api/rest/2.0/schedules/create
Create schedule. Version: 9.4.0.cl or later Creates a Liveboard schedule job. Requires at least edit access to Liveboards. To create a schedule on behalf of another user, you need ADMINISTRATION (Can…
createSchedule body → 200400401403500
POST
/api/rest/2.0/schedules/{schedule_identifier}/delete
Deletes a scheduled job. Version: 9.4.0.cl or later Deletes a scheduled Liveboard job. Requires at least edit access to Liveboard or ADMINISTRATION (Can administer Org) privilege. If [Role-Based Acce…
deleteSchedule 1 param → 204400401403500
POST
/api/rest/2.0/schedules/search
Search Schedules Version: 9.4.0.cl or later Gets a list of scheduled jobs configured for a Liveboard. To get details of a specific scheduled job, specify the name or GUID of the scheduled job. Requir…
searchSchedules body → 200400401403500
POST
/api/rest/2.0/schedules/{schedule_identifier}/update
Update schedule. Version: 9.4.0.cl or later Updates a scheduled Liveboard job. Requires at least edit access to Liveboards. To update a schedule on behalf of another user, you need ADMINISTRATION (Ca…
updateSchedule 1 param body → 204400401403500

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are ResponseSchedule (15 properties), UpdateScheduleRequest (12 properties), CreateScheduleRequest (11 properties), SchedulesPdfOptionsInput (9 properties). Each schema is shown below with its type and property counts.

SortingOptions
object
Sort options.
2 properties
LiveboardOptionsInput
object
Options to specify details of Liveboard.
1 property 1 required
SearchSchedulesRequest
object
6 properties
PdfOptions
object
Options for PDF export.
9 properties
Author
object
Author of the schedule.
2 properties 2 required
CronExpression
object
Schedule selected cron expression.
6 properties 6 required
ResponseScheduleRun
object
Schedule run response object
5 properties 4 required
UpdateScheduleRequest
object
12 properties
Frequency
object
Configuration of schedule with cron expression
1 property 1 required
MetadataResponse
object
3 properties 2 required
PrincipalsListItem
object
2 properties 2 required
LiveboardOptions
object
Options to specify details of Liveboard.
1 property 1 required
MetadataInput
object
2 properties
RecipientDetailsInput
object
Recipients of the scheduled job notification.
2 properties
CreateScheduleRequest
object
11 properties 6 required
ErrorResponse
object
1 property
RecipientDetails
object
Recipient configuration which includes email address, ID or name of the users and groups.
2 properties
FrequencyInput
object
Configuration of schedule with cron expression
1 property 1 required
CronExpressionInput
object
Schedule selected cron expression.
6 properties 6 required
SchedulesPdfOptionsInput
object
Options for PDF export.
9 properties
PrincipalsListItemInput
object
2 properties 2 required
ScheduleHistoryRunsOptionsInput
object
3 properties
ResponseSchedule
object
15 properties 9 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

thoughtspot-schedules-api-openapi.yml Raw ↑

Other APIs ThoughtSpot publishes across the network.

ThoughtSpot AI API
ThoughtSpot Authentication API
ThoughtSpot Collections API
ThoughtSpot Connection Configurations API
ThoughtSpot Connections API
ThoughtSpot Custom Action API
ThoughtSpot Custom Calendars API
ThoughtSpot Data API
ThoughtSpot DBT API
ThoughtSpot Email Customization API
ThoughtSpot Groups API
ThoughtSpot Input Tables API
Where this information came from

This is an independent, third-party profile of ThoughtSpot Schedules API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.