Operations and API documentation
Prerequisites for API integration
If you elect to integrate via API, please also ensure you have the following:
| Requirement | Details |
|---|---|
API key | Generated after selecting your consumer deletion list(s) |
| HTTPS client | Ability to make GET and POST requests over TLS 1.2+ (for example, curl, PowerShell, or HTTP library) |
| CSV handling | Ability to read and write CSV files following the required naming convention |
| Secret storage | Secure storage for API key |
| Logging | Ability to log request timestamps and upload/download outcomes |
API base URL
| Environment | URL |
|---|---|
| Production | https://api.drop.privacy.ca.gov |
| Sandbox | https://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
- Sign in to your DROP account.
- For production integration, navigate to Home > Consumer Deletion Lists.
- Select the consumer deletion list(s) your business will process.
- Click Save.
- Open the API Key tab.
- 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 Unauthorizedindicates that an incorrect API key was entered. Correct the key or generate a new one and try again.403 Forbiddenindicates 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,Statuscolumns - 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.
| Method | Path | Description |
|---|---|---|
GET | /data/download | Request or download consumer deletion request data as a ZIP archive |
POST | /data/upload | Upload new status response files |
POST | /data/amend | Update 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:
| Code | Meaning | Action |
|---|---|---|
200 OK - ZIP | ZIP is ready and returned in the response | Download and process the ZIP |
200 OK - No data | No new consumer request data is available | No action needed. Try again later based on your processing schedule |
202 Accepted -Preparing | The request was received and the download is being prepared | Call GET /data/download again later |
401 Unauthorized | API key is missing or invalid | Fix or regenerate the API key and try again |
403 Forbidden | Broker is not eligible to download data | Resolve account, registration, payment, or access issue and try again |
403 Forbidden - No selected lists | Broker has not selected any list types | No identifier list preferences are enabled. Select at least one list and try again. |
404 Not Found | Endpoint URL is wrong or resource path does not exist | Correct the URL/path and retry |
429 Too Many Requests | Too many requests | Wait 30 seconds and retry |
500 Server Error | Temporary system error | Retry 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
| Code | Meaning | Action |
|---|---|---|
202 Accepted | At least one file was accepted and queued for validation | Review accepted and rejected (if any) file results |
400 Bad Request | Request is malformed or no files were accepted | Fix the request or rejected files and try again |
401 Unauthorized | API key is missing or invalid | Fix or regenerate the API key and try again |
403 Forbidden | Broker is not eligible to upload responses | Resolve account, registration, payment, or access issue and try again |
404 Not Found | Endpoint URL is wrong or resource path does not exist | Correct the URL/path and retry |
403 Forbidden - No selected lists | No upload expected as no records outstanding | Use GET /data/download to request or download a new ZIP file. |
429 Too Many Requests | Too many requests | Wait 30 seconds and retry |
500 Server Error | Temporary system error | Retry 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
| Rejection | Message |
|---|---|
| No CSV file provided | No CSV file was provided |
| Wrong file type | Only CSV files are accepted |
| Invalid header | Invalid CSV header. Expected: Id,Status |
| Duplicate file name | A file with this name was already uploaded for the current download. Use a unique suffix and try again |
| File unreadable | File could not be read as UTF-8 CSV |
Response format
| Field | Type | Description |
|---|---|---|
| message | string | Summary of the upload result |
| acceptedCount | integer | Number of files accepted for validation |
| rejectedCount | integer | Number of files rejected before validation |
| accepted | array | Files accepted for validation, each with file name and file size bytes |
| rejected | array | Files 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
| Scenario | Retry? | Notes |
|---|---|---|
429 Too Many Requests | Yes | Wait 30 seconds and try again |
500 Server Error | Yes | Retry later |
401 Unauthorized | No | Correct or regenerate the API key before trying again |
403 Forbidden | No | Resolve the account, registration, payment, or access issues, and select at least one list type before trying again |
404 Not Found | No | Fix the URL or path before trying again |
400 Bad Request | No | Fix the request, file, or CSV format before retrying |
409 Conflict | No | Complete the required action provided in the message before trying |
| Duplicate file name rejection | No | Use a unique optional suffix in the file name and upload again |
| Invalid CSV header rejection | No | Fix the header to Id,Status and upload again |
| Wrong file type rejection | No | Upload a CSV file |
| File unreadable rejection | No | Save the file as UTF-8 CSV and upload again |
Consumer deletion lists
| Code | Identifier | Type |
|---|---|---|
NDZ | First Name + Last Name + Date of Birth + ZIP | Composite hash |
Email | Email address | Single-field hash |
Phone | Phone number | Single-field hash |
MAID | Mobile advertising ID | Single-field hash |
NameVIN | First Name + Last Name + VIN | Composite hash |
CTVID | Connected TV identifier | Single-field hash |
Consumer data properties
| Property | Format | Details |
|---|---|---|
| Name | Separate First Name and Last Name fields | Names are collected, standardized, and hashed separately |
| Date of Birth | YYYYMMDD | Eight digits, four-digit year |
| ZIP Code | Up to 5 alphanumeric characters | Strip non-alphanumeric characters, remove leading zeros, and use the first five characters |
| String | Validated as a valid email address | |
| Phone | Last 10 digits only | Strip non-numeric characters, then keep the last 10 digits |
| MAID | 32 hexadecimal characters | Mobile Advertising ID |
| VIN | 17 alphanumeric characters | Vehicle Identification Number |
| CTVID | 8 to 32 alphanumeric characters | Unique 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
| Field | Description |
|---|---|
YYYYMMDD | Batch generation date |
DataBrokerId | Your short broker identifier, currently 4 digits. This ID is provided in the file name you download |
DataType | List type code: NDZ , Email , Phone , MAID , NameVIN , or CTVID. For removed identifiers, the file type is Removed |
OptionalSuffix | Optional. 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.
| Column | Description |
|---|---|
Id | Work item identifier |
Hash | SHA-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.
| Column | Description |
|---|---|
Id | Work item identifier |
Hash | SHA-256 Base64 hash |
List | List 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 headerId,Status.
Single-field lists (Email, Phone, MAID, CTVID)
| Column | Description |
|---|---|
Id | Work item identifier from the downloaded file |
Status | Numeric status code |
Example:
Id,Status
A7kP2xQ9Lm4R,2
bK8rT3nV6pZa,5
x92LmQ8Zp3Rt,4
Status codes
| Code | Label | Meaning |
|---|---|---|
| 2 | Exempted | Match found and personal information is exempt |
| 3 | Deleted | Match found and non-exempt personal information was deleted |
| 4 | Opted out | Multiple consumers are linked to the same identifier and all were opted out of sale or sharing |
| 5 | Not found | No 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
- Standardize each value using the rules for its identifier type, in the order listed.
- Hash the standardized value using SHA-256 with UTF-8 input encoding.
- 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.
- Apply Unicode normalization and remove control and format characters. DROP uses NFKC normalization.
- Convert to lowercase.
- 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.
- Replace accented Latin characters with plain ASCII equivalents where supported, such as å is a, ö is o, and ñ is n.
- 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 letter | Latin 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 letter | Latin 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 letter | Latin letter |
|---|---|
| ß | ss |
| æ | ae |
| œ | oe |
| ø | o |
| ð | d |
| þ | th |
| ł | l |
| đ | d |
| ħ | h |
| ŋ | n |
| ı | i |
| ij | ij |
| ŀ | 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.
| Input | Standardization | SHA-256 Base64 |
|---|---|---|
| Juan Pablo | juanpablo | 91hIbrbzNeqHs3o81O5yNrXUj7wDd2shvZ6THKi9qz8= |
| Martinez | martinez | 2wRPGbwBNxhShjRczx8GfS2c4cjvs4NJskeWloUNtp8= |
| María José | mariajose | 3VsywV/Fa+hXC9SFqmuszWhThL0Dyf6UelEDdsxJeKY= |
| O'Connor | oconnor | eg+/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.
| Input | Standardization | SHA-256 Base64 |
|---|---|---|
| July 4, 1776 | 17760704 | skXYXxBER6HQTZ3rXSZH1wVGLQ054mS5rbR/bwvzy4I= |
ZIP code standardization
- Remove leading and trailing whitespace.
- 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.
- Keep only letters and digits, then convert to lowercase.
- Remove leading zeros (0). If the value is all zeros, use 0.
- Use the first five characters, or all characters if fewer than five remain.
| Input | Standardization | SHA-256 Base64 |
|---|---|---|
91790-3771 | 91790 | 2FPZucR4x7U8KlM+SFAX4LPGhwNz/PIZUCSUdDh0o/s= |
M1B 1A1 | m1b1a | n8L9q8mVeT6Xt9/EeUNiTukGDrkbPJ3DvOEx14uElxk= |
00712345 | 71234 | aeNUYKh7Xw5sqpxSbSP9eOHsj6iXewbUyavv89DIuhQ= |
00300-9999 | 300 | mDvWFLta/s5as7YCP3EUfNe2vCMU+dJ690IlQcZVg4k= |
Email standardization
Remove whitespace and convert to lowercase. Do not remove dots, plus signs, or other characters.
| Input | Standardization | SHA-256 Base64 |
|---|---|---|
Anna.Smith@Domain.com | anna.smith@domain.com | KA18MT/ph6IHYjzT9zwETySDQyvSh87YuoSBpOQtkhE= |
danielle.johnson12@example.com | danielle.johnson12@example.com | mKDnDvwF2inxrKcK1hJN2TRkxPfL6kzNNTtU12eH8Bw= |
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.
| Input | Standardization | SHA-256 Base64 |
|---|---|---|
+1(415)555-9317 | 4155559317 | vGM7y5n+hBXRSEAklhHDPCbysyNgYTmXdMcagGUOY8E= |
+84(90)123 4567 | 4901234567 | ptzVkgbv9DonwvPCHmXmJ2SEOaolSh37z3ZzY/Gmm+U= |
+354(123)4567 | 3541234567 | Btrzydf5K6ALAKKXJGFHSx7u5bDzHC9WlVYtpq1n2rY= |
+1(212)555-0186 ext. 123 | 2125550186 | IEWV38qOhXizX6uXmPYydSfrglkBOIfpSou2bt0lqcc= |
VIN standardization
Keep only alphanumeric characters and convert to lowercase.
| Input | Standardization | SHA-256 Base64 |
|---|---|---|
1HGCM82633A004352 | 1hgcm82633a004352 | iNswy1m+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.
| Input | Standardization | SHA-256 Base64 |
|---|---|---|
a3f1c2d4-5678-90ab-cdef-1234567890ab | a3f1c2d4567890abcdef1234567890ab | 250KY6lOgzYUB3EHrkbDCE2kMEZQE69SF38muhoDudI= |
CTVID standardization
Keep only alphanumeric characters, then convert to lowercase.
| Input | Standardization | SHA-256 Base64 |
|---|---|---|
SmartTV_9F8E7D6C | smarttv9f8e7d6c | d9fxuTIrKksBXYDlaWsvQbcyUUfCbUx7v78gd+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
- Standardize and hash each field separately (SHA-256, UTF-8, Base64).
- Concatenate the four Base64 hashes in this order:
FirstName + LastName + DOB + ZIP. - Hash the concatenated string (SHA-256, UTF-8, Base64).
Example: Danielle Johnson, DOB July 4, 1985, ZIP 91790.
| Field | Standardized | SHA-256 Base64 |
|---|---|---|
| First Name | danielle | 5dUD1FgiKcTJq+JQ5JZUdlyIXrSbtJ338YYbt5/HNG4= |
| Last Name | johnson | K+TjOqPiH2/3rRRPj9WCKKHM47UDQLSAX/DGNIDuxIg= |
| DOB | 19850704 | IWi7qxOAbBJe0fNciDj76Eg84gmj40rB7aNMK/VnFOI= |
| ZIP | 91790 | 2FPZucR4x7U8KlM+SFAX4LPGhwNz/PIZUCSUdDh0o/s= |
Concatenated string: 5dUD1FgiKcTJq+JQ5JZUdlyIXrSbtJ338YYbt5/HNG4=K+TjOqPiH2/3rRRPj9WCKKHM47UDQLSAX/DGNIDuxIg=IWi7qxOAbBJe0fNciDj76Eg84gmj40rB7aNMK/VnFOI=2FPZucR4x7U8KlM+SFAX4LPGhwNz/PIZUCSUdDh0o/s=
Final hash: PQOfn1RffEKmqMmNAzDKKaoZCwxWbQZkQzPWmQo9REA=
NameVIN: Name + VIN
- Standardize and hash each field separately (SHA-256, UTF-8, Base64).
- Concatenate the three Base64 hashes in this order:
FirstName + LastName + VIN. - Hash the concatenated string (SHA-256, UTF-8, Base64).
Example: Eve Genesis, VIN, 1HGCM82633A004352.
| Field | Standardization | SHA-256 Base64 |
|---|---|---|
| First Name | eve | hSYq33RRi7twx8uUzWFZ2RZp5age3x7+vVQ+rb2p+is= |
| Last Name | genesis | ruutSnlvzC4V3ExgYbRe2bNz8mrfx5jKfS2MxYGCcY4= |
| VIN | 1hgcm82633a004352 | iNswy1m+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 name | Description | Webhook Event Type |
|---|---|---|
| Download Ready | Your batch containing your selected consumer deletion list(s) is ready for download | drp.list.download.ready |
| Upload Confirmation | Your upload has been received and is being processed | drp.upload.received |
| Upload Processed | Your upload has been processed and responses are available for review Review this notification for any rejected records | drp.upload.processed |
| Amendment Confirmation | Your amendment upload has been received and is being processed | drp.amendment.received |
| Amendment Upload Processed | Your amendment has been processed and responses are available for review Review this notification for any rejected records | drp.amendment.processed |
| Batch Complete | Your outstanding batch has been returned and is complete with no records outstanding | drp.batch.completed |
| API Key Issued | An API key has been issued for your account | (email only) |
| API Key Changed | A new API key has been issued; all previous keys have been deactivated | (email only) |
Webhook configuration
To enable webhook notifications:
- Go to Notification settings in your DROP account under Deletion request processing.
- Toggle Webhook to Active.
- Enter your HTTPS endpoint URL.
- 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:
| Header | Description |
|---|---|
| X-Webhook-Event-Id | Unique ID for the logical event |
| X-Webhook-Event-Type | Event type |
| X-Webhook-Delivery-Id | Unique ID for this delivery attempt |
| X-Webhook-Timestamp | UTC timestamp for the webhook event |
| X-Webhook-Version | Webhook version |
| X-Webhook-Signature | HMAC-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:
- Read the raw request body exactly as received
- Read X-Webhook-Timestamp
- Build the signing string: <timestamp>.<raw request body>
- Compute HMAC-SHA256 using the webhook signing secret
- Compare the hex digest to X-Webhook-Signature after removing the sha256= prefix
- 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.