Delete a Usage Consumption Object
delete
{apiRoot}/queryUsageConsumption/{id}
Deletes the usage consumption object specified by the ID.
Request
Path Parameters
-
id(required): string
The ID of the usage consumption object.
There's no request body for this operation.
Back to TopResponse
Supported Media Types
- application/json;charset=utf-8
204 Response
The usage consumption object was deleted successfully.
400 Response
The request isn't valid.
Root Schema : Error
Type:
objectAn error.
Show Source
-
@baseType: string
When sub-classing, this defines the super class.
-
@schemaLocation: string
(uri)
The URI to a JSON-schema file that defines additional attributes and relationships.
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
The error code, which contains application-relevant detail.
-
message: string
Additional details about the error as well as possible corrective actions.
-
reason(required): string
The reason for the error that can be shown to a client user.
-
referenceError: string
(uri)
The URI to the documentation describing the error.
-
status: string
The HTTP error code extension.
401 Response
The client doesn't have the correct privileges.
Root Schema : Error
Type:
objectAn error.
Show Source
-
@baseType: string
When sub-classing, this defines the super class.
-
@schemaLocation: string
(uri)
The URI to a JSON-schema file that defines additional attributes and relationships.
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
The error code, which contains application-relevant detail.
-
message: string
Additional details about the error as well as possible corrective actions.
-
reason(required): string
The reason for the error that can be shown to a client user.
-
referenceError: string
(uri)
The URI to the documentation describing the error.
-
status: string
The HTTP error code extension.
403 Response
The request wasn't authorized.
Root Schema : Error
Type:
objectAn error.
Show Source
-
@baseType: string
When sub-classing, this defines the super class.
-
@schemaLocation: string
(uri)
The URI to a JSON-schema file that defines additional attributes and relationships.
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
The error code, which contains application-relevant detail.
-
message: string
Additional details about the error as well as possible corrective actions.
-
reason(required): string
The reason for the error that can be shown to a client user.
-
referenceError: string
(uri)
The URI to the documentation describing the error.
-
status: string
The HTTP error code extension.
404 Response
The server couldn't find the requested object.
Root Schema : Error
Type:
objectAn error.
Show Source
-
@baseType: string
When sub-classing, this defines the super class.
-
@schemaLocation: string
(uri)
The URI to a JSON-schema file that defines additional attributes and relationships.
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
The error code, which contains application-relevant detail.
-
message: string
Additional details about the error as well as possible corrective actions.
-
reason(required): string
The reason for the error that can be shown to a client user.
-
referenceError: string
(uri)
The URI to the documentation describing the error.
-
status: string
The HTTP error code extension.
405 Response
This method isn't supported for the requested resource.
Root Schema : Error
Type:
objectAn error.
Show Source
-
@baseType: string
When sub-classing, this defines the super class.
-
@schemaLocation: string
(uri)
The URI to a JSON-schema file that defines additional attributes and relationships.
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
The error code, which contains application-relevant detail.
-
message: string
Additional details about the error as well as possible corrective actions.
-
reason(required): string
The reason for the error that can be shown to a client user.
-
referenceError: string
(uri)
The URI to the documentation describing the error.
-
status: string
The HTTP error code extension.
409 Response
The request couldn't be processed due to a conflict. An item already exists.
Root Schema : Error
Type:
objectAn error.
Show Source
-
@baseType: string
When sub-classing, this defines the super class.
-
@schemaLocation: string
(uri)
The URI to a JSON-schema file that defines additional attributes and relationships.
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
The error code, which contains application-relevant detail.
-
message: string
Additional details about the error as well as possible corrective actions.
-
reason(required): string
The reason for the error that can be shown to a client user.
-
referenceError: string
(uri)
The URI to the documentation describing the error.
-
status: string
The HTTP error code extension.
500 Response
An internal server error occurred.
Root Schema : Error
Type:
objectAn error.
Show Source
-
@baseType: string
When sub-classing, this defines the super class.
-
@schemaLocation: string
(uri)
The URI to a JSON-schema file that defines additional attributes and relationships.
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
The error code, which contains application-relevant detail.
-
message: string
Additional details about the error as well as possible corrective actions.
-
reason(required): string
The reason for the error that can be shown to a client user.
-
referenceError: string
(uri)
The URI to the documentation describing the error.
-
status: string
The HTTP error code extension.
Examples
The following example shows how to delete a usage consumption object by submitting a DELETE request on the REST resource using cURL. For more information about cURL, see "Use cURL".
curl -X DELETE "apiroot/queryUsageConsumption/6500000427" -H "accept: */*"
where apiRoot is for accessing the HTTP Gateway server at either http://hostname:httpPort or https://hostname:httpsPort.
Example of Response Body
If successful, the response code 204 is returned with no response body.
If the request fails, the response includes the appropriate HTTP code. For a 4xx/5xx code, the message body also contains a ProblemDetails structure with the cause attribute set to the appropriate application error.