HTTP clients
Calling an HTTP API outside the system from application code, with the request, the credential and the response handled by a client each time the call is made. Serving HTTP is the other direction, and where the address and the credential are kept is destinationsDestinationsReaching a system that is not yours — an S/4HANA tenant, an on-premise service, a third-party API — without the address, the credentials or the tunnel being written into the application. The destination is the indirection, and the reason an endpoint can move without a redeploy.SAP and community, unassessed.
Overview
In Standard ABAP the factory method CREATE of CL_HTTP_CLIENT returns a client object for an address. In ABAP for Cloud Development the released CL_WEB_HTTP_CLIENT_MANAGER creates the client from an HTTP destination object, built from a communication arrangement or a plain URL.
Not covered: At the generic request. The two classes are separate APIs, so code written against CL_HTTP_CLIENT has to be rewritten for a cloud release, and a third-party service's sign-in and payloads are written by hand on top of either one.
How the core classes and the community clients came to be present side by side has not been assessed. That CL_HTTP_CLIENT is not released for ABAP Cloud is stated in the abapify/fetch README rather than on an SAP page checked here.
Clients that run on classic and cloud releases alike, such as abapify/fetchabapify/fetchA Fetch API-style polyfill for ABAP: one facade over request, response and destination, with the release-specific HTTP client of cloud or classic systems supplied by a plugin like Cloud fetch.independent, abap and open-abap cross http clientcross-http-clientAn ABAP HTTP client intended to work across classic on-premise ABAP and ABAP Cloud, using CL_HTTP_CLIENT on the one and CL_HTTP_DESTINATION_PROVIDER on the other.community org, abap. Also a web service client and connector that handle secrets and JWT tokens beside the call (btocs coreB-Tocs ABAP SDKAn ABAP package that carries the outbound web service call for an SAP ABAP server, with the utility and security classes it needs under it and one plugin per integration on top.independent, abap), and clients for one vendor's API each: Azure services, Firebase, Google Sheets and Salesforce.
Artifacts
Content
Show 2 more
Details
Coverage
For your agent
- Ref
capability:http-clients- JSON
- /capabilities/http-clients.json
- MCP
- Connecting an agent