Which statement best describes REST API capabilities?

Which statement best describes REST API capabilities?

• A. New functionality with Mobile, Journey Builder, and Content Builder
• B. Selective support for core functionality including Email and Data Extensions
• C. REST API does not support transactional messages
• D. New functionality with Mobile, Journey Builder, and Content Builder and selective support for core functionality including Email and Data Extensions

Answer: (D)

REST API capabilities in Marketing Cloud cover both newly added areas and core data functions. The REST API introduces new functionality for MobilePush, Journey Builder, and Content Builder, giving you modern, asset- and journey-centric endpoints. At the same time, it provides selective support for core functionality, such as Email and Data Extensions, meaning you can work with these objects through REST but not necessarily with every feature or operation that SOAP offers. This combination—new, domain-specific endpoints plus partial coverage of core data/messaging objects—best describes what the REST API can do. The other statements fall short because they either ignore the new functionality across these areas or overstate the absence of transactional capabilities.

REST API capabilities in Marketing Cloud cover both newly added areas and core data functions. The REST API introduces new functionality for MobilePush, Journey Builder, and Content Builder, giving you modern, asset- and journey-centric endpoints. At the same time, it provides selective support for core functionality, such as Email and Data Extensions, meaning you can work with these objects through REST but not necessarily with every feature or operation that SOAP offers. This combination—new, domain-specific endpoints plus partial coverage of core data/messaging objects—best describes what the REST API can do. The other statements fall short because they either ignore the new functionality across these areas or overstate the absence of transactional capabilities.