To learn more, see the sources I considered: [[1] DELETE /v2/schema/{proj_id}/{env_id}/resources/{resource_id}/roles/{role_id}/permissions](https://api.permit.io/v2/redoc#tag/Resource-Roles/operation/remove_permissions_from_resource_role)

this is the API

<https://api.permit.io/v2/schema/{proj_id}/{env_id}/roles/{role_id}/permissions>

resource key is in the body

You're absolutely right, and I apologize for the confusion in my previous response. You're using the correct endpoint for removing permissions from roles (not resource roles) . The endpoint you're using:

DELETE /v2/schema/{proj_id}/{env_id}/roles/{role_id}/permissions

is the correct one for removing permissions from roles, where the resource key is specified in the request body. Given that you're experiencing issues with the ADD permissions API failing after successfully removing permissions, especially when handling 75-100 permissions per role with minimal delay between calls, this could be related to: 1. ​*Rate limiting or throttling*​ on the API side 2. ​*Race conditions*​ when making rapid sequential calls 3. ​*Potential timing issues*​ with permission propagation To help our engineers investigate this issue properly, could you please provide: 1. Which Workspace / Project / Env you are using 2. What calls you are performing (as SDK code or CURL) - including the exact body payloads 3. Which PDP version you are running 4. Relevant logs from your PDP Additionally, could you share: • The exact error message or response you're receiving from the ADD permissions API • Whether this happens consistently or intermittently • The approximate delay you're using between the REMOVE and ADD calls This information will help the team identify what changed and resolve the iss

Feel free to tag me with additional questions. I also appreciate feedback, it helps me improve. 👍 button 👎 button

The issue you're experiencing with permissions not appearing after the ADD API call, despite no error messages, is likely related to ​*data synchronization timing*​ between the Permit API and your PDP. When you make rapid API calls (200ms apart) that modify permissions, there can be a delay before those changes propagate to the PDP. This is a known consideration in distributed authorization systems (1) . *Recommended Solution: Use "Send Consistent Updates" (Read-Your-Own-Writes) * Permit.io offers a feature called ​*Send Consistent Updates*​ that ensures data changes are immediately available for permission checks by routing requests through the PDP and waiting for synchronization before responding . To enable this in your Node.js code:

const permit = new Permit({
  token: "<your-api-key>",
  pdp: "<http://localhost:7766>",
  proxyFactsViaPdp: true
}) ;

With

proxyFactsViaPdp

enabled, API calls wait until data is fully synced to the PDP before returning, ensuring permission checks work immediately after . ​*Important Notes:*​ • This feature requires ​*PDP version 0.5.1 or above*​ • It increases API latency but provides faster sync times compared to direct Permit API calls • It works best when PDPs are deployed as Centralized PDPs or Sidecars to your application ​*Alternative Approach:*​ If you cannot use the above feature, consider increasing the delay between REMOVE and ADD operations to allow for propagation time, or implement a retry mechanism that verifies permissions were added before proceeding. To help our engineers investigate further, please also provide: 1. Which PDP version you are running 2. Relevant logs from your PDP showing the timing of these operations 3. The exact

fetch()

code you're using for both the REMOVE and ADD calls

To learn more, see the sources I considered: [[1] Send Consistent Updates (Read-Your-Own-Writes)](https://docs.permit.io/how-to/manage-data/local-facts-uploader)