Operations and API documentation

Prerequisites for API integration

If you elect to integrate via API, please also ensure you have the following:

RequirementDetails
API keyGenerated after selecting your consumer deletion list(s)
HTTPS clientAbility to make GET and POST requests over TLS 1.2+ (for example, curl, PowerShell, or HTTP library)
CSV handlingAbility to read and write CSV files following the required naming convention
Secret storageSecure storage for API key
LoggingAbility to log request timestamps and upload/download outcomes

API base URL

EnvironmentURL
Productionhttps://api.drop.privacy.ca.gov
Sandboxhttps://api.drop.privacy.ca.gov/sandbox

Authentication

All API requests require an API key passed in the X-API-KEY header:

X-API-KEY: your-api-key-here

Your API key is scoped to the consumer deletion list(s) you select. Only the selected list(s) will appear in the batch that you download.

API key security

  • Store keys securely using environment variables or secret management systems
  • Regenerate keys if compromised or if list selection changes

Obtain an API key

  1. Sign in to your DROP account.
  2. For production integration, navigate to Home > Consumer Deletion Lists.
  3. Select the consumer deletion list(s) your business will process.
  4. Click Save.
  5. Open the API Key tab.
  6. Click Get a new API key.

Your key is now ready to use. API keys do not expire. If your key is compromised, follow the instructions to generate a new one. Note that the API Key for production is distinct from the API Key for the DROP Sandbox.

Note: During sandbox testing, navigate to Sandbox Environment > Issue Sandbox API Key.

Verify connectivity

Send a request to confirm your API key works:

curl -X GET "https://api.drop.privacy.ca.gov/data/download" \
  -H "accept: */*" \
  -H "X-API-KEY: your-api-key-here" \
  -I

A 200 OK response confirms authentication.

  • 401 Unauthorized indicates that an incorrect API key was entered. Correct the key or generate a new one and try again.
  • 403 Forbidden indicates that registration, if applicable, and payment of required fees is incomplete. Confirm your account status and try again.

Confirming successful integration

A successful integration via API indicates you are able to:

  • Authenticate against the API
  • Download and extract a ZIP archive
  • Read CSV files and understand the schema
  • Produce a correctly named response CSV response with Id,Status columns
  • Upload the response and receive confirmation

Endpoints

The endpoints below are used for downloading and uploading via DROP, whether you elect to process manually or via API.

MethodPathDescription
GET/data/downloadRequest or download consumer deletion request data as a ZIP archive
POST/data/uploadUpload new status response files
POST/data/amendUpdate status code for records that have already been reported on through /data/upload

File encoding and formats

  • CSV encoding: UTF-8
  • Hash input encoding: UTF-8
  • Hash output format: Base64
  • Download format: ZIP archive containing CSV files
  • Upload format: Individual CSV files sent via multipart/form-data

Download (API)

GET /data/download

Requests the current ZIP archive. If the ZIP is ready, the response returns the ZIP file. If the ZIP is still being prepared, the response returns a JSON message and the data broker should call GET /data/download again later.

Request headers:

Base URL used in the examples below: https://api.drop.privacy.ca.gov

X-API-KEY: your-api-key-here
Accept: application/zip, application/json

Curl example:

 curl -X GET "https://api.drop.privacy.ca.gov/data/download" 
  -H "accept: application/zip, application/json" 
  -H "X-API-KEY: your-api-key-here" 
  --output download.zip

PowerShell example:

$apiKey = "your-api-key-here"
$url = "https://api.drop.privacy.ca.gov/data/download"
$headers = @{
    "X-API-KEY" = $apiKey
    "Accept" = "application/zip, application/json"
}
Invoke-WebRequest -Uri $url -Headers $headers -OutFile "download.zip"

Download response codes:

CodeMeaningAction
200 OK - ZIPZIP is ready and returned in the responseDownload and process the ZIP
200 OK - No dataNo new consumer request data is availableNo action needed. Try again later based on your processing schedule
202 Accepted -PreparingThe request was received and the download is being preparedCall GET /data/download again later
401 UnauthorizedAPI key is missing or invalidFix or regenerate the API key and try again
403 ForbiddenBroker is not eligible to download dataResolve account, registration, payment, or access issue and try again
403 Forbidden - No selected listsBroker has not selected any list typesNo identifier list preferences are enabled. Select at least one list and try again.
404 Not FoundEndpoint URL is wrong or resource path does not existCorrect the URL/path and retry
429 Too Many RequestsToo many requestsWait 30 seconds and retry
500 Server ErrorTemporary system errorRetry later

ZIP response:

HTTP/1.1 200 OK 
Content-Type: application/zip 
Content-Disposition: attachment; filename="20260312_4821.zip"

JSON response example:

{"message":"No identifier list preferences are enabled. Select at least one list and try again."} 

Upload (API)

There are two upload endpoints. Both accept the same multipart/form-data request. Only the purpose differs.

For both /data/upload and /data/amend a single upload request can have a maximum of 10 files and a total size of 100MB. You must wait for your current upload/amend request to finish record level validation before attempting your next request.

POST /data/upload

Use /upload to report status for records that have not yet been processed. Each batch is limited to 100 files total across all upload requests.

In the event you have rejected records, you must re-upload rejected records to the /data/upload endpoint with a new file name.

POST /data/amend

Use /amend to report status for records already submitted through /data/upload.

Note: This endpoint is not used for correcting rejected records. See Ongoing processing for additional requirements related to amending records in the event a change in status is detected.

Request format

Both endpoints use multipart/form-data with the field name files.

Request headers:

Base URL used in the examples below: https://api.drop.privacy.ca.gov

X-API-KEY: your-api-key-here
Content-Type: multipart/form-data
Accept: application/json

Curl example (new upload):

 curl -X POST "https://api.drop.privacy.ca.gov/data/upload" 
  -H "accept: application/json" 
  -H "X-API-KEY: your-api-key-here" 
  -F "files=@20260312_4821_Email.csv;type=text/csv"

Curl example (amend):

curl -X POST "https://api.drop.privacy.ca.gov/data/amend" 
  -H "accept: application/json" 
  -H "X-API-KEY: your-api-key-here" 
  -F "files=@20260312_4821_Email_amend1.csv;type=text/csv"

Upload and amend response codes

CodeMeaningAction
202 AcceptedAt least one file was accepted and queued for validationReview accepted and rejected (if any) file results
400 Bad RequestRequest is malformed or no files were acceptedFix the request or rejected files and try again
401 UnauthorizedAPI key is missing or invalidFix or regenerate the API key and try again
403 ForbiddenBroker is not eligible to upload responsesResolve account, registration, payment, or access issue and try again
404 Not FoundEndpoint URL is wrong or resource path does not existCorrect the URL/path and retry
403 Forbidden - No selected listsNo upload expected as no records outstandingUse GET /data/download to request or download a new ZIP file.
429 Too Many RequestsToo many requestsWait 30 seconds and retry
500 Server ErrorTemporary system errorRetry later

File and record level validation

Both endpoints return JSON showing which files were accepted for processing and which files were rejected.

Accepted files are queued for validation. Full row-level validation may continue after the response is returned.

File rejection messages

RejectionMessage
No CSV file providedNo CSV file was provided
Wrong file typeOnly CSV files are accepted
Invalid headerInvalid CSV header. Expected: Id,Status
Duplicate file nameA file with this name was already uploaded for the current download. Use a unique suffix and try again
File unreadableFile could not be read as UTF-8 CSV

Response format

FieldTypeDescription
messagestringSummary of the upload result
acceptedCountintegerNumber of files accepted for validation
rejectedCountintegerNumber of files rejected before validation
acceptedarrayFiles accepted for validation, each with file name and file size bytes
rejectedarrayFiles rejected before validation, each with file name and message

JSON responses:

Example response with accepted files:

{ 
  "message": "Upload received. Accepted files were queued for validation.", 
  "acceptedCount": 1, 
  "rejectedCount": 0, 
  "accepted": [ 
    { 
      "fileName": "20260312_4821_Email.csv", 
      "fileSizeBytes": 2849112 
    } 
  ], 
  "rejected": [] 
} 

Example response with accepted and rejected files:

{ 
  "message": "Upload received. Accepted files were queued for validation. Rejected files were not accepted.", 
  "acceptedCount": 1, 
  "rejectedCount": 1, 
  "accepted": [ 
    { 
      "fileName": "20260312_4821_Email.csv", 
      "fileSizeBytes": 2849112 
    } 
  ], 
  "rejected": [ 
    { 
      "fileName": "notes.txt", 
      "message": "Only CSV files are accepted." 
    } 
  ] 
} 

API error handling

Retry guidance

ScenarioRetry?Notes
429 Too Many RequestsYesWait 30 seconds and try again
500 Server ErrorYesRetry later
401 UnauthorizedNoCorrect or regenerate the API key before trying again
403 ForbiddenNoResolve the account, registration, payment, or access issues, and select at least one list type before trying again
404 Not FoundNoFix the URL or path before trying again
400 Bad RequestNoFix the request, file, or CSV format before retrying
409 ConflictNoComplete the required action provided in the message before trying
Duplicate file name rejectionNoUse a unique optional suffix in the file name and upload again
Invalid CSV header rejectionNoFix the header to Id,Status and upload again
Wrong file type rejection NoUpload a CSV file
File unreadable rejectionNoSave the file as UTF-8 CSV and upload again

Consumer deletion lists

CodeIdentifierType
NDZFirst Name + Last Name + Date of Birth + ZIPComposite hash
EmailEmail addressSingle-field hash
PhonePhone numberSingle-field hash
MAIDMobile advertising IDSingle-field hash
NameVINFirst Name + Last Name + VINComposite hash
CTVIDConnected TV identifierSingle-field hash

Consumer data properties

PropertyFormatDetails
NameSeparate First Name and Last Name fieldsNames are collected, standardized, and hashed separately
Date of BirthYYYYMMDDEight digits, four-digit year
ZIP CodeUp to 5 alphanumeric charactersStrip non-alphanumeric characters, remove leading zeros, and use the first five characters
EmailStringValidated as a valid email address
PhoneLast 10 digits onlyStrip non-numeric characters, then keep the last 10 digits
MAID32 hexadecimal charactersMobile Advertising ID
VIN17 alphanumeric charactersVehicle Identification Number
CTVID8 to 32 alphanumeric charactersUnique device identifier for smart TVs, streaming players, and gaming consoles

File naming convention (Downloads and Uploads)

Downloaded CSV files follow a standard naming convention:

<YYYYMMDD>_<DataBrokerId>_<DataType>.csv

Response CSV files should follow an identical naming convention.

If you upload multiple response files for the same downloaded list, add a suffix to the file name using an underscore followed by up to 10 alphanumeric characters.

<YYYYMMDD>_<DataBrokerId>_<DataType>[_<OptionalSuffix>].csv 

FieldDescription
YYYYMMDDBatch generation date
DataBrokerIdYour short broker identifier, currently 4 digits. This ID is provided in the file name you download
DataTypeList type code: NDZ , Email , Phone , MAID , NameVIN , or CTVID. For removed identifiers, the file type is Removed
OptionalSuffixOptional. Up to 10 alphanumeric characters to differentiate uploads

Note: DROP will not accept duplicate file names. If you need to upload the same file twice to /data/upload or /data/amend add a unique suffix before you upload the file again.

Amend file naming

Follow the same file naming convention for /data/amend as /data/upload. However, you may also combine all records across the same list type that need to be amended into one file. For example, if you need to amend the records of phone hashes across several batches, you may upload them all within one file to /data/amend with the file name YYYYMMDD_DataBrokerId_Phone.csv where the date is a date that makes the most sense for your own record keeping.

Correct example file names:

20260312_4821_NDZ.csv
20260312_4821_Email.csv
20260312_4821_NameVIN.csv
20260312_4821_Email_part01.csv

Incorrect example file names:

202603012_4821_email.csv (the e in email should be capitalized) 
202603012_4821_Email1.csv (the suffix is not separated with an underscore)
202603012_4821_Email_1234567890A.csv (the suffix is greater than 10 characters)

Consumer deletion list file schema

Deletion list files use the same schema. The list type determines how the Hash value was generated.

Every row in the CSV includes an Id column that identifies a single work item. The corresponding Hash column contains the hashed identifier you will compare against your own records.

ColumnDescription
IdWork item identifier
HashSHA-256 Base64 hash

Work item Ids:

"Work item Ids" are case-sensitive, and contain 12 alphanumeric characters (Base 62). Work item Ids are permanently associated with a single work item and uniquely identifies a specific consumer-identifier pair.

For example, if two consumers enter the same phone number into their DROP requests, each phone number will be assigned a different work item Id.

Reminder: consumers may edit their DROP requests to add or remove identifiers. As a result, a work item Id may appear in a "removed" CSV and later reappear in a subsequent batch's deletion list. If you receive a previously processed work item Id again, you must still report on that identifier through the /data/upload endpoint so the batch can be completed successfully.

List hashing:

For Email, Phone, MAID, and CTVID lists, the Hash value is generated from a single standardized identifier.

For NDZ and NameVIN lists, the Hash value is the final hash generated through composite hashing.

Find more information in the Hashing and standardization section.

Note: When two DROP requests share an identical identifier, they will have the same hashed identifier but unique work item Ids. So, for example, if two consumers each input a shared landline into their request, the hashed identifier will be the same, but the work item Id will be unique per consumer.

Example:

Id,Hash
A7kP2xQ9Lm4R,KA18MT/ph6IHYjzT9zwETySDQyvSh87YuoSBpOQtkhE=

Removed identifiers file schema

If previously delivered identifiers have been removed, for example as a result of a cancellation, your batch will include a separate “Removed” CSV file. Data brokers are not required to respond with status for removed identifiers.

ColumnDescription
IdWork item identifier
HashSHA-256 Base64 hash
ListList type code: NDZ, Email, phone, MAID, NameVin, or CTVID

Example:

Id,Hash,List A7kP2xQ9Lm4R,KA18MT/ph6IHYjzT9zwETySDQyvSh87YuoSBpOQtkhE=,Email

Upload file schema (for both Upload and Amend endpoints)

When you upload via DROP, your response file must include that same work item identifier in the Id column alongside the status code you assign based on the outcome of your matching, whether for a first time upload or an amendment.

Refer to the File naming convention section for how to label your uploads.

Your response file must use the header Id,Status.

Single-field lists (Email, Phone, MAID, CTVID)

ColumnDescription
IdWork item identifier from the downloaded file
StatusNumeric status code

Example:

Id,Status
 A7kP2xQ9Lm4R,2 
 bK8rT3nV6pZa,5 
 x92LmQ8Zp3Rt,4

Status codes

Code LabelMeaning
2ExemptedMatch found and personal information is exempt
3DeletedMatch found and non-exempt personal information was deleted
4Opted outMultiple consumers are linked to the same identifier and all were opted out of sale or sharing
5Not foundNo match found after completing the matching process

For more information on the legal requirements based on match outcomes, see Civil Code section 1798.99.80 et seq. and CCR, title 11, section 7600 et seq.

Hashing and standardization

Use the rules below to standardize identifiers before hashing them for DROP. If you already have hashes generated using these exact rules, do not hash them again.

General rules

  1. Standardize each value using the rules for its identifier type, in the order listed.
  2. Hash the standardized value using SHA-256 with UTF-8 input encoding.
  3. Encode the hash using standard Base64, keeping uppercase and lowercase letters, +, /, and the ending =.

Tip: A SHA-256 hash in Base64 is typically 44 characters long and ends with =.

Name standardization

Standardize First Name and Last Name separately. Treat compound names as a single value. For example, Juan Pablo is juanpablo.

  1. Apply Unicode normalization and remove control and format characters. DROP uses NFKC normalization.
  2. Convert to lowercase.
  3. Replace supported Greek, Cyrillic, and special Latin characters using the DROP Transliteration Mapping below. Other writing systems, including Chinese, Japanese, Korean, Arabic, and Hebrew, are not transliterated.
  4. Replace accented Latin characters with plain ASCII equivalents where supported, such as å is a, ö is o, and ñ is n.
  5. Keep only Unicode letters and decimal digits. Remove spaces, hyphens, apostrophes, punctuation, symbols, and other characters.

DROP transliteration mapping:

Use these mappings exactly. Other transliteration methods may produce different hashes.

Greek

Greek letterLatin letter
αa
βv
γg
δd
εe
ζz
ηi
θth
ιi
κk
λl
μm
νn
ξx
οo
πp
ρr
σs
ςs
τt
υy
φf
χch
ψps
ωo
άa
έe
ίi
ήi
ύy
όo
ώo
ϊi
ΐi
ϋy
ΰy

Cyrillic

Cyrillic letterLatin letter
аa
бb
вv
гg
дd
еe
ёyo
жzh
зz
иi
йy
кk
лl
мm
нn
оo
пp
рr
сs
тt
уu
фf
хkh
цts
чch
шsh
щshch
ъ[removed]*
ыy
ь[removed]*
эe
юyu
яya
єe
іi
їi
ґg
ўu
ѐe
ђdj
ѓgj
ѕdz
јj
љlj
њnj
ћc
ќkj
ѝi
џdzh
ғgh
ҕgh
җzh
ҙz
қq
ҝg
ҟq
ҡq
ңng
ҥng
ҧp
ҩh
ҫs
ҭt
үu
ұu
ҳh
ҵts
ҷj
ҹch
һh
ҽch
ҿch
ӂzh
ӄk
ӆl
ӈng
ӊng
ӌch
ӎm
ӑa
ӓa
ӕae
ӗe
әa
ӛa
ӝzh
ӟz
ӡdz
ӣi
ӥi
ӧo
өo
ӫo
ӭe
ӯu
ӱu
ӳu
ӵch
ӷgh
ӹy
ӻgh
ӽkh
ӿkh
ԥp
ԧsh
ԩng
ԫdzzh
ԭdch
ԯl
*[removed] means replace the character with an empty string.

Special Latin

Special Latin letterLatin letter
ßss
æae
œoe
øo
ðd
þth
łl
đd
ħh
ŋn
ıi
ijij
ŀl
ĸq
ŧt
ƒf
ƙk
ƴy
ǝe
ǥg
ǿo
ɓb
ɔo
ɖd
ɗd
əa
ɛe
ɨi
ɲn
ʉu
ʊu
ʋv

Characters not included in this mapping are retained if they qualify as Unicode letters or decimal digits.

InputStandardizationSHA-256 Base64
Juan Pablojuanpablo91hIbrbzNeqHs3o81O5yNrXUj7wDd2shvZ6THKi9qz8=
Martinezmartinez2wRPGbwBNxhShjRczx8GfS2c4cjvs4NJskeWloUNtp8=
María José mariajose3VsywV/Fa+hXC9SFqmuszWhThL0Dyf6UelEDdsxJeKY=
O'Connoroconnoreg+/30DL65dCm9uI9RLOzSfw1Et+V5hqtXhCO7YZNqw=
דודדודm4LFnWfqjtywvdjHlgqUPu5+lb3ol9jttbjwG591/JE=
张张9WoEn8wj8ev84f3WTLJPQFW8UZrPLpEK451DCDoc7PY=

Date of birth standardization

Convert to YYYYMMDD using a four-digit year, two-digit month, and two-digit day. Do not include separators.

InputStandardizationSHA-256 Base64
July 4, 177617760704skXYXxBER6HQTZ3rXSZH1wVGLQ054mS5rbR/bwvzy4I=

ZIP code standardization

  1. Remove leading and trailing whitespace.
  2. If the entire value matches ZIP+4 format (five digits, a hyphen or plus sign, and four digits), remove the separator and last four digits.
  3. Keep only letters and digits, then convert to lowercase.
  4. Remove leading zeros (0). If the value is all zeros, use 0.
  5. Use the first five characters, or all characters if fewer than five remain.
InputStandardizationSHA-256 Base64
91790-3771917902FPZucR4x7U8KlM+SFAX4LPGhwNz/PIZUCSUdDh0o/s=
M1B 1A1m1b1an8L9q8mVeT6Xt9/EeUNiTukGDrkbPJ3DvOEx14uElxk=
0071234571234aeNUYKh7Xw5sqpxSbSP9eOHsj6iXewbUyavv89DIuhQ=
00300-9999300mDvWFLta/s5as7YCP3EUfNe2vCMU+dJ690IlQcZVg4k=

Email standardization

Remove whitespace and convert to lowercase. Do not remove dots, plus signs, or other characters.

InputStandardizationSHA-256 Base64
Anna.Smith@Domain.comanna.smith@domain.comKA18MT/ph6IHYjzT9zwETySDQyvSh87YuoSBpOQtkhE=
danielle.johnson12@example.comdanielle.johnson12@example.commKDnDvwF2inxrKcK1hJN2TRkxPfL6kzNNTtU12eH8Bw=

Phone standardization

  • Remove any phone extension, including its digits.
  • Remove all non-digit characters.
  • Use the last 10 digits, or all digits if fewer than 10 remain.
InputStandardizationSHA-256 Base64
+1(415)555-93174155559317vGM7y5n+hBXRSEAklhHDPCbysyNgYTmXdMcagGUOY8E=
+84(90)123 45674901234567ptzVkgbv9DonwvPCHmXmJ2SEOaolSh37z3ZzY/Gmm+U=
+354(123)45673541234567Btrzydf5K6ALAKKXJGFHSx7u5bDzHC9WlVYtpq1n2rY=
+1(212)555-0186 ext. 123 2125550186 IEWV38qOhXizX6uXmPYydSfrglkBOIfpSou2bt0lqcc=

VIN standardization

Keep only alphanumeric characters and convert to lowercase.

InputStandardizationSHA-256 Base64
1HGCM82633A0043521hgcm82633a004352iNswy1m+0VSt8jAfFrvaiQ1R/0HAbgSwNGkwqo6QBss=
7F01C123456 7f01c123456 iB4tPoGDMN2UMZSKr42kfXfbdN3uycsiuw4sgMLesNHs=

MAID standardization

Keep only hexadecimal characters ( 0–9 , A-F, a–f ), then convert to lowercase. The standardized value must be 32 characters.

InputStandardizationSHA-256 Base64
a3f1c2d4-5678-90ab-cdef-1234567890aba3f1c2d4567890abcdef1234567890ab250KY6lOgzYUB3EHrkbDCE2kMEZQE69SF38muhoDudI=

CTVID standardization

Keep only alphanumeric characters, then convert to lowercase.

InputStandardizationSHA-256 Base64
SmartTV_9F8E7D6Csmarttv9f8e7d6cd9fxuTIrKksBXYDlaWsvQbcyUUfCbUx7v78gd+KP+tc=

Composite hashing

The NDZ and NameVIN list types use composite hashing. This means each field is standardized and hashed first, then the resulting Base64 hashes are concatenated and hashed again.

NDZ: Name + Date of Birth + ZIP

  1. Standardize and hash each field separately (SHA-256, UTF-8, Base64).
  2. Concatenate the four Base64 hashes in this order: FirstName + LastName + DOB + ZIP.
  3. Hash the concatenated string (SHA-256, UTF-8, Base64).

Example: Danielle Johnson, DOB July 4, 1985, ZIP 91790.

FieldStandardizedSHA-256 Base64
First Namedanielle5dUD1FgiKcTJq+JQ5JZUdlyIXrSbtJ338YYbt5/HNG4=
Last NamejohnsonK+TjOqPiH2/3rRRPj9WCKKHM47UDQLSAX/DGNIDuxIg=
DOB19850704IWi7qxOAbBJe0fNciDj76Eg84gmj40rB7aNMK/VnFOI=
ZIP917902FPZucR4x7U8KlM+SFAX4LPGhwNz/PIZUCSUdDh0o/s=

Concatenated string: 5dUD1FgiKcTJq+JQ5JZUdlyIXrSbtJ338YYbt5/HNG4=K+TjOqPiH2/3rRRPj9WCKKHM47UDQLSAX/DGNIDuxIg=IWi7qxOAbBJe0fNciDj76Eg84gmj40rB7aNMK/VnFOI=2FPZucR4x7U8KlM+SFAX4LPGhwNz/PIZUCSUdDh0o/s=

Final hash: PQOfn1RffEKmqMmNAzDKKaoZCwxWbQZkQzPWmQo9REA=

NameVIN: Name + VIN

  1. Standardize and hash each field separately (SHA-256, UTF-8, Base64).
  2. Concatenate the three Base64 hashes in this order: FirstName + LastName + VIN.
  3. Hash the concatenated string (SHA-256, UTF-8, Base64).

Example: Eve Genesis, VIN, 1HGCM82633A004352.

FieldStandardizationSHA-256 Base64
First NameevehSYq33RRi7twx8uUzWFZ2RZp5age3x7+vVQ+rb2p+is=
Last NamegenesisruutSnlvzC4V3ExgYbRe2bNz8mrfx5jKfS2MxYGCcY4=
VIN1hgcm82633a004352iNswy1m+0VSt8jAfFrvaiQ1R/0HAbgSwNGkwqo6QBss=

Concatenated string: hSYq33RRi7twx8uUzWFZ2RZp5age3x7+vVQ+rb2p+is=ruutSnlvzC4V3ExgYbRe2bNz8mrfx5jKfS2MxYGCcY4=iNswy1m+0VSt8jAfFrvaiQ1R/0HAbgSwNGkwqo6QBss=
Final hash: rtnDuXIe63jXYQQXW5r07GJ7lSsrib8+46QuKFwkOmk=

Notifications

DROP sends notifications to data brokers based on system activity for the events listed below. The notifications below are sent via email to primary and secondary email addresses on your DROP account. These emails are sent from DoNotReply@privacy.ca.gov.

Optionally, you may enable webhooks for these notifications.

Ensure contact information for primary and secondary contacts on your account is up to date. Review notifications carefully to ensure any issues detected during processing are addressed in a timely manner.

Events

Event nameDescriptionWebhook Event Type
Download ReadyYour batch containing your selected consumer deletion list(s) is ready for downloaddrp.list.download.ready
Upload ConfirmationYour upload has been received and is being processed drp.upload.received
Upload ProcessedYour upload has been processed and responses are available for review

Review this notification for any rejected records
drp.upload.processed
Amendment ConfirmationYour amendment upload has been received and is being processeddrp.amendment.received
Amendment Upload ProcessedYour amendment has been processed and responses are available for review

Review this notification for any rejected records
drp.amendment.processed
Batch CompleteYour outstanding batch has been returned and is complete with no records outstanding drp.batch.completed
API Key IssuedAn API key has been issued for your account(email only)
API Key ChangedA new API key has been issued; all previous keys have been deactivated(email only)

Webhook configuration

To enable webhook notifications:

  1. Go to Notification settings in your DROP account under Deletion request processing.
  2. Toggle Webhook to Active.
  3. Enter your HTTPS endpoint URL.
  4. Save changes.

Signing secret:

When you enable webhooks, a signing secret is generated and shown in the portal. Store this secret securely in your webhook receiver configuration. It is used to verify that incoming webhook requests are sent by DROP. Rotate the secret as needed for security.

HTTP headers

Each webhook request includes:

HeaderDescription
X-Webhook-Event-IdUnique ID for the logical event
X-Webhook-Event-TypeEvent type
X-Webhook-Delivery-IdUnique ID for this delivery attempt
X-Webhook-TimestampUTC timestamp for the webhook event
X-Webhook-VersionWebhook version
X-Webhook-SignatureHMAC-SHA256 signature

Webhook body

Each webhook request includes a JSON body.

{ 
 "message": message text, 
} 

Example:

POST https://example.com/drop/webhook 
Content-Type: application/json 
X-Webhook-Event-Id: 00000000-0000-0000-0000-000000000000 
X-Webhook-Event-Type: download.ready 
X-Webhook-Delivery-Id: 11111111-1111-1111-1111-111111111111 
X-Webhook-Timestamp: 2026-07-02T18:30:00.0000000Z 
X-Webhook-Version: 1.0 
X-Webhook-Signature: sha256=abc123... 
 
{ 
 "message": "download ready" 
} 

Secret verification

DROP signs each webhook using the data broker’s webhook signing secret.

To verify:

  1. Read the raw request body exactly as received
  2. Read X-Webhook-Timestamp
  3. Build the signing string: <timestamp>.<raw request body>
  4. Compute HMAC-SHA256 using the webhook signing secret
  5. Compare the hex digest to X-Webhook-Signature after removing the sha256= prefix
  6. Reject the request if the signature is invalid

Example logic:

const expected = hmacSha256Hex(secret, `${timestamp}.${rawBody}`); 

const received = signatureHeader.replace("sha256=", ""); 

 

if (constantTimeEqual(expected, received)) { 

  // valid DROP webhook 

} else { 

  // reject 

} 

Recommended: reject webhook requests with timestamps older than five minutes to prevent out of date webhook requests.

Expected response:

Return any 2xx status when the webhook is received successfully.
Preferred response: HTTP/1.1 204 No Content
DROP treats non-2xx responses as failed delivery and may retry.