NetSuite REST icon

NetSuite REST

Call NetSuite SuiteTalk REST operations.

Actions979

Gift Certificate Item → Insert or update record

AI-generated

Summary

Send a PUT request to update (or create if not existing) a Gift Certificate Item in NetSuite by its internal ID, optionally adding custom and additional fields.

Inputs

  • id (required) — Internal NetSuite identifier of the gift certificate item.
  • isDebugMode — If true, the node outputs the full request and response payloads in the result.
  • additionalFields — Collection of standard item properties (e.g., itemId, description, price, partner values, etc.) that should be sent in the body of the PUT request.
  • customFields — Fixed collection allowing you to set custom field values for fields that exist on the record. Each entry specifies the field name, type, and value.
  • Prefer — Header to request async processing (respond-async).
  • X-NetSuite-Idempotency-Key — Unique idempotency key for asynchronous calls.
  • X-NetSuite-PropertyNameValidation — Strictness level for property name validation.
  • X-NetSuite-PropertyValueValidation — Strictness level for property value validation.

Output shape

an object containing the NetSuite record as returned by the REST API; if debug mode is enabled, the output also includes the raw HTTP request and response.

The API may return paginated fields or embedded objects for nested collections. Error responses are propagated by the node as a standard error object. The output structure mirrors NetSuite’s JSON schema for Gift Certificate Items.

Examples

Example 1: Update basic item attributes

Set id to 123, enable isDebugMode, and provide fields such as itemId, price (list), and daysBeforeExpiration in additionalFields.

Example 2: Add or change a custom field

Provide id, add a customField entry for customerCategory with type select and choose the desired internal ID.

Example 3: Execute an asynchronous update

Set id, enable Prefer: respond-async and provide an X-NetSuite-Idempotency-Key value to ensure the request runs only once.

Discussion