Possible types of compliance events will include Tweet (or “status”) events and User events, for which there are multiple types described below.  

Please note:

  • Read more about User statuses here and our developer policy around deleted Tweets here.
  • Several User delete, protect and suspend events are not necessarily permanent and can toggle between states infinitely. These include: user_delete,user_undelete, user_protect, user_unprotect and user_suspend, user_unsuspend.
  • User_deletes are followed by status_deletes 30 days later only if the user has not selected to user_undelete their account. It is possible that a user_delete is reversed by the user and deletes for all of their tweets 30 days later do not occur.
  • User_suspend is an action that remains true unless the user is subject to an user_unsuspend event. These are not subject to any changes on a 30 day time period.

Refer to the ‘Recommended Action’ column to understand how to process each type of event in order to respect the privacy and intent of the end user. For examples of how these compliance events are represented in the JSON payload, please see the Compliance Data Objects page.

Original Message Type Object Permanent (Yes/No) Recommended Action
delete Status Yes Delete associated Tweet.
status_withheld Status Yes Suppress associated Tweet in specific countries listed in the status_withheld message.
user_delete User No Suppress or delete all Tweets by associated user.
user_undelete User No All Tweets by associated user may be displayed again and treated as public.
user_protect User No Suppress or delete all Tweets by associated user.
user_unprotect User No All Tweets by associated user may be displayed again and treated as public.
user_suspend User No Suppress or delete all Tweets by associated user.
user_unsuspend User No All Tweets by associated user may be displayed again and treated as public.
scrub_geo User Yes Delete all geodata provided by Twitter for all Tweets by the user prior to the specified Tweet in the scrub_geomessage. Note that subsequent Tweets by a user may contain geodata that may be used.
user_withheld User Yes Suppress Tweets by associated user in specific countries listed in the user_withheld message.

Payload examples

See the payload examples below for each compliance event described in the table above.

Status delete

  {
  "delete": {
    "status": {
      "id": 601430178305220600,
      "id_str": "601430178305220608",
      "user_id": 3198576760,
      "user_id_str": "3198576760"
    },
    "timestamp_ms": "1432228155593"
  }
}

Status withheld

  {
  "status_withheld": {
    "status": {
      "id": 601430178305220600,
      "id_str": "601430178305220608",
      "user_id": 3198576760,
      "user_id_str": "3198576760"
    },
    "withheld_in_countries": [
      "XY"
    ],
    "timestamp_ms": "1432228155593"
  }
}

Scrub geo

  {
  "scrub_geo": {
    "user_id": 519761961,
    "up_to_status_id": 411552403083628540,
    "up_to_status_id_str": "411552403083628544",
    "user_id_str": "519761961",
    "timestamp_ms": "1432228180345"
  }
}

User delete

  {
  "user_delete": {
    "id": 771136850,
    "timestamp_ms": "1432228153548"
  }
}

User undelete

  {
  "user_undelete": {
    "id": 796250066,
    "timestamp_ms": "1432228149062"
  }
}

User withheld

  {
  "user_withheld": {
    "user": {
      "id": 1375036644,
      "id_str": "1375036644"
    },
    "withheld_in_countries": [
      "XY"
    ],
    "timestampMs": "2014-08-27T23:49:41.839+00:00"
  }
}

User protect

  {
  "user_protect": {
    "id": 3182003550,
    "timestamp_ms": "1432228177137"
  }
}

User unprotect

  {
  "user_unprotect": {
    "id": 2911076065,
    "timestamp_ms": "1432228180113"
  }
}

User suspend

  {
  "user_suspend": {
    "id": 3120539094,
    "timestamp_ms": "1432228194217"
  }
}

User unsuspend

  {
  "user_unsuspend": {
    "id": 3293130873,
    "timestamp_ms": "1432228193828"
  }
}