2a:T706,

Hi Team,
I'm new here and currently working on implementing the user deletion API flow. I have a question and a point to raise regarding the API documentation.

Question:
We have six different projects within the same Amplitude account—three for production and three for development. When initiating a data deletion request via the API, is there a way to prevent the request from failing if the user ID does not exist in some of the projects?
In the documentation, I noticed the delete_from_org parameter, which, when set to true, deletes the user data across all projects in the organization. However, if the user ID doesn't exist in some projects (e.g., development projects when the user is only present in production), the API returns an error, and the request fails. Is there a recommended approach to handle such scenarios where we want to delete user data only from applicable projects, without the entire request failing due to missing user records in others?
I'm referring to the documentation here: Amplitude User Privacy API

Clarification:
Additionally, I observed that in the documentation, the parameters ignore_invalid_id, delete_from_org, and include_mapped_user_ids are indicated as boolean values. However, during implementation, I found that these parameters need to be passed as strings (e.g., "true" or "false"). When I used boolean values, the API call failed, but it succeeded when I used string representations.
I wanted to highlight this discrepancy for correction in the documentation.