DeleteREST

Step facilitates REST DELETE interactions and will return the returned data dictionary and specified headers as data to the next step

Added in version 1.5.0.

Friendly name: DeleteREST
Step class: base_steps_syncpack.steps.DeleteREST.DeleteREST
Step version: 1.0.1
Required parameters: prefix_url

Parameters

This step adds no parameters of its own. It accepts exactly the parameters of Shared parameters: HTTPBaseStep.

Required inherited parameters

These are defined on Shared parameters: HTTPBaseStep but are required here, so a working configuration must set them.

Name	Type	Required	Default	Description
`prefix_url`	string	yes	–	used with relative_url to create the full URL. Example: `http://host.example.com`

Other inherited parameters

This step also accepts 31 optional parameter(s) inherited from Shared parameters: HTTPBaseStep.

Every step also accepts the platform parameters common to all steps – see Platform parameters.

Dependencies

Inherits from: DeleteREST -> HTTPBaseStep -> BaseStep -> Serializable
SyncPack modules: base_steps_syncpack.steps.HTTPBaseStep
External packages: ipaascommon

Behaviour

Fixes method = "DELETE" and enable_paging = False, then delegates to Shared parameters: HTTPBaseStep. Registers no parameters of its own.

Outputs

Same as PostREST. Many APIs return an empty body for a successful delete, in which case the saved output is the response dict rather than a resource — do not rely on a payload being present downstream.

Example

{
  "prefix_url": "https://example.service-now.com",
  "relative_url": "/api/now/table/incident/abc123",
  "auth_method": "http_basic",
  "username": "svc_powerflow",
  "password": "${config.snow_password}",
  "expected_http_response": 204
}

Notes

Set expected_http_response deliberately here. A delete that returns 204 with no body and a delete that returns 404 because the record was already gone are easy to confuse otherwise.