---
title: "After enabling Delete API  – Error:MXAccessDeniedOnOperationException"
description: "Ticket ID for reference https://support.leadsquared.com/a/tickets/77858 Issue After enabling delete API on an account, on triggering API gets the below error for customer [Status] => Error [ExceptionType] => MXAccessDeniedOnOperationException ..."
url: "https://supportb.kinsta.cloud/docs/after-enabling-delete-api-error-mxaccessdeniedonoperationexception/"
updated: "2020-07-13"
category: API
---

# After enabling Delete API  – Error:MXAccessDeniedOnOperationException

| **Ticket ID for reference**  [https://support.leadsquared.com/a/tickets/77858](https://support.leadsquared.com/a/tickets/77858) |
| --- |
| **Issue** After enabling delete API on an account, on triggering API gets the below error for customer *\[Status\] => Error \[ExceptionType\] => MXAccessDeniedOnOperationException \[ExceptionMessage\] => Delete is not enabled for you* |
| **Resolution** Customer had two LeadSquared accounts. 17858 and 10284. When customer raised request to enable Delete API, we enabled in 17858 since customer user id ([kapil.gupta@footprintseducation.in](mailto:kapil.gupta@footprintseducation.in)) is associated with that account. The access/secret key being used to call the delete API belongs to user: [franchise.crm@footprintseducation.in](mailto:franchise.crm@footprintseducation.in) who is part of 10284. This is the reason customer was getting following error and we were not: *\[Status\] => Error \[ExceptionType\] => MXAccessDeniedOnOperationException \[ExceptionMessage\] => Delete is not enabled for you * **RCA** noticed it and enabled the Delete API access for 10284 also. After that the error was gone. But now, you can still find the lead b641f0f9-2865-4bb9-a3b0-fa8b63980e8b ([test@test.in](mailto:test@test.in)) . But note that the lead is in 17858 and not in 10284. You tried to delete a lead of 17858 with credentials of 10284. The API gave “success” message which is incorrect. It should have given “Lead does not exist” message. We will fix that. |