onedevatlasBeta
Browse the atlas
AllCAPUI5BTPABAP
All CAPNode.jsJava
CapabilityIntegration & MessagingNode.js, read from its artifacts

Destinations

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

Showing artifacts, examples and content with confirmed Node.js applicability. View All CAP

Overview

SAP SHIPS
@sap/cds

Resolves an SAP BTP destination in the runtime's own fetch client, so a production call no longer has to go through the SAP Cloud SDK. Added in CAP Node.js 10.1 and marked beta, covering proxy type Internet with NoAuthentication, BasicAuthentication or OAuth2ClientCredentials; a destination using any other authentication type is served by @sap-cloud-sdk/http-client once that package is installed.

SourceCAP Release Notes — September 2026checked

A Node.js coverage assessment has not been written. View all flavors

THE COMMUNITY ADDS
cdse

Connects to a destination by name from the CAP configuration and issues the outbound request with axios, with an X-CSRF-Token round trip available on writes.

Sourcecdse — READMEchecked
@sapmentors/cds-scp-api

Resolves a destination by name from the CAP service and makes the call against it, so the endpoint, the credentials and the on-premise tunnel stay in the destination configuration.

SourceCDS-SCP-API Node Module — README, what the module provideschecked

A Node.js coverage assessment has not been written. View all flavors

Licence1

LicenceSAP Developer License Agreement 3.2 CAP§ 1AlwaysA destination used by a covered CAP application sends SAP product data to a non-SAP product rather than only addressing a remote endpoint.
  • § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.

A destination is configuration, not the deciding boundary. The licence becomes material when the resulting data flow is extraction into a non-SAP product, so the target and purpose need review.

SAP Developer License Agreement 3.2 CAP →
SourceSAP Developer License Agreement 3.2 CAPchecked

Artifacts4

4 of 4 artifacts
ArtifactSignals
Packages3
@sap/cdsCAP Node.js runtime
Signals
none
@sapmentors/cds-scp-apiNode module for CAP calling external APIs through a destination
Signals
Quiet+1
cdseDestination resolution and axios calls from CAP configuration
Signals
Quiet
Services1
SAP Destination serviceNamed, credentialed addresses of other systems resolved at runtime
Signals
none

Seen working8

ArtifactSignals
Samples8
az-private-linky-capCAP project reaching S/4 via SAP BTP Private Link Service for Azure
No license
cap-ams-a2aApp-to-app setups between CAP Java and CAP Node.js under AMS and IAS
No license
cap-external-northwindCAP service serving Northwind's external OData Products as its own
none
cap-openaiCAP service actions calling OpenAI chat completions two ways
No license
cap-principal-propagationOn-premise ABAP OData V2 service read from CAP over Connectivity
No license
cap-rfcCAP Node.js action calling BAPI_EPM_BP_CREATE over RFC
No license
cap-uiMTA deploying CAP, HDI container and a Fiori elements app
none
SAP-samples/cap-service-integration-codejamCodeJam on consuming external services from a CAP project
none

Details

Coverage
statecore and community, CAP, Node.js, derived
domainIntegration & Messaging
also inBTP/BAIP, UI5
For your agent
Ref
capability:destinations
JSON
/capabilities/destinations.json
MCP
Connecting an agent