SAP Cloud Integration provides two primary methods to connect to Twitter's API. The most direct method is using the dedicated Twitter outbound adapter, which is specifically designed for this purpose. This adapter is placed within a Request-Reply step in an integration flow to send a request and receive a response. Alternatively, since Twitter's API is a standard RESTful web service based on HTTP, the generic HTTP outbound adapter can also be configured to connect to it. This also requires a Request-Reply step to manage the call and response, along with manual configuration of the endpoint URL and OAuth credentials.

B. Use only the Twitter outbound adapter: This is imprecise. An adapter is a configuration component; it must be used within a flow step like Request-Reply to execute the call during message processing.

C. Use RFC adapter to connect directly to Twitter: The RFC adapter is used for the SAP-proprietary Remote Function Call protocol to communicate with SAP ABAP systems and is not compatible with Twitter's web-based API.

1. SAP Help Portal

Cloud Integration – Twitter Adapter: The official documentation describes the Twitter adapter for connecting to the Twitter API. Integration flow examples consistently show outbound adapters being used within a Request-Reply step. The adapter handles the specific authentication (OAuth 1.0a) and API calls for Twitter. (See SAP Help Portal -> Cloud Integration -> Prepackaged Integration Content -> Adapters and Modules -> Twitter Adapter).

2. SAP Help Portal

Cloud Integration – HTTP Receiver Adapter: This documentation explains that the HTTP adapter can be used to call an external system via HTTP/HTTPS. It supports various authentication methods

including OAuth2

making it suitable for connecting to modern REST APIs like Twitter's. The adapter is configured with the target URL and credentials. (See SAP Help Portal -> Cloud Integration -> Developing Integration Content -> Configure the Receiver HTTP Adapter).

3. SAP Help Portal

Cloud Integration – Request-Reply: The documentation for the Request-Reply flow step explicitly states its purpose: "You use a Request Reply step to call an external system and retrieve a response from it... The call is routed through a receiver channel." This confirms that both the Twitter and HTTP adapters would be used within this step. (See SAP Help Portal -> Cloud Integration -> Developing Integration Content -> Define a Request-Reply Step).