In this article

Overview

You can use the REST Delete Snap to delete business object resources using a REST API call.

Prerequisites

None.

Supported Features

Works in Ultra Task Pipelines. We recommend you to set the batch size to 1.

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	Field Dependency	Description
Label*	N/A	Specify a 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. Default Value: REST Delete Example: REST Delete
Service URL*	N/A	The excerpt 'REST_Serviceurl' was not found in the space 'SD' or you may not have the necessary permissions to access it. The Service URL for the REST snap has to be valid. If the Service URL contains any special characters, such as !, =, %21, $, and ^, the Snap throws an exception error. You can escape the special characters (using expression language) using one of the following methods: Use the global function encodeURIComponent on any variables that might contain special characters so that they are encoded properly. For example, `'http://coresnapsqa-v4.s3.us-east-2.amazonaws.com/S3Account/'+encodeURIComponent(_fileName)` If you are aware of the code, use the code directly in the Service URL field. For example, http://coresnapsqa-v4.s3.us-east-2.amazonaws.com/S3Account/Special_char_owner_%213%2912.json; where <%213%2912> is the code. We recommend you to use the former (encodeURIComponent) method to escape the special characters. Default Value: N/A Example: https://www.example.com/slm/webservice/v2.0/defect/%s".replace("%s", $.widget.id)
HTTP entity	N/A	Specify the JSON path to the HTTP entity data in the input map data. You can leave this field blank if there is no entity data to send to the service URL. Default Value: N/A Example: $response.entity.id
Batch size	N/A	The number of documents to be included in a single request. The incoming documents will be accumulated in a list up to the defined batch size before it is submitted to the endpoint Make sure to set the batch size only if your REST endpoint expects a list. Default Value: N/A Example: 50
Show all headers	Checkbox	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. If any of these objects has a key-value format, it is parsed into the map data. Default Value: Deselected Example: N/A
Trust all certificates*	N/A	Select this checkbox to trust all certificates, such as self-signed certificates. Default Value: Deselected Example: N/A
Follow redirects*	N/A	Select this checkbox to enable the Snap to follow redirects. If you select this checkbox, the Snap receives a redirect response, such as a 301 or 302 response code, it sends another request to the URL specified in the response Location header. If you deselect this checkbox, the Snap does not make another request, and the 301/302 response appears in the output view. Default Value: Selected Example: N/A
Query parameters	Use this field set to add query parameters to your request. This field set comprises the following fields: Query parameter Query parameter value
Query parameter	N/A	Specify the name (or key) of the query parameter. Default Value: N/A Example: oauth2_access_token
Query parameter value	N/A	Specify the value associated with the query parameter. Default Value: N/A Example: $account.access_token
HTTP header	Use this field set to create the HTTP header key-value pairs required for defining the headers for different types of input (JSON, PDF, DOCX, and so on). If you want to specify only content-type headers, you can configure the Multipart Content-Type property instead. This field set comprises the following fields: Key Value
Key	N/A	Specify the name that you want to use for the HTTP header. Default Value: N/A Example: User-Agent
Value	N/A	Specify the value that you want to assign to the HTTP header. Default Value: N/A Example: SnapLogic
Response entity type	N/A	The excerpt 'Response_Entity_Type' was not found in the space 'SD' or you may not have the necessary permissions to access it. Default Value: DEFAULT Example: TEXT
Read timeout	N/A	Specify the number of seconds for which the Snap waits before aborting the request due to a failure to read from the target service. In some cases, the request does not return, such as during network issues. For those a timeout can be configured to allow failing fast. Every Snap instance can have its own timeout settings. The Snap will execute five retries within a couple of seconds back-off time before it fails. Default Value: 900 Example: 1500
Connection timeout	N/A	Specify the number of seconds for which the Snap waits before aborting the request due to a failure to establish a connection to the target endpoint or service. Default Value: 30 Example: 45
Maximum request attempts	N/A	Specify the maximum number of attempts that the Snap must make to receive a response. If the attempts do not result in a response, the Snap terminates the request. Default Value: 5 Example: 3
Retry request interval	N/A	The excerpt 'Retry_Request_Interval' was not found in the space 'SD' or you may not have the necessary permissions to access it. Default Value: 3 Example: 10
Snap Execution	N/A	Select one of the three modes in which the Snap executes. Available options are: Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime. Execute only: Performs full execution of the Snap during Pipeline execution without generating preview data. Disabled: Disables the Snap and all Snaps that are downstream from it. Example: Validate and Execute

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.
The provided URI is invalid	Illegal character in scheme name	Verify the URI and parameters that you provide are syntactically correct.
URL Parse Exception - 403	The Service URL path might be containing any of the following special characters: !, =, %, #, $, ^&()_¢äâêîôûñç¡¿ÉÙËÇ¨°¸ðø©¢¾A+²½µ®§÷¶þ	To escape the special characters, use the global function encodeURIComponent on any variables that might contain special characters so that they are encoded properly.

Examples

Creating and Deleting an Account in Salesforce Using REST Snaps

In this example Pipeline, we demonstrate how we create an account in Salesforce and delete it using REST Snaps.

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

Initially, we configure the JSON Generator Snap—we enter a name Test Account—the account that you want to create.

Then, we configure the REST Post Snap to create an account in your Salesforce instance using the account-name string of your choice. To do so:

We use the URL provided by Salesforce for managing the accounts available in your instance.
We use '$' in the HTTP entity field to indicate that we want to use the string coming from the Snap upstream.
We add an HTTP header to the Snap, instructing Salesforce to read the document coming in as a JSON file.

We click the Account tab and select the account that we want to use with the Snap.

When we validate the Snap, it creates an account in the Salesforce instance and displays the following output:

The id field lists out the unique identifier of the new account created by the Snap.

We now want to delete the account that you just created. To do so, we need to isolate the account ID from the REST Post Snap's output. We use a Mapper for this task.

Upon validation, the Mapper Snap displays the following output:

We now use the REST Delete Snap to delete the newly-created account.

When the Snap is executed, the account is deleted.

Downloads

	File	Modified

No files shared here yet.

Snap Pack History

Click to view/expand

Release	Snap Pack Version	Date	Type	Updates
November 2024	main29029	13 Nov 2024	Stable	Updated and certified against the current SnapLogic Platform release.
August 2024	main27765	21 Aug 2024	Stable	Upgraded the `org.json.json` library from v20090211 to v20240303, which is fully backward compatible.
May 2024	437patches26522	12 Jun 2024	Latest	Enhanced the REST OAuth2 Account with Snaplex support for executing OAuth2 operations.
May 2024	main26341	08 May 2024	Stable	Updated and certified against the current SnapLogic Platform release.
February 2024	main25112	14 Feb 2024	Stable	Updated and certified against the current SnapLogic Platform release.
November 2023	main23721	08 Nov 2023	Stable	Updated and certified against the current SnapLogic Platform release.
August 2023	main22460	16 Aug 2023	Stable	Updated and certified against the current SnapLogic Platform release.
February 2023	main21015	10 May 2023	Stable	Upgraded with the latest SnapLogic Platform release.
February 2023	432patches20054	09 Mar 2023	Latest	For Snaps using AWS Signature V4 accounts, DNS canonical names are now supported for S3 buckets.
February 2023	main19844	09 Feb 2023	Stable	Upgraded with the latest SnapLogic Platform release.
November 2022	main18944	10 Nov 2022	Stable	Upgraded with the latest SnapLogic Platform release.
September 2022	430patches17851	16 Sep 2022	Latest	The REST Post Snap now works without displaying any errors when the Show all headers checkbox is selected and the Content-type is text/xml or application/xml.
August 2022	430patches17684	30 Aug 2022	Latest	The REST AWS Sig v4 Account is now enhanced with the AWS Region and Service Name fields that enable the Snap to support Virtual Private Cloud (VPC) endpoint.
August 2022	main17386	11 Aug 2022	Stable	You can set cookie policy specifications using the Cookie Policy dropdown list in REST Snaps . Support for auto-retries where the REST Snaps automatically retry when they encounter 429 HTTP status code - `Too Many Requests` error. The REST AWS Sig v4 Account supports: Passing AWS Security Token Service (STS) temporary credentials in the Security Token field. Expression values for Access-key ID and Secret Key fields. Improved the performance of REST Snaps when the Snaps encounter Unauthorized (401) or Forbidden (403) errors even when the user credentials are available in the organization and the account type is OAuth2.
4.29 Patch	429patches17084	19 Jul 2022	Latest	Enhanced the following REST Snaps with Cookie Policy dropdown list to set the cookie policy specifications. This field is case-insensitive: REST Delete REST Get REST Patch REST Post REST Put Learn more Cookie Policy: The Cookie Policy to select from the following options: BROWSER COMPATIBILITY: This policy is compatible with different servers even if they are not completely standards-compliant. If you are facing issues while parsing cookies, you should try using this policy. IGNORE COOKIES: This cookie policy ignores all cookies. You should use this policy to prevent HTTP Client from accepting and sending cookies. RFC STRICT: All servers that handle version 1 cookies should use this policy. RFC LAX: The original cookie specification which formed the basis for RFC2109. Added a new field Security Token in the REST AWS Sig v4 Account to support AWS Security Token Service (STS) for using temporary credentials. Enhanced the REST AWS Sig v4 Account to support expression values for Access-key ID and Secret Key fields.
4.29 Patch	429patches16076	20 May 2022	Latest	Enhanced the REST Snaps with support for auto-retry where the Snap retries automatically when the Snap encounters 429 HTTP status code - Too many requests error. Improved the performance of REST Snaps when the Snaps encountered errors due to Unauthorized (401) or Forbidden (403) statuses though the user credentials are available in the organization and the account type is OAuth2.
4.29	main15993	14 May 2022	Stable	Added the REST In-memory OAuth2 Account type with Client Credentials Grant Type that supports and stores the access token in memory for reuse until it expires. When the Snap encounters `401` or `403` errors, this account generates a new token after refreshing the cache.
4.28 Patch	428patches15172	28 Mar 2022	Latest	Fixed an issue that caused REST SSL accounts to fail when the username in the REST SSL Account was null and the Enhanced Encryption level was low, medium, or high.
4.28	main14627	12 Feb 2022	Stable	Enhanced the REST Post, REST Put, and REST Patch Snaps with the Multipart Type list to support multipart (files and text) upload. Renamed the following fields: Upload File(s) field set to Form Upload Upload-file key to Multipart Key Upload file to Multipart Value
4.27 Patch	427patches12750	01 Dec 2021	Latest	Enhanced the REST Put Snap with the Upload Transfer Request Type field to support encoding of chunked transfer and calculating content length.
4.27	main12989	15 Nov 2021	Stable and Latest	Fixed an issue in the REST OAuth2 account that caused a new feature, OAuth Password Grant Type to be excluded from the GA version. The latest deployed build includes this feature.
4.27	main12833	13 Nov 2021	Stable	Enhanced REST OAuth2 accounts with a new option password for Grant Type to obtain an access token through user credentials. On selecting password, the Snap populates the Username and Password fields to enter the credentials.
4.26	426patches12749	08 Nov 2021	Latest	Fixed an issue with the REST Post Snap, where the Snap delayed the fetching of documents, when the batch size is greater than or equal to one.
4.26	426patches11746	01 Oct 2021	Latest	Enhanced the REST Post Snap to display all cookies (`securedauth` cookies and `httponly` cookies) from the CookieStore along with headers when you select the Show all headers checkbox.
4.26	main11181	14 Aug 2021	Stable	Upgraded with the latest SnapLogic Platform release.
4.25 Patch	425patches10419	21 Jul 2021	Latest	Fixed a memory leak issue in the REST Snap Pack
4.25 Patch	425patches9929	13 Jul 2021	Latest	Enhanced the REST Snap Pack to support Proxy Authentication.
4.25 Patch	425patches9684	20 May 2021	Latest	Fixed the REST Post Snap that fails to correctly set the Content-Length header when working with multi-file uploads. Added Send Client Data as Basic Auth Header check box to the OAuth2 and OAuth2 SSL accounts. This check box enables you to include and pass the client credentials information in the header when connecting to the OAuth endpoint. Added a new account type REST AWS Sig V4 Account that adds the ability to call any AWS API.
4.25	main9554	08 May 2021	Stable	Upgraded with the latest SnapLogic Platform release.
4.24	main8556	13 Feb 2021	Stable	Upgraded with the latest SnapLogic Platform release.
4.23	main7430	14 Nov 2020	Stable	Improved the handling of expired access tokens in REST Snaps that use OAuth2 accounts (REST OAuth2 Account and REST OAuth2 SSL Account). The Snaps can refresh expired access tokens on-demand, through a request to the platform. The Snap reloads the account with the updated/fresh access token before attempting the next retry.
4.22 Patch	422patches7103	19 Oct 2020	Stable	Enhances the Snaps in REST Snap Pack by separating the retry logic for OAuth account from that of the Snap.
4.22	main6403	12 Sep 2020	Stable	Added a new account type, REST OAuth2 SSL, which enables support for the OAuth2 SSL authentication for REST Snaps with endpoints that require client certificates. [Docs Update] Applied the enhanced doc template to the Snap Pack's documentation. Improves usability by enhancing Snap field descriptions, functional examples, and use cases.
4.21 Patch	rest8858	-	Latest	Fixed the REST Get and REST Post Snaps that does not parse Content-Encoding and Content-Type headers for gzipped responses.
4.21	snapsmrc542	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.20 Patch	rest8798	-	Latest	Fixed the REST POST Snap that fails when a single file is uploaded in multi-part form using the Single file upload Snap settings.
4.20	snapsmrc535	-	Stable	The new Multipart related option in the Upload body type property in the REST Post Snap enables you to post files to the Google Drive API and retain the original names. The REST Account now has a new Grant Type option called Client Credentials. This enables the Snap to obtain an access token to the client ID and client secret through the token endpoint URL.
4.19 Patch	rest8374	-	Latest	Added a drop-down property Retry Policy to the REST Snaps to provide users with different retry options for connection and 4xx and 5xx error responses. Fixed the REST GET Snap that limits the output to five documents, even when more output documents are expected. Critical fix If your current or new Pipelines with REST Snaps use the retry functionality, then we recommend you to use this latest patch version as subsequent GA releases may result in Pipeline executions failing. Else, you can continue using your existing Snap Pack version (stable distribution – snapsmrc528).
4.19	snapsmrc528	-	Stable	Fixed a regression issue wherein REST Snaps are unable to handle empty XML responses when Show All Headers is enabled.
4.18	snapsmrc523	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.15 Patch	rest6310	-	Latest	Fixed an issue with the NLTM Rest account connection hanging infinitely.
4.15	snapsmrc500	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.14 Patch	rest6159	-	Latest	Fixed an issue wherein the REST GET and POST Snaps were infinitely trying to connect to endpoint even after pipeline execution abortion.
4.14 Patch	rest5782	-	Latest	Fixed an issue wherein the REST POST Snap was not accepting any blank values from upstream Mapper Snap.
4.14 Patch	rest5719	-	Latest	Fixed an issue where the Ultra task was not producing a valid response while acknowledging documents.
4.14	snapsmrc490	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.13 Patch	NA	-	Latest	REST POST Snap: New properties: Multipart Content-Type, and Filename to be used added.
4.13	snapsmrc486	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.12 Patch	rest4917	-	Latest	Fixed an encoding issue with the REST Get Snap so that it uses the same encoding format (UTF-8) by default on all machines instead of using a different encoding format based on the machine's Operating System.
4.12 Patch	rest4816	-	Latest	Fixed an issue that caused the REST OAuth accounts to fail when running in orgs with Enhanced encryption in Medium or higher level.
4.12 Patch	rest4781	-	Latest	Enhanced REST Post Snap to prevent it from encoding file names.
4.12	snapsmrc480	-	Stable	Added Upload body type property to the REST Post Snap for processing the specified content type.
4.11 Patch	rest4333	-	Latest	Added support for the Binary File Uploads with the REST POST Snap.
4.11	snapsmrc465	-	Stable	Updated support of NTLM Account Authentication to the REST Snap Pack.
4.10 Patch	rest4070	-	Latest	Resolved an issue with the REST GET Snap that often fails to exit properly. This should reduce or eliminate that problem.
4.10	snapsmrc414	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.9 Patch	rest3177	-	Latest	Addressed an issue with REST Get displaying the authorization header in plain text
4.9 Patch	rest3126	-	Latest	Added Connection timeout property to specify the number of seconds to wait before terminating a connection. The Timeout property has been renamed to Read timeout.
4.9.0	snapsmrc405	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.8.0	snapsmrc398	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.7.0 Patch	rest2555	-	Latest	Addressed an issue in the REST Post Snap with the REST API not returning a full cookie response. Added Show all headers setting to the show full cookie response for the Post, Put, Patch and Delete Snaps.
4.7.0 Patch	rest2336	-	Latest	Resolved an issue with REST Get not handling multiple response cookies.
4.7.0 Patch	rest2260	-	Latest	Added a new "Follow redirects" setting to toggle whether redirects should be followed (default behavior is to follow redirects)
4.7.0	snapsmrc382	-	Stable	Updated Snaps in the REST Snap Pack with Response entity type field(The DEFAULT option under this property allows the backward compatibility. The addition of the property will not affect the existing production pipelines and allows them to run as before). Updated Snaps in the REST Snap Pack with Maximum request attempts and Retry request interval Upload fields. Updated the RESTPost Snap with Upload transfer request type field.
4.6.0 Patch	rest1992	-	Latest	Resolved an issue where Rest Snaps failed to process the received response that is encoded in charsets such as Windows-1252. This fix will process the response purely based on the charset provided in the Content-Type header.
4.6.0	snapsmrc362	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.5.1	rest1566	-	Latest	A new property was added to the REST Get Snap to specify the iteration interval for pagination. All Snaps now have at most one input and one output view.
4.5.0	snapsmrc344	-	Stable	Upgraded with the latest SnapLogic Platform release.
4.4.1	NA	-	Latest	Resolved an issue with REST SSL Accounts with Username not send the Authorization header with the HTTP request.
4.4.0	NA	-	Stable	REST Get now supports using parameters from an input document in the Next URL Setting.
4.3.1	NA	-	Latest	Addressed a defect where REST GET Snap fails saying 'Scheme "http" not registered'
Fall Release 2015 (4.3.0)	NA	-	Stable	Two-way SSL support was added to the REST account. REST Get Now has support for iterating over additional result pages. Header variables are now being updated for each input REST Post Improved error handling messages. Resolved an issue with the Snap failing with "Failed to execute HTTP request" error.
September 5, 2015 (4.2.2)	NA	-	Latest	Maximum retries and Retry interval support added. Resolved an issue with using a REST Dynamic OAuth2 account with Facebook Graph API. REST Account: REST SSL account added.
June 27, 2015 (2015.22)	NA	-	Latest	REST Get now allows you to have no output views. Previously, there was exactly one output view.
June 6, 2015 (2015.20)	NA	-	Latest	Rest Post Snap now supports posting a file.
May 2, 2015	NA	-	Stable	REST: Output views made optional
January 2015	NA	-	Stable	Optional Raw data property added to all REST Snaps. If selected, the HTTP response content is written to the output view as is. If not selected, it is parsed according to the content type specified in the response header.
October 18, 2014	NA	-	Stable	NEW! REST Patch Snap introduced in this release. Addressed an issue where REST GET (and perhaps REST Snaps) error view does not include response body.
Fall 2014	NA	-	Stable	REST Get: support added for gzip format.
June 30, 2014	NA	-	Stable	Addressed an issue with RestRequestExecutor class writing data into error views even on successful requests status code 201, 204.
May 2014	NA	-	Stable	REST Get, REST Post all updated to support input parameters in HTTP headers
July 2013	NA	-	Stable	NEW! REST Delete Snap introduced in this release. NEW! REST Get Snap introduced in this release. NEW! REST Post Snap introduced in this release. NEW! REST Put Snap introduced in this release.

REST Delete