API NameWhat It’s ForWhen to Use ItProtocolData FormatCommunication
|Accessing objects in your organization using REST.
|You want to leverage the REST architecture to integrate with your organization. No WSDL requirement. Well-suited for browser-based applications, mobile apps, and highly-interactive social applications.
|Integrating your organization’s data with other applications using SOAP.
|You have pre-existing middleware services that need to work with WSDLs and XML data.
|Chatter REST API
|Accessing Chatter feeds and social data such as users, groups, followers, and files using REST.
|You want to integrateChatter into a variety of applications, such as mobile apps, intranet sites, and third-party Web applications.
|Synchronous (photos are processed asynchronously)
|Loading or deleting large numbers of records.
|You have over a million records to process and speed is a requirement.
|Managing customizations in your organization and building tools that can manage the metadata model, not the data itself.
|You want to migrate changes, such as custom object definitions and page layouts, from asandbox to your production environment.
|Providing a stream of data reflecting data changes in your organization.
|You need near real-time notifications of when records are created or updated.
|Asynchronous (stream of data)
|Apex REST API
|Building your own REST API in Apex. ExposesApex classes as RESTful Web services.
|You need to build custom JSON responses or you want to expose custom functionality that you implemented in Apex.
|JSON, XML, Custom
|Apex SOAP API
|Creating custom SOAP Web services in Apex. Exposes Apex classes as SOAP Web services.
|You need to build custom XML responses or you want to expose custom functionality that you implemented in Apex .
|Building custom development tools forForce.com applications.
|You want to add functionality to your existing development and integration tools or you want to build specialized development tools for a specific application or service.