Deleting Objects
Each object that allows deletion via the API will have a delete method in that object's namespace.
The delete method takes a single parameter which is the primary identifier for the object to be deleted. See Fetching Objects for more information about how to specify an object.
Delete will return null if the delete is successful. If the object did not exist to begin with, null is also returned.
Calling the delete method
Here is an example request calling the delete method
A JSON-RPC Request for calling the delete method
{ "method": "member.delete", "params": ["example_username"], "id": 1 }
The JSON-RPC Response
{ "result": null, "error": null, "id": 1 }
Deleting Member Objects
Member objects are a special case for delete. With other object types, you can delete the object and add back an different version of that object. Members are treated differently. When a member object is deleted, the username associated with that member is not released. Therefore, any subsequence member.create for that same username will fail with a duplicate object error.
Docs Navigation
- API Documentation Portal
- IO Docs Definition
- Mashery API Documentation
- Mashery 3.0 API Guide
- Mashery 2.0 API Guide
- OAuth Supporting Methods
- Examples
- JSON RPC
- Authentication
- API Objects
- Fetching Objects
- Query Language
- Creating Objects
- Updating Objects
- Validating Fields
- Deleting Objects
- Applications
- General Object Methods
- Members
- Packages
- Plans
- Package Keys
- Keys
- Developer Classes
- Services
- Roles
- Mashery 2.0 Reporting API Guide
- Event Trigger API
- Differences between Roles and Portal Access Groups
- Managing a Portal Access Group Using Mashery V2 or V3 API
- Mashery Reporting Event Post API Guide
- Tips and Tricks
- Your Portal
- API Traffic Manager
- I/O Docs WSDL requirements