Campaign Subscription Record Now Exposed via REST Web Services

What changed

The campaignsubscription record is now exposed as a REST web services resource. This is a top-level record (not a subrecord) and contains no subrecords. It supports full CRUD operations at the endpoint:

/services/rest/record/v1/campaignsubscription

Supported HTTP methods

• POST — Create a new campaign subscription
• GET — Retrieve a campaign subscription by internal ID (supports expandSubResources=true)
• PATCH — Update an existing campaign subscription
• DELETE — Remove a campaign subscription by internal ID

Known fields

Based on the code samples provided by Oracle, the record exposes at least these fields:

• name (string)
• description (string)
• externalName (string)
• externalDescription (string)
• isInactive (boolean)
• subscribedByDefault (boolean)

For the complete field list and field types, refer to the campaignsubscription entry in the REST API Browser.

Prerequisites

The Marketing Automation feature must be enabled in your account before this record is accessible via REST. Navigate to Setup > Company > Enable Features > CRM tab and confirm Marketing Automation is checked.

What to do

1. If you manage campaign subscriptions programmatically (e.g., syncing subscription lists with an external email platform), you can now use the REST API instead of SuiteTalk SOAP or SuiteScript. The record ID is campaignsubscription.
2. Verify the Marketing Automation feature is enabled in every target account (including sandbox and production) before making REST calls against this record.
3. Review the REST API Browser for the full schema — Oracle's sample payloads are minimal and may omit optional or read-only fields.
4. Note that Oracle's published JSON samples contain a syntax error (missing commas between isInactive and subscribedByDefault). Ensure your payloads include proper comma delimiters.
5. Authentication uses OAuth 1.0 as shown in the samples. If you are using OAuth 2.0 or token-based authentication (TBA), the standard authorization headers apply; the endpoint path remains the same.

Caveats

Oracle does not specify which NetSuite release introduced this REST record. The source page lacks a version number or publication date. Confirm availability in your account's REST API Browser, as record exposure can vary by release and account configuration.