PackagePackagetypeA library you install and call yourself.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

abapify/fetch

A 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.

The same HTTP call needs different ABAP classes depending on the release: cl_http_client on legacy systems, but cl_http_destination_provider or cl_web_http_client_manager in ABAP Cloud, where cl_http_client is not released for use. zcl_fetch gives one minimalistic facade over a request, response and destination instead, so a call such as by_url(...)->fetch(...) works the same way wherever it runs, with the release-specific implementation supplied by a plugin like Cloud fetch. It covers building the request and reading status, body and headers back off the response, and leaves a full alternative client, such as open-abap's cross-http-client, to that project.

Facts

Last push

Where it sits

Lives in
Provides
HTTP clientsABAPHTTP clientscapabilityCalling 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
throwthrowartifactNamed as a dependency in its documentation.

Who is behind it

abapifyabapifyOrganisationMaintains this
In the atlas: maintains 9
@abapify
maintainerLars HvamPersonContributes to this
In the atlas: maintains 13, contributes to 92, wrote 1
@larshp
Petr PlenkovPersonContributes to this
In the atlas: contributes to 13
@ThePlenkov
2 contributors

Before choosing this

Signals

LicenceNo licenseNeither the package manifest nor the repository tree declares a licence

Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.

What it declares

Every artifact

Type
Package
Origin
Independently maintained

As a package

Where it runs
does not say
Distributed through
does not say

Connections4

README

quoted from abapify/fetch, read
abapify/fetch/README.mdOn GitHub

Fetch ABAP polyfill

ABAP Fetch API-like implementation

excerpt, no licence read, read the rest, on GitHub
HTTP clients
  1. abapify/fetch-cloudCloud-compatible plugin for the abapify Fetch API polyfill
  2. abapify/fetch-legacyLegacy-release Fetch API implementation for outbound HTTP in ABAP
  3. ABAPFireABAP client for Firebase's Realtime Database REST API
  4. B-Tocs ABAP SDKWeb service client and connector layer for calling out of ABAP
  5. abap-soql-queryABAP report that runs Salesforce SOQL queries and exports results
  6. abap2gappsABAP API for Google Apps, with upload to Google Docs
  7. ABAP SDK for AzureABAP classes for calling Azure services from SAP processes
  8. cross-http-clientHTTP client for classic on-premise ABAP and ABAP Cloud
  9. abap2gsheetABAP framework wrapping the Google Sheets API for SAP S/4HANA

Details

Sources3
Added by handdiscovered herechecked
github.com/abapify/fetchtree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

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 viaAdded by hand
first seen in the atlas
ecosystem and domainabap, protocols-and-apis
abaplint
issues under its own abaplint configuration0
lines706
statements417
objects27
files53
analysed, main
abaplint version2.120.84
Contributors2

From the repository’s contributor list, .

History in the atlas1
  1. First seen.
For your agent
Ref
artifact:abapify-fetch
JSON
/artifacts/abapify-fetch.json
MCP
Connecting an agent