POST /account/identity

Create a new identity.

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

An HTTPS POST request sent to:

A successful call to this endpoint returns: 201 Created plus a JSON object.


Parameter Description

The label for this new identity.


The status of the new identity:

  • active
  • disabled

Default: active


A Boolean value that indicates whether this is your master identity.

Default: false


  1. Create a new identity called test:

curl -X POST 
    -d '{"label": "test","status": "active","master": false}' 
    -H 'Content-type: application/json' 
    -H 'Authorization: username:api_key'

The output looks like this:

HTTP/1.1 201 Created
  Content-type: application/json

      "id": "<id>",
      "api_key": "<api_key>",
      "label": "<label>",
      "status": "<active|disabled>",
      "master": <boolean>,
      "created_at": <timestamp>,
      "updated_at": <timestamp>,
      "expires_at": <timestamp>

Output Fields

Property Type Description
id string An account identity. A 32-character alphanumeric hash.
api_key string The API key for this identity.
label string The label you applied to this identity.
status string Can be:
  • active
  • disabled
master boolean Indicates whether this is your master id or a client id.
created_at int Unix timestamp.
updated_at int Unix timestamp.
expires_at int Unix timestamp. Can be null.


Response code Description
Status 201 Created The identity was successfully created.
Status 409 Conflict

Occurs if you have already used that label.

  "error": "An Identity with the label \"<label>\" already exists"


  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. All POST and PUT requests require Content-type: application/json.

Resource information

Rate limit cost: 5

Requires authentication: Yes

Response formats: JSON, JSONP