NEW!!! Update the CSDL code of a recording while it is running or rename a recording.

To learn how to use the endpoints together take a look at our PYLON API step-by-step page.

An HTTP PUT request sent to:

A successful call to this endpoint returns: 204 No content.


Parameter Description

The id of the recording.


The hash of the new CSDL. The hash is a required parameter if you are updating the CSDL of your recording.


A new name for your recording. The name is a required parameter if you are renaming a recording.


Sample request

curl -X PUT 
    -d '{"hash":"1a4268c9b924d2c48ed8946d6a7e6272", "id":"d1b7d73b47c639ea3cc290595bca888ca4388afe","name":"my_new_test"}' 
    -H "Content-type: application/json" 
    -H 'Authorization: username:api_key'


HTTP/1.1 204


Response code Description
Status 204 No Content The recording was successfully updated.
Status 400 Bad Request

You omitted the id parameter.

{ "error": "No id was supplied." }

You specified the id but not the name or the hash.

{ "error": "Nothing to update specify a name or hash value to update" }

Status 404 Not Found No recording with that id could be found. Or you are attempting to use a version of the API prior to v1.3.


  1. All calls to the API must be properly authenticated with a DataSift username and API key.
  2. All calls to the API must be versioned. The current version is v1.3.
  3. Note that the username is the one you use to log in to and to make calls to any of the REST endpoints but the API key is the one that was returned by your call to the  POST /account/identity endpoint. That is, it is an identity-based API key.
  4. Take a look at our Changelog page to review the changes we've made to the DataSift API over time.
  5. Changes take effect a few seconds after you call this endpoint.

Revision history


This endpoint appears for the first time in v1.3.

Resource information

Rate limit cost: 25