CCPA Deletion

You can use the CCPA Deletion API in order to comply with California Consumer Privacy Act (CCPA) deletion requests through Attentive. For more information, you can review Attentive’s FAQs for CCPA or the Important Notice Regarding the CCPA of 2018.

Note: Legacy APIs and the APIs outlined in the Attentive API section need separate tokens. Contact legacyapi@attentivemobile.com for a legacy API token.

URL

POST https://tactical-client-api.attentivemobile.com/privacy/delete-request

Headers

Header name Description Value Required
Authorization You must provide an access token. Contact legacyapi@attentivemobile.com for this token. Bearer <token> Required
Content-type The format of returned data. application/json Required

Parameters

Parameter Description Example Type Required Notes
subjectPhone Phone number of the user. 555-555-5555 string Required* *Only required if subjectEmail is not provided.
subjectEmail Email address of the user. test@gmail.com string Required* *Only required if subjectPhone is not provided.
requestMsg An optional message for an audit trail. The subscriber requested to be removed. string Optional

Sample JSON request

curl 'https://tactical-client-api.attentivemobile.com/privacy/delete-request' \
  -X POST \
  -H 'Authorization: Bearer XXXXX' \
  -H "Content-Type: application/json" \
  -d '{"subjectPhone": "555-555-5555", "subjectEmail": "test@gmail.com", "requestMsg":"The subscriber requested to be removed"}'

Sample JSON response

{
  "id":59,
  "affiliateUserId":268
  "processed":false,
  "type":"DELETE",
  "subjectphone":"+5555555555",
  "requestMsg":"The subscriber requested to be removed",
  "requestDateTime":"2020-09-02T17:44:23.875+0000"
}

Status codes

The following table lists the returned HTTP status codes.

Code Description Notes
202 Accepted Request accepted.
400 Bad request Data is improperly formatted.
401 Authorization error API key is incorrect.
500 Attentive server-side error n/a