Web Services and SuiteTalk
NetSuite Unknown
2026-07-24

Campaign Template Record Now Available via REST Web Services

The campaign template record (campaigntemplate) is now exposed through the SuiteTalk REST API, supporting full CRUD operations at /services/rest/record/v1/campaigntemplate.

Affects:SuiteTalk REST APICRMMarketing Automation

What changed

The campaigntemplate record is now a supported REST web services record. This exposes email marketing campaign templates to the SuiteTalk REST API with full CRUD support (POST, GET, PATCH, DELETE) at the endpoint:

/services/rest/record/v1/campaigntemplate

The record is not a subrecord itself, but contains the following subrecords:

  • fromEmail
  • replyToEmail
  • restrictToGroup
  • subscription
  • typeName
  • usesMedia

Key fields available on the record include content (HTML body), subject, fromName, emailAsSalesRep, trackStatistics, isPrivate, isInactive, and isAutoConverted. Subrecord references (fromEmail, replyToEmail, restrictToGroup, subscription, usesMedia) are set via { "id": "..." } objects.

Use ?expandSubResources=true on GET requests to inline subrecord data in the response.

Prerequisites

The following features must be enabled at Setup > Company > Enable Features before this record is accessible via REST:

  • Marketing Automation
  • Customer Relationship Management (CRM)
  • CRM Template Categories

What to do

  1. If you currently manage campaign templates through SuiteLet UIs, CSV imports, or SOAP web services, you can now integrate them via REST. Evaluate whether migrating to REST simplifies your workflow.
  2. Review the field names and types in the REST API Browser under the campaigntemplate reference page — Oracle's documentation does not enumerate every field in the article itself.
  3. Note that usesMedia expects a boolean passed as { "id": true } or { "id": false }, which is an unusual pattern for a subrecord reference. Test this in your sandbox before relying on it in production.
  4. Standard OAuth 1.0 authentication headers apply. Ensure your integration record and token-based authentication are configured for REST access.

Version note

The source documentation does not specify which NetSuite release introduced this record to REST web services. Check the REST API Browser in your target account to confirm availability before building against this endpoint.