Skip to content

Add native fetch client section for remote service consumption #2519

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
schwma wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Add native fetch client section for remote service consumption #2519

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5d9c128
add native fetch client section for remote service consumption
schwma Apr 21, 2026
c411c02
Merge branch 'main' into native-fetch-client
schwma Apr 21, 2026
fec82d4
Merge branch 'main' into native-fetch-client
renejeglinsky Apr 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 17 additions & 1 deletion guides/deploy/to-cf.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -155,7 +155,11 @@ The roles/scopes are derived from authorization-related annotations in your CDS

[Learn more about SAP Authorization and Trust Management/XSUAA.](https://discovery-center.cloud.sap/serviceCatalog/authorization-and-trust-management-service?region=all){.learn-more}

### 3. SAP Cloud SDK {#add-cloud-sdk}
### 3. Remote Service Consumption {#remote-services}

CAP supports two HTTP clients for remote service calls.

#### SAP Cloud SDK {#add-cloud-sdk}

If you intend to consume remote services in production, for example, via [BTP Destinations](https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/destination-service), add the requisite SAP Cloud SDK packages, like that for Node.js:

Expand All @@ -167,6 +171,18 @@ npm add @sap-cloud-sdk/resilience

[Learn more about consuming remote services with SAP Cloud SDK.](https://sap.github.io/cloud-sdk/docs/js/overview){.learn-more}

#### Native Fetch Client <Beta /> {#native-fetch}

As an alternative to SAP Cloud SDK, CAP can use Node.js's built-in `fetch` API for remote service calls. Native fetch is selected per request based on the following rules, in that order:
Copy link
Copy Markdown
Contributor

@renejeglinsky renejeglinsky Apr 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
As an alternative to SAP Cloud SDK, CAP can use Node.js's built-in `fetch` API for remote service calls. Native fetch is selected per request based on the following rules, in that order:
As an alternative to SAP Cloud SDK, CAP can use Node.js's built-in `fetch` API for remote service calls. Native fetch is selected per request based on the following rules:


1. If the destination requires features only available in CloudSDK (e.g., BTP Destination Service resolution or non-basic authentication), CloudSDK is always used.
Copy link
Copy Markdown
Contributor

@renejeglinsky renejeglinsky Apr 29, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1. If the destination requires features only available in CloudSDK (e.g., BTP Destination Service resolution or non-basic authentication), CloudSDK is always used.
1. If the destination requires features only available in SAP Cloud SDK (for example, SAP BTP Destination service resolution or non-basic authentication), the SAP Cloud SDK is always used.

2. If <Config>cds.remote.native_fetch</Config> is explicitly set to `true` or `false`, that setting is used.
3. Otherwise, native fetch is used when `@sap-cloud-sdk/http-client` is not installed.

::: warning Current limitations
The native fetch client does not yet support named destinations via BTP Destination Service, only [application defined destinations](../services/consuming-services#use-application-defined-destinations). Authentication is limited to `NoAuthentication` and `BasicAuthentication`. CSRF token handling is not yet fully on par with SAP Cloud SDK.
Copy link
Copy Markdown
Contributor

@renejeglinsky renejeglinsky Apr 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The native fetch client does not yet support named destinations via BTP Destination Service, only [application defined destinations](../services/consuming-services#use-application-defined-destinations). Authentication is limited to `NoAuthentication` and `BasicAuthentication`. CSRF token handling is not yet fully on par with SAP Cloud SDK.
The native fetch client does not yet support named destinations using the SAP BTP Destination service. Only [application defined destinations](../services/consuming-services#use-application-defined-destinations) are supported. In addition, authentication is limited to `NoAuthentication` and `BasicAuthentication`. CSRF token handling is not yet at parity with SAP Cloud SDK.

:::


### 4. MTA-Based Deployment {#add-mta-yaml}

Expand Down
Loading