Campaign Offer Record Exposed to REST Web Services

What changed

The campaignoffer record is now exposed through the SuiteTalk REST API. This is a standalone record — it is not a subrecord and contains no subrecords of its own. Full CRUD operations are supported:

• POST — /services/rest/record/v1/campaignoffer — Create a new campaign offer. The body accepts name, description, and isInactive fields (at minimum).
• GET — /services/rest/record/v1/campaignoffer/{id}?expandSubResources=true — Retrieve a campaign offer by internal ID.
• PATCH — /services/rest/record/v1/campaignoffer/{id} — Update an existing campaign offer.
• DELETE — /services/rest/record/v1/campaignoffer/{id} — Delete a campaign offer by internal ID.

Prerequisites

The Marketing Automation feature must be enabled in your account (Setup > Company > Enable Features > CRM) before this record is accessible via REST. Without it, requests to the campaignoffer endpoint will fail.

Technical details

• Record ID: campaignoffer
• Authentication: OAuth 1.0 (as shown in Oracle's samples). Token-Based Authentication (TBA) headers follow the standard SuiteTalk REST pattern.
• Known fields: name (string), description (string), isInactive (boolean). The full field list and types are available in the REST API Browser under the campaign offer reference page.

Oracle's documentation does not specify the release in which this record was added. Check the REST API Browser in your target account to confirm availability. If the campaignoffer endpoint returns a 404, the feature may not yet be deployed to your account's release.

What to do

1. Verify Marketing Automation is enabled in your account.
2. Check the REST API Browser in your account to confirm the campaignoffer record is listed and to review the full schema (field names, types, and available operations).
3. If you have existing integrations that manage campaign offers through SuiteTalk SOAP or SuiteScript, evaluate whether migrating to REST simplifies your workflow — REST provides a cleaner CRUD interface without WSDL versioning concerns.
4. Update any integration role permissions to include access to the Campaign Offer record if you plan to use this endpoint.
5. For SuiteScript consumers: note that the REST record ID campaignoffer can also be referenced in N/record and N/query contexts, but always verify the internal type string matches — REST record IDs and SuiteScript type enums do not always align.