NetSuite REST Azerion icon

NetSuite REST Azerion

Call NetSuite SuiteTalk REST operations.

Actions981

Partner → Insert or update record

AI-generated

Summary

Insert a new partner record or update an existing one in NetSuite by specifying the partner's internal ID and providing details via various optional fields and custom fields.

Inputs

  • id (required) — The internal ID of the partner record to insert or update.
  • authMethod — Choose the authentication method (OAuth1 or OAuth2) used for the request. Defaults to OAuth1.
  • autoName — Boolean flag to let NetSuite auto-generate the partner name if true; if false, supply a manual name.
  • companyName — The legal name of the partner company. Recommended if auto-name generation is used.
  • entityId — The name of the partner as it should appear in lists.
  • email — The partner's email address.
  • phone — Phone number of the partner.
  • comments — Additional information about the partner.
  • isInactive — Boolean to mark the partner as inactive.
  • defaultBilling — Boolean indicating if the address is the default billing address.
  • defaultShipping — Boolean indicating if the address is the default shipping address.
  • customFields — List of custom fields to set on the partner record, with field names, types, and values.
  • additionalFields — Collection of additional optional partner fields including address book entries, categories, campaigns, class, contacts, department, location, subsidiary, and others, with nested detailed options.
  • replace — Comma delimited sublist names to replace all lines with those specified in the request.
  • replaceSelectedFields — Boolean to specify if all fields that should be deleted in the update request must be included in the replace query parameter.
  • isDebugMode — Boolean to include full request and response details in output for debugging.

Output shape

a JSON object representing the inserted or updated partner record response from NetSuite, including any NetSuite internal IDs and field data.

Response may include additional debug information if Debug Mode is enabled. The request updates or inserts the partner record identified by the internal ID; if the record does not exist, it is inserted; otherwise, it is updated. Custom fields and sublist data can be provided. API errors will be returned if mandatory inputs are missing or invalid.

Examples

Example 1: Insert a new partner with auto-generated name

Set 'id' to the intended internal ID, check 'autoName' to true, provide 'companyName' for legal name, and populate optional fields like 'email' and 'phone'.

Example 2: Update an existing partner

Provide the known internal 'id', set fields to update such as 'comments', 'isInactive', or 'customFields', and set 'replace' parameters to overwrite sublists if needed.

Links

Discussion