If you have the latest version of apiman then it is possible to "retire" a service version and "unregister" an application version. This does not delete those versions, but it does remove them from the gateway, which means that clients will no longer be able to invoke them. As for deleting organizations, services, plans, etc... we're still working out the semantics of that. It's complicated because of the various references and relationships. For example, if an Organization has 5 services, and each of those services have a few dozen contracts, what do we do when the Organization owner deletes the organization? We would have to also retire all of that org's services, which would break all of the existing contracts. This is certainly what *should* happen - but we need to be able to do it in a way that notifies applications in other organizations that their service contracts have been broken. Same thing with plans - if a plan is deleted but is being used in one or more service, then deleting it is problematic. It would actually be super helpful if you could describe what you, as a user, would expect to happen in some of these scenarios! -Eric On 12/22/2014 6:03 AM, Rao Dingyuan wrote: