Identify the custom record type's script ID in NetSuite by navigating to the record type definition or using the metadata catalog endpoint
Via the REST Record API, construct the URL using the custom record script ID as the record type segment and POST a JSON body with field script IDs as keys
Retrieve a custom record instance via GET using the record type script ID and the internal record ID
Via SuiteTalk SOAP, construct a CustomRecord object with the recType attribute set to the custom record type's internalId and POST using the add or get operation
Map between REST field naming (camelCase script IDs) and SOAP field naming (CustomFieldList with scriptId attributes) when normalizing data across both interfaces
Compare the response structures from both APIs and choose the appropriate interface based on batch size requirements and field complexity
Known gotchas
REST and SOAP use different identifiers for the same custom record type; the REST API uses the script ID string while SOAP uses the numeric internalId, and mixing them causes a record-not-found error
Body fields and sublists have different access patterns in both APIs; sublists on custom records via REST require separate sub-resource requests rather than being nested in the main payload
NetSuite's REST Record API for custom records requires the REST Web Services feature to be enabled in the account and the appropriate role permission on the custom record type
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp