then with archived=true appended to "purge" the database so that I could start over. I'm following the exact same protocol. I first deleted all records of the object and am attempting to delete the object but am receiving a 400 error with the following response:
endpoint to completely delete the object. You can then recreate a custom object with the same name if you want. Purge has been deprecated, I believe. The key is to make sure all instances of the object are deleted first. I'm not sure if this helps but just giving some background in case it might help. This seems to be a particular error. Let me know if you've tried that and are getting this same error on the initial delete endpoint. Might help to pinpoint what's going on and where.