NetSuite REST icon

NetSuite REST

Call NetSuite SuiteTalk REST operations.

Actions979

Intercompany Journal Entry → Remove record

AI-generated

Summary

Delete an Intercompany Journal Entry record by internal ID, optionally sending asynchronous execution or idempotency headers, and optionally outputting request/response debug info.

Inputs

  • Debug Mode — Include the full HTTP request and response details in the node output.
  • Id (required) — Internal identifier of the Intercompany Journal Entry to delete.
  • Prefer — When set to respond-async, instructs NetSuite to process the request asynchronously. Sends the header Prefer: respond-async; the response will contain the header Preference-applied: respond-async.
  • X-NetSuite-Idempotency-Key — Unique key used for idempotent asynchronous requests. Ignored for synchronous calls. Provide a UUID string per RFC 4122.

Output shape

no body — success/failure only

The node returns an empty success payload when the delete succeeds. If Debug Mode is enabled, the output will also contain the raw HTTP request and response data (headers, body, status). When Prefer: respond-async is used, the response will include a 202 status with a Preference-applied: respond-async header; the node still emits no body, only the status and debug information if requested.

Examples

Example 1: Remove a single intercompany journal entry synchronously

Resource: Intercompany Journal Entry, Operation: Remove record, Id: 123, Prefer: (left blank), X-NetSuite-Idempotency-Key: (empty), Debug Mode: false

Example 2: Remove an entry asynchronously with idempotency key

Resource: Intercompany Journal Entry, Operation: Remove record, Id: 456, Prefer: respond-async, X-NetSuite-Idempotency-Key: 550e8400-e29b-41d4-a716-446655440000, Debug Mode: true

Example 3: Delete with debug information for troubleshooting

Resource: Intercompany Journal Entry, Operation: Remove record, Id: 789, Prefer: (left blank), X-NetSuite-Idempotency-Key: (empty), Debug Mode: true

Discussion