---
title: "Data erasure using the API"
date: "2024-02-14T06:18:38+00:00"
summary: "Efficiently manage customer data with our API-based data erasure process. Learn about request limits, SLAs, and weekly processing caps to ensure compliance and streamline your data management workflow."
image:
type: "page"
url: "/customer-data-platform/data-erasure-using-api"
id: "8892da7f-363d-44c2-b9c4-331d0ba132b0"
---

Data erasure through the API consist of the following request call:

*   [Using the data erasure API](/customer-data-platform/data-erasure-requests/data-erasure-through-api/using-data-erasure-api)
    
*   [Payload and response code](/customer-data-platform/data-erasure-requests/data-erasure-through-api/payload-response-code)
    

Important points
----------------

*   **API limit**: The API can accept up to 200 records per batch. This is the same limit that you get when submitting requests through the Data Erasure Hub screen.
    
*   **SLA for request**: Data erasure batches are chosen in reverse-date order so that the requests closer to the 30-day SLA are chosen first. When you enter data in the Data Erasure Hub screen through UI or API, CDP sets the expiry date on the records as the _current date + 30 days_. CDP selects the records for erasure based on the expiry date in the reverse chronological order, that is, the oldest records are chosen first. The date entered in **Date of Customer Request** through the UI is not used to prioritize the requests.
    
*   **Requests per week**: CDP has a limit of 9990 data erasure requests that can be processed per week.