In this article

Table of Contents

maxLevel	2
absoluteUrl	true

Overview

Use the REST Delete Snap to delete business object resources using a REST API call.

Prerequisites

None.

Supported Features

Works in Ultra Pipelines if a timeout is specified and batching is disabled.

Limitations and Known Issues

None.

Snap Input and Output

Input/Output	Type of View	Number of Views	Examples of Upstream and Downstream Snaps	Description
Input	Document	Min: 0 Max: 1	REST Get Mapper Script	Each input document contains the ID of the object to be deleted at the REST API service endpoint.
Output	Document	Min: 0 Max: 1	REST Post JSON Formatter Mapper	Each output document contains response data from the REST API service endpoint detailing the status of the request.

Snap Settings

Parameter Name Data Type Description Default Value Example

Label String The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline. N/A Delete Identified Objects

Service URL

String

The service endpoint URL of the REST API.

The Snap looks for the value at the JSON path provided in the input document ($.widget.id in the sample service URL provided on the right) and replaces "%s" in the Service URL with this value.

N/A

"https://www.example.com/slm/webservice/v2.0/defect/%s".replace("%s", $.widget.id)

HTTP entity

String

The JSON path to the HTTP entity data in the input map. You can leave this property empty if there is no entity data to send to the service URL.

$ (the HTTP entity data is at the root of the input map.)

$response.entity.id (if the HTTP entity that you want to delete is the value of the response.entity.id key in the input map.)

Batch size Integer The number of delete requests that you want to execute per batch. The Snap accumulates incoming documents in a list up to the defined batch size before the entire batch is submitted to the endpoint. Make sure to only set this if your REST endpoint expects a list. N/A 50

Show all headers

Check box/ Boolean

The REST endpoint may return a response with multiple headers with the same header name.

If this property is deselected, only one response header will be shown in the output document.
If selected, the response header displays all the response header values received as a list of objects.

Note
If any of these objects has a key-value format, it is parsed into the map data.

Deselected

N/A

Trust all certificates Check box Select this check box to instruct the Snap to trust all certificates, such as self-signed certificates. Deselected N/A

Follow redirects

Check box

Select this check box to instruct the Snap to follow HTTP redirects.

For example, when this check box is selected and the endpoint sends a redirect response, such as a 301 or 302 response code, the Snap makes another request to the URL specified in the Location header of the API response.

In the same scenario, when this check box is not selected, the Snap does not make the second request, and the redirect response code will appear in the output view.

Selected

N/A

Query parameters Fieldset Enables you to define query parameters. This is optional and can also be defined directly in the service URL.

Query parameter

String

The name that you want to use for the query parameter.

N/A

oauth2_access_token

Query parameter value

String

The value that you want to assign to the query parameter.

N/A

$account.access_token

HTTP header Fieldset Enables you to define the HTTP headers that you want to use with your query. This is optional and can also be defined directly in the service URL.

Key

String

The name that you want to use for the HTTP header.

N/A

User-Agent

Value

String

The value that you want to assign to the HTTP header.

N/A

SnapLogic

Response entity type

String

The response entity type in the output document. The available options are:

DEFAULT: Select this option to process the response entity automatically. The Snap attempts to convert the entity into a string or a byte array, depending on the contents of the response headers.
TEXT: Select this option to produce an entity of type String.
BINARY: Select this option to produce a byte array.

Note
If TEXT or BINARY is selected, the Snap will not attempt to parse the entity content. If DEFAULT is selected, the Snap parses the response received and produces the expected result in most cases. If it fails to do so, set the Response entity type to TEXT or BINARY as appropriate.

DEFAULT

TEXT

Read timeout

Integer

The number of seconds for which you want the Snap to wait before aborting the request.

Note
Every Snap instance can have its own timeout settings. The Snap executes five retries with a couple of seconds back-off time before it fails.

900

1500

Connection timeout

Integer

The number of seconds for which the Snap waits before aborting the request due to a failure in establishing a connection to the target service.

30

45

Maximum request attempts

Integer

The maximum number of attempts that the Snap makes to receive a response. The request is terminated once the maximum request attempt count is reached.

5

3

Retry request interval

Integer

The interval (in seconds) between two successive requests.

3

10

Snap Execution

String

Specifies the execution type:

Validate & Execute: Performs limited execution of the Snap (up to 50 records) during Pipeline validation; performs full execution of the Snap (unlimited records) during Pipeline execution.
Execute only: Performs full execution of the Snap during Pipeline execution; does not execute the Snap during Pipeline validation.
Disabled: Disables the Snap and, by extension, its downstream Snaps.

Validate and Execute

Execute only

Troubleshooting

Error	Reason	Resolution
Batch execution failed	The Pipeline ended before the batch could complete execution due to a connection error.	Verify that the Batch size field is configured to handle the inputs properly. If you are not sure when the input data is available, configure this field as zero to keep the connection always open.

Examples

Creating and Deleting an Account in Salesforce Using REST Snaps

In this example, you create an account in Salesforce and delete it using REST Snaps.

Note
To use this example, you need at least an account in the free version of Salesforce. To create a Salesforce account, see Salesforce Developers.

You design the Pipeline as follows:
In the JSON Generator Snap, you enter a name for the account that you want to create. In this example, you create an account called Test Account.
You configure the REST Post Snap to create an account in your Salesforce instance using the account-name string of your choice. To do so:
1. You use the URL provided by Salesforce for managing the accounts available in your instance.
2. You use '$' in the HTTP entity field to specify that you want to use the string coming from the Snap upstream.
3. You add an HTTP header to the Snap, instructing Salesforce to read the document coming in as a JSON file.
You click the Account tab and select the account that you want to use with the Snap.

You save your changes and close the Snap. When you validate the Snap, it creates an account in your Salesforce instance and displays the following output:

The id field lists out the unique identifier of the new account created by the Snap.
You now want to delete the account that you just created. To do so, you need to isolate the account ID from the REST Post Snap's output. You use a Mapper for this task.

Upon validation, the Mapper Snap offers the following output:
You now use the REST Delete Snap to delete the newly-created account:

When the Snap is executed, the account is deleted.