2026-11-11: record types, flows and exports in the partner portal#

• Optional platformId argument on platformRecordTypes, definePlatformRecordType, flowTemplates, saveFlowTemplate, activateFlowTemplate, retireFlowTemplate, testFlowTemplate, flowRuns, retryFlowRun, platformExportDestinations, platformExportSchedules, platformExportRun, createPlatformExportDestination, updatePlatformExportDestinationCredentials, deletePlatformExportDestination, createPlatformExportSchedule, updatePlatformExportSchedule and runPlatformExportNow. Server tokens leave it out (the token names the platform; a different id is refused). Members signed in to the partner portal pass it: the portal's Record types, Flows and Exports pages use these operations.
• Who may call them. Server tokens with the scope, as before, and now portal members. Portal roles apply (area "data"): support reads, owners, admins and developers also change. User, embed and headless tokens still cannot call them.
• No change for existing integrations: the argument is optional.