Skip to content

DROP API or manual upload?

Both routes meet the Delete Act. Manual use of the DROP portal suits a broker with one or two lists, small batches and a person who reliably logs in each cycle. The API suits brokers who want downloads on a schedule, large files and webhooks. The files, statuses and deadlines are identical either way.

Last reviewed 22 November 2026

What is the same

CalPrivacy states that integration via API is not required. The portal and the API are two doors to the same process:

  • The same batch ZIP of Id,Hash files, and the same removals file.
  • The same response files with the header Id,Status and the same status codes 2 to 5.
  • The same limits: 10 files and 100 MB per upload, 100 files per batch.
  • The same row validation, with results by email, and rejected rows listed in the portal either way.
  • The same deadlines: at least every 45 days now and every 30 days from 1 January 2027. See DROP deadlines.

Neither route does the hard part for you. Standardizing and matching your records, deleting in every system and keeping evidence happen outside DROP whichever door you use.

Side by side

Manual (portal)API
SetupNone beyond the DROP accountIssue a key, build or buy a client, store the key securely
DownloadA person generates and downloads the ZIPScheduled GET /data/download, polling on 202
UploadA person uploads CSVs; amendments via the Amend buttonPOST /data/upload and /data/amend
NotificationsEmail to the account contactsEmail plus optional signed webhooks
Main riskSomeone is away and the date passesA rotated key or failed job nobody notices
EvidenceScreenshots and saved emails, unless you log it yourselfEvery request and response can be logged automatically
If it breaksAnother person logs inNotify CalPrivacy in writing and fall back to the portal

When manual fits

Manual use is a sound choice when most of these are true:

  • You select one or two lists, and later batches are small enough to handle in a spreadsheet or a short script.
  • At least two people know how to run a cycle, so holidays and sick days are covered.
  • You have no engineering time to spare for an integration, or no wish to hold an API key.
  • You keep your own record of each download date, upload and DROP response.

The cost of manual use grows with frequency. At 45 days it is around eight cycles a year; from 1 January 2027, at 30 days, it is at least twelve. Each needs someone to log in, download, process, upload, watch for the validation email and fix rejected rows. The first download for each list is the full list and is expected to be larger than later ones.

When the API fits

  • You want downloads to happen on a fixed day without anyone logging in.
  • Your matching already runs as a job, and the batch can feed straight into it.
  • You select several lists, or your first downloads are large.
  • You want an automatic record of every call and response for the audit.
  • You want webhooks to tell your systems when a download is ready or an upload has been validated.

The API brings its own chores. Keys do not expire, but issuing a new one deactivates the old, so a rotation in the portal silently breaks the job. Lists change only with a new key. A downloaded batch is not served again while it is open, so the job must store the ZIP before it does anything else. And if the connection fails through no fault of yours, the regulations ask you to notify CalPrivacy in writing and download manually. The details are in the DROP API guide.

Running both

Most brokers who use the API keep the portal route working too. Set the API up for routine cycles, and keep a written manual runbook with a named person for the day the key is rotated, an account issue causes a 403, or DROP is unavailable. Rejected-row details are only in the portal anyway, so someone will need portal access regardless.

A tool can also sit between the two. CalDrop Compliance accepts a ZIP you downloaded by hand, matches it in your browser and gives back ready-named Id,Status files to upload, or it runs the API cycle on a schedule on the Growth and Scale plans. Compare plans on pricing, or weigh building your own in build or buy.

Five questions to decide

  1. How many lists do you select, and how large was your first download?
  2. Who runs a cycle when the usual person is away, and do they know how?
  3. Can you keep an API key encrypted and notice within a day if it stops working?
  4. Will you be able to show an auditor the exact download time and every upload response for each batch?
  5. Does your process fit inside 30 days, including DROP's validation and a round of rejected rows?

If the answers to 2 and 5 make you uneasy, the route matters less than adding a second person and reminders. If 1 and 4 worry you, the API, or a tool that wraps it, is likely worth the setup.

Questions

Do I have to use the DROP API?

No. CalPrivacy says integration via API is not required. Downloading and uploading in the DROP portal meets the same obligations.

Are the files different between the API and the portal?

No. Both give the same batch ZIP of Id,Hash files and accept the same Id,Status response files, with the same limits of 10 files and 100 MB per upload.

Are the deadlines different for API users?

No. Every broker must download at least every 45 days, and every 30 days from 1 January 2027, whichever route it uses.

What happens if my API integration breaks?

Download and upload in the portal instead. If the failure is not your fault, the current regulations ask you to notify CalPrivacy in writing within 45 days of your last access. Deadlines keep running.

Can I switch between manual and API?

Yes. Both routes act on the same account and batches. Many brokers use the API for routine cycles and keep the portal as the fallback.

Sources

  1. CalPrivacy: DROP API operations
  2. CalPrivacy: DROP operations and API documentation
  3. CalPrivacy: Processing DROP requests
  4. CalPrivacy: DROP for data brokers
  5. DROP regulations, 11 CCR §§ 7600–7622 (PDF)

Written by the CalDrop Compliance team at Preptics LLC and last reviewed 22 November 2026. This guide explains the rules; it is not legal advice. CalDrop Compliance is an independent product of Preptics LLC. It is not affiliated with, endorsed by or operated by the State of California or the California Privacy Protection Agency (CalPrivacy).