Lead Source Record Now Exposed via SuiteTalk REST API

What changed

The lead source record is now exposed to the SuiteTalk REST web services framework. The REST record ID is leadsource, and the full endpoint path is:

/services/rest/record/v1/leadsource

All four standard HTTP methods are supported:

• POST — create a new lead source
• GET — retrieve a lead source by internal ID (supports expandSubResources=true)
• PATCH — update an existing lead source
• DELETE — remove a lead source by internal ID

The record is not a subrecord and contains no subrecords, so there is no sublisting or subrecord wiring to worry about.

Available fields

Based on the code samples in the documentation, the following fields are confirmed writable:

• name (string)
• description (string)
• isInactive (boolean)
• externalId (string)

Consult the REST API Browser for the full field list and field types — Oracle's documentation defers to the browser for the complete schema.

Prerequisites

The CRM feature must be enabled in your account (Setup > Company > Enable Features > CRM) before the endpoint will respond. Requests against accounts without CRM enabled will fail.

What to do

1. If you manage lead sources via SOAP or CSV imports today, you can now migrate those integrations to REST. The endpoint supports OAuth 1.0 authentication using the standard Authorization header with realm, consumer key, token, and signature parameters.
2. If you sync lead sources to or from an external CRM or marketing platform, use the externalId field for cross-system key mapping, exactly as you would on other REST-exposed records.
3. Review the REST API Browser for the full schema. The documentation does not enumerate every field — only name, description, isInactive, and externalId appear in the samples. Fields such as subsidiary restrictions or custom fields on the lead source record may also be available; verify in the browser.
4. Governance note: REST web service calls consume governance units under the standard SuiteTalk concurrency and rate-limit model. No special governance considerations are called out for this record type.