PackagePackageA library you install and call yourself.See every one →What this type is →independently maintainedindependently maintainedPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →
abapify/fetch-legacy
A legacy-release implementation of the Fetch API interface for outbound HTTP calls from ABAP, plugging into 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 so the calling code needs no refactoring when it moves to the cloud.
Implements the Fetch API interface for outbound HTTP calls on a legacy release, so code written against that interface is not refactored once it moves to the cloud. The interface itself is 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, the polyfill this implementation plugs into, and it has to be installed first.
Facts
Last pushLicenceMIT
Where it sits
Lives in
Provides
HTTP clientsABAPHTTP clientsCalling 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 [destinations](capability:destinations).
Requires
abapify/fetchabapify/fetchthe polyfill interface this package implements for a legacy release
Who is behind it
abapifyabapifyMaintains this
In the atlas: maintains 9@abapifymaintainerLars HvamContributes to this
In the atlas: maintains 13, contributes to 92, wrote 1@larshpPetr PlenkovContributes to this
In the atlas: contributes to 13@ThePlenkov2 contributors
In the atlas: maintains 9@abapifymaintainerLars HvamContributes to this
In the atlas: maintains 13, contributes to 92, wrote 1@larshpPetr PlenkovContributes to this
In the atlas: contributes to 13@ThePlenkov2 contributors
What it declares
Every artifact
- Type
- Package
- Origin
- Independently maintained
As a package
- Where it runs
- does not say
- Distributed through
- does not say
Connections
Group by
NodeRelationBasis
Functional
HTTP clientsHTTP clientsCalling an external HTTP API from application codeSAP and community, unassessed
provides
stated
provides HTTP clients
Implements the Fetch API interface for outbound HTTP calls so code avoids a rewrite when it moves to the cloud.
“allowing to make outbound http calls and avoiding unnessesary refactoring once code is moved to cloud”
Calling an external HTTP API from application code
Technical
abapify/fetchabapify/fetchFetch API-style HTTP polyfill for cloud and classic ABAPindependent, abap
needs
stated
needs abapify/fetch
the polyfill interface this package implements for a legacy release
“Install [Fetch API](https://github.com/abapify/fetch) which is the polyfill interface”
Fetch API-style HTTP polyfill for cloud and classic ABAP
Download
README
quoted from abapify/fetch-legacy under MIT, readabapify/fetch-legacy/README.mdthe maintainer’s wordsOn GitHub
Legacy compatible fetch API implementation
Legacy compaible fetch API implementation allowing to make outbound http calls and avoiding unnessesary refactoring once code is moved to cloud.
Prerequsites
- Install Fetch API which is the polyfill interface
Others providing
Compare all 10 on the HTTP clients page →HTTP clientsHTTP clientsCalling 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 destinations.SAP and community, unassessed
- abapify/fetch-cloudabapify/fetch-cloudA plugin for the abapify/fetch polyfill that supplies its BAdI implementation for ABAP Cloud, where cl_http_client cannot be used directly; the polyfill is installed first.independent, abapCloud-compatible plugin for the abapify Fetch API polyfill
- 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, abapFetch API-style HTTP polyfill for cloud and classic ABAP
- ABAPFireABAPFireAn ABAP client library for Firebase's Realtime Database REST API, with email-and-password authentication and methods to read, set, update, push and remove data at a path.independent, abapABAP client for Firebase's Realtime Database REST API
- B-Tocs ABAP SDKB-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, abapWeb service client and connector layer for calling out of ABAP
- abap-soql-queryabap-soql-queryAn ABAP report that runs Salesforce SOQL queries against standard or custom objects through a connected app, shows the rows in an ALV grid and exports them to CSV or Excel.independent, abapABAP report that runs Salesforce SOQL queries and exports results
- abap2gappsabap2gappsAn ABAP API for Google Apps integration, with a program, ZGAPPS_UPLOAD, that uploads a chosen file from the SAP system to Google Docs through a consumer registered for OAuth 2.0.independent, abapABAP API for Google Apps, with upload to Google Docs
- ABAP SDK for AzureABAP SDK for AzureABAP objects and classes for sending SAP business process data to Azure services such as Event Hub, Service Bus, Key Vault, Blob and Azure OpenAI, without depending on a middleware product.partner, abapABAP classes for calling Azure services from SAP processes
- 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, abapHTTP client for classic on-premise ABAP and ABAP Cloud
- abap2gsheetabap2gsheetAn ABAP framework that wraps the Google Sheets API behind ABAP calls for on-premise SAP S/4HANA, authenticating through SAP's standard OAuth 2.0 client.independent, abapABAP framework wrapping the Google Sheets API for SAP S/4HANA
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
discovered viadotabap
first seen in the atlas
ecosystem and domainabap, protocols-and-apis
abaplint
issues under its own abaplint configuration0
lines481
statements250
objects8
files13
analysed, main
abaplint version2.120.84
read fromabaplint.app,
Contributors
History in the atlas
- First seen.
For your agent
- Ref
artifact:abapify-fetch-legacy- JSON
- /artifacts/abapify-fetch-legacy.json
- MCP
- Connecting an agent