API operations

Request 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:

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"

Response codes:

ZIP response:

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

JSON responses:

{"message":"Complete the current batch or contact DROP support if a re-download is needed."} 

ZIP contents:

The ZIP contains one CSV per selected list type. If a selected list has no new records, the CSV contains only the header row. If any previously delivered identifiers were removed, the ZIP also includes one Removed CSV file.

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

Upload new status responses.

Upload a correction or update to responses submitted previously.

Request format

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

Request headers:

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

Curl example (new):

 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.csv;type=text/csv"

Response format

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.

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." 
    } 
  ] 
} 

Common rejection messages