Deleting the Time Frames – synthetic API

The POST method of the API deletes single or list of Time Frames.

Before you begin

You must obtain an authToken by using the login API. The token authenticates the user performing the operation. For details, see TSWS authentication .

Synthetic configuration APIs


  • If you have upgraded to version 11.3.02, you can access the Synthetic Blackout and Synthetic Time Frames APIs listed in this table.
  • If you are using version 11.3.01 or earlier, you can continue to use the Execution Plan APIs to access the Blackouts.

GETRetrieve the details of applications

Update an existing application

POSTCreate a new application
DELETEDelete an application

Execution Plans

GETRetrieve the details of Execution Plans
DELETEDelete an Execution Plan
ScriptsGETRetrieve the details of scripts
LocationsGETRetrieve the details of all locations


POSTRetrieve the details of Blackouts
POSTActivate the Blackout
POSTDeactivate the Blackout
POSTDelete a Blackout

Time Frames

POSTRetrieve the details of Time Frames
POSTDelete Time Frames

To delete Time Frames

The API uses the POST method to delete one or list of Time Frames.

Request syntax


Request parameters


Value of authToken

Sample request with REST client

After accessing the REST client, perform the following steps:

  1. Enter the URL for the API.
    The generic format is as follows:
  2. Add a new header row and select Authorization as the header type.
  3. Enter the text authToken followed by the authToken generated through the login API. 
  4. Enter a single Time Frame ID or the list of Time Frame IDs in the request body.
  5. Click Send.

Request body

To delete, the request body must contain a single or the list of Time Frame IDs.

 ["3a48f0f0-a13e-44f0-b001-8a66e9262236", "3a18f0f0-a13e-44f0-b001-8a77e9261236"]


If the delete operation is successful, the response is an empty array.

If the delete operation fails, the response returns a collection of Time Frame IDs that could not be deleted. For example, 

 ["3a48f0f0-a13e-44f0-b001-8a66e9262236", "3a18f0f0-a13e-44f0-b001-8a77e9261236"]

Related topics


Was this page helpful? Yes No Submitting... Thank you