Nope, I am using the :sis_user_id in my command, it was finding the correct records. As I said in my initial post, the call was returning a valid admin object paylod for the user with a workflow_statu...

Apparently, its just bugged out records. I added a new admin with the same role and was able to remove them with the API, so for some reason I have a bunch of old records that the API can't remove...

When I do a DELETE request against the /api/v1/accounts/:account_id/admins?role_id=XXXX REST API and pass the correct account_id and role_id, the API returns an Admin JSON as its supposed to, and ...

Is there a maximum number of Sub-Accounts that is supported in a specific account? I have an account with over 500 sub-accounts, largely due to some old logic for our automation, and i've noticed ...

Nope, I am using the :sis_user_id in my command, it was finding the correct records. As I said in my initial post, the call was returning a valid admin object paylod for the user with a workflow_statu...

Apparently, its just bugged out records. I added a new admin with the same role and was able to remove them with the API, so for some reason I have a bunch of old records that the API can't remove...

When I do a DELETE request against the /api/v1/accounts/:account_id/admins?role_id=XXXX REST API and pass the correct account_id and role_id, the API returns an Admin JSON as its supposed to, and ...

Is there a maximum number of Sub-Accounts that is supported in a specific account? I have an account with over 500 sub-accounts, largely due to some old logic for our automation, and i've noticed ...