Delete a Usage Consumption Object

delete

{apiRoot}/queryUsageConsumption/{id}

Deletes the usage consumption object specified by the ID.

Request

Path Parameters

There's no request body for this operation.

Back to Top

Response

Supported Media Types

204 Response

The usage consumption object was deleted successfully.

400 Response

The request isn't valid.
Body ()
Root Schema : Error
Type: object
An error.
Show Source

401 Response

The client doesn't have the correct privileges.
Body ()
Root Schema : Error
Type: object
An error.
Show Source

403 Response

The request wasn't authorized.
Body ()
Root Schema : Error
Type: object
An error.
Show Source

404 Response

The server couldn't find the requested object.
Body ()
Root Schema : Error
Type: object
An error.
Show Source

405 Response

This method isn't supported for the requested resource.
Body ()
Root Schema : Error
Type: object
An error.
Show Source

409 Response

The request couldn't be processed due to a conflict. An item already exists.
Body ()
Root Schema : Error
Type: object
An error.
Show Source

500 Response

An internal server error occurred.
Body ()
Root Schema : Error
Type: object
An error.
Show Source
Back to Top

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.

Back to Top