ServiceServiceA BTP service you subscribe to and bind, rather than install. It has plans and regions, not versions, and may deliver a product that lives outside the atlas.See every one →What this type is →by SAPby SAPPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →
SAP Destination service
Named, credentialed addresses of other systems, resolved at runtime — so an application holds no URL and no secret of its own, and the same code reaches a different system in every landscape.
Where it sits
Lives in
Provides
DestinationsCAPBTPDestinationsReaching 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.
Serves
Designs
Agentic AI & AI AgentsAgentic AI & AI Agentsdestination management for SAP cloud solutions, third-party applications and on-premise systemsAgentic Engineering for SAP BTP ExtensionsAgentic Engineering for SAP BTP ExtensionsConnectivityDesigning Event-Driven ApplicationsDesigning Event-Driven Applicationsbackend destination detailsGenerative AI on SAP BTPGenerative AI on SAP BTPbackend destination detailsIntegrating and Extending JouleIntegrating and Extending Joulecalls the Joule Function in the name of the userMultitenant SaaS Application using CAPMultitenant SaaS Application using CAPconnections to SAP and third-party systemsSAP Document AISAP Document AIoutbound integration
Before choosing this
Conditions
LicenceSAP Developer License Agreement 3.2 CAP§ 1from DestinationsA 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 →What it declares
Every artifact
- Type
- Service
- Origin
- By SAP
As a service
- Plans
- 1
- Regions
- 46
- Support component
- BC-CP-DEST-CFBC-CP-DEST-CF-CLIBSBC-CP-DEST-CF-TOOLS
Connections
Group by40 of 40 connections
NodeRelationBasis
Functional
DestinationsDestinationsReaching remote systems without addresses or credentials in the codeSAP and community, unassessed
provides
authored
provides Destinations
Reaching remote systems without addresses or credentials in the code
Technical
@sap/approuter@sap/approuterSAP's Node.js application router in front of business applicationssap official, btp
connected from
derived
connected from @sap/approuter
Reading the configuration of the destination a route forwards to, where the router's own environment does not define it.
“The approuter first looks for the destination name in the manifest.yaml file, and if not found, looks for it in the destination service.”
SAP's Node.js application router in front of business applications
@sapmentors/cds-scp-api@sapmentors/cds-scp-apiNode module for CAP calling external APIs through a destinationcommunity org, cap
connected from
derived
connected from @sapmentors/cds-scp-api
Reads the authentication, the proxy settings and the baseURL of the named destination, which is why the call site writes a relative URL.
“CDS-SCP-API will ignore the Axios config settings for the authentification, the proxy settings, and the baseURL. The CDS-SCP-API retrieves these settings from the SAP Cloud Platform Destination & Connectivity services.”
Node module for CAP calling external APIs through a destination
arc-1arc-1MCP server over the ADT REST API for ABAP objectsindependent, abap
connected from
derived
connected from arc-1
deployed as a Cloud Foundry app on SAP BTP
has the Destination service forward the MCP user's identity to the SAP system it reaches through a managed destination
“**Destination Service** — connect to SAP systems via managed destinations”“**Per-user SAP identity** — BTP Destination Service forwards the MCP user to SAP: Cloud Connector principal propagation for on-premise SAP, or `OAuth2UserTokenExchange` for BTP ABAP Environment”“### BTP Cloud Foundry Deployment
Deploy ARC-1 as a Cloud Foundry app on SAP BTP with full platform integration:”
MCP server over the ADT REST API for ABAP objects
calmcpcalmcpMCP server with read tools over the SAP Cloud ALM APIsindependent, btp
connected from
derived
connected from calmcp
run in BTP mode, where `CALM_DESTINATION_NAME` names the destination entry the server looks up at runtime
reads the OAuth2 client-credentials and the Cloud ALM API base out of a destination the deployment binds, instead of holding them in its own environment
“calmcp authenticates to Cloud ALM via a bound **Destination** (type OAuth2 client-credentials, URL = your Cloud ALM API base, e.g. `https://<tenant>.<region>.alm.cloud.sap/api`). Set `CALM_DESTINATION_NAME` to that destination's name.”“**`CALM_DESTINATION_NAME`** (default `SAP_CALM`) — the name of the destination *entry* the app looks up at runtime.”
MCP server with read tools over the SAP Cloud ALM APIs
SAP Document AISAP Document AIExtracts header fields and line items from business documentssap official, btp
connected from
derived
connected from SAP Document AI
reaches customer systems for outbound integration
“Outbound integration to customer systems uses the **SAP Connectivity service** and **SAP Destination service**.”
Extracts header fields and line items from business documents
@sapmentors/cds-scp-api@sapmentors/cds-scp-apiNode module for CAP calling external APIs through a destinationcommunity org, cap
needed by
derived
needed by @sapmentors/cds-scp-api
Holds the endpoint and the credentials the module resolves by name before it issues the request.
“Endpoint and Configuration using SAP Cloud Platform Destination and Connectivity services”
Node module for CAP calling external APIs through a destination
arc-mcp-hubarc-mcp-hubHub on SAP BTP putting several arc-1 instances behind one loginindependent, btp
needed by
derived
needed by arc-mcp-hub
one destination per backend, which both resolves the backend's URL and carries the `OAuth2JWTBearer` exchange that produces the per-user token
“`HUB_BACKENDS` | yes | JSON array of `{ name, destination, description? }`.”“exchanges it via a **BTP destination**”
Hub on SAP BTP putting several arc-1 instances behind one login
auth-samplesauth-samplesCAP services and a UI for trying role restrictions with mock usersindependent, cap
needed by
derived
needed by auth-samples
In production the imported products service is reached by the name of a destination rather than an address, and the MTA binds a destination instance on the lite plan to the service module.
“"destination": "products-srv",”“- name: salesorders-dest
type: org.cloudfoundry.managed-service
parameters:
service: destination
service-plan: lite”
CAP services and a UI for trying role restrictions with mock users
auth-transportauth-transportUI5 app and CAP service copying role collections between subaccountsindependent, btp
needed by
derived
needed by auth-transport
The source and the target subaccount are each reached through a destination that points at the Authorization and Trust Management API and carries the client credentials of that subaccount's service key.
“4. Create destinations pointing to Authorization and Trust Management API referencing the service keys”
UI5 app and CAP service copying role collections between subaccounts
az-private-linky-capaz-private-linky-capCAP project reaching S/4 via SAP BTP Private Link Service for Azureindependent, cap
needed by
derived
needed by az-private-linky-cap
The private hostname, the credentials and the PrivateLink proxy type are held in a destination named az-destinations, which the deployed application and the local hybrid profile both bind.
“Maintain your target on the deployed Destination service az-destinations”
CAP project reaching S/4 via SAP BTP Private Link Service for Azure
BTP CF MCP ServerBTP CF MCP ServerCloud Foundry V3 API on SAP BTP as MCP toolsindependent, btp
needed by
derived
needed by BTP CF MCP Server
the named address of the Cloud Foundry V3 API, `CF_API`, and the OAuth2 token handling behind every call
“BTP Destination configured for the CF V3 API (`CF_API`) with OAuth2 authentication”“Destination (lite) -- resolves the CF API endpoint and manages OAuth2 tokens”
Cloud Foundry V3 API on SAP BTP as MCP tools
btp-agentbtp-agentLangGraph agent and UI5 chat screen over four BTP MCP serversindependent, cap
needed by
derived
needed by btp-agent
the deployed MCP server URLs the agent's client is pointed at in production, created as instance destinations by the MTA
“In production the same configuration flips to destinations with the deployed URLs, and the chat service injects the caller’s JWT as a bearer token so the downstream MCP server authorises the user that actually asked the question.”“The MTA ships nine modules (approuter, CAP srv, UI5 chat, HANA deployer, and four MCP-server apps) and binds xsuaa, HANA HDI, destination, connectivity, html5-repo (host+runtime) and AI Core (extended plan).”
LangGraph agent and UI5 chat screen over four BTP MCP servers
cap-external-northwindcap-external-northwindCAP service serving Northwind's external OData Products as its ownindependent, cap
needed by
derived
needed by cap-external-northwind
How the remote service is reached once deployed: the project's own requires block names a destination instead of an address, and the repository does not set that destination up.
“"NorthWind": {
"kind": "odata",
"model": "srv/external/NorthWind",
"credentials": {
"destination": "NorthWind"
}
}”
CAP service serving Northwind's external OData Products as its own
Reports Assistant with SAP Document ManagementReports Assistant with SAP Document ManagementCAP agent writing reports into a shared SDM document workspaceindependent, cap
needed by
derived
needed by Reports Assistant with SAP Document Management
Named addresses for the model and the SDM API, which the project configures by destination name rather than by URL.
“Requires a SAP BTP Cloud Foundry environment with AI Core, Document Management,
Destination, XSUAA, and HTML5 Application Repository runtime services.”“set `cds.requires.llm.destinationName` and model.”
CAP agent writing reports into a shared SDM document workspace
SAP-samples/btp-ai-core-consumption-monitorSAP-samples/btp-ai-core-consumption-monitorCAP and React dashboard for SAP AI Core capacity unit consumptionsap official, btp
needed by
derived
needed by SAP-samples/btp-ai-core-consumption-monitor
a bound service instance the deployment needs, on the lite plan
“| Destination Service | lite | ✅ Yes |”
CAP and React dashboard for SAP AI Core capacity unit consumption
SAP-samples/btp-resource-consumption-monitorSAP-samples/btp-resource-consumption-monitorApp monitoring SAP BTP credit consumption with alerts on increasessap official, btp
needed by
derived
needed by SAP-samples/btp-resource-consumption-monitor
the runtime destination the Work Zone content package is mapped to
“- Destination service: lite”
App monitoring SAP BTP credit consumption with alerts on increases
SAP-samples/joule-a2a-agent-toolkitSAP-samples/joule-a2a-agent-toolkitSkills for building an A2A agent for Joule and deploying it to CFsap official, btp
needed by
derived
needed by SAP-samples/joule-a2a-agent-toolkit
a [SAP BTP](artifact:btp-destination) destination through which Joule reaches the deployed agent
“**BTP subaccount** with Cloud Foundry runtime, AI Core service, and Destination service”
Skills for building an A2A agent for Joule and deploying it to CF
@arc-mcp/xsuaa-auth@arc-mcp/xsuaa-authXSUAA authentication stack for an MCP server on SAP BTPindependent, btp
optionally used by
derived
optionally used by @arc-mcp/xsuaa-auth
the `./btp` entrypoint is used, which is the per-user principal propagation path; a server that only verifies bearer tokens never reaches it
the destination the entrypoint looks up with the verified user JWT to obtain the per-user tokens
“The `./btp` entrypoint maps the authenticated MCP user to their own SAP identity via the BTP Destination Service + Cloud Connector.”
XSUAA authentication stack for an MCP server on SAP BTP
@expertum/cap-email-plugin@expertum/cap-email-pluginAnnotation-driven mail on CAP entity lifecycle eventsindependent, cap
optionally used by
derived
optionally used by @expertum/cap-email-plugin
The graph kind is configured for Microsoft Graph.
Carries the OAuth2 client credentials the graph provider authenticates Microsoft Graph with, configured as a destination in the BTP subaccount.
“BTP Destination Service (for Microsoft Graph provider)”“The `graph` kind uses Microsoft Graph API via a BTP destination.”
Annotation-driven mail on CAP entity lifecycle events
abap2UI5/samples-stackabap2UI5/samples-stackabap2UI5 apps in front of OData, RAP, events and other technologycommunity org, abap
optionally used by
derived
optionally used by abap2UI5/samples-stack
the `10` AI samples run on an ABAP Cloud system
On ABAP Cloud the `10` package's transport class resolves a destination of the BTP subaccount through `cl_http_destination_provider=>create_by_cloud_destination`, with the communication arrangement for `SAP_COM_0276` in the ABAP environment.
“| **ABAP Cloud** | `Z2UI5_CL_SMPS_LLM_CLOUD` ([`src/10/02`](02)) — `cl_web_http_client_manager` on `cl_http_destination_provider=>create_by_cloud_destination` | a destination in the **BTP subaccount** (type HTTP, URL = scheme and host only, NoAuthentication), and in the ABAP environment the communication arrangement for **`SAP_COM_0276`** (destination service integration) |”
abap2UI5 apps in front of OData, RAP, events and other technology
calmcpcalmcpMCP server with read tools over the SAP Cloud ALM APIsindependent, btp
optionally used by
derived
optionally used by calmcp
run in BTP mode, which the MTA descriptor and `cf push` both set up
the destination service instance the deploy creates and binds, which holds the destination entry the server resolves
“This creates and binds `calmcp-xsuaa` (XSUAA), `calmcp-destination` (Destination) and `calmcp-logs` (Application Logs), and runs the HTTP transport with a `/health` check.”
MCP server with read tools over the SAP Cloud ALM APIs
cap-attachments-pluscap-attachments-plusCAP Node.js attachments plugin with database or cloud storageindependent, cap
optionally used by
derived
optionally used by cap-attachments-plus
A cloud storage backend is selected.
“bind the **Destination service** instance (which the plugin uses to look up your BTP destination at runtime)”
CAP Node.js attachments plugin with database or cloud storage
com.sap.cds:cds-feature-n8ncom.sap.cds:cds-feature-n8nTriggers n8n workflows from CAP Java through the outboxsap official, cap
optionally used by
derived
optionally used by com.sap.cds:cds-feature-n8n
n8n.destination is configured, for production deployments behind a proxy instead of a plain base URL.
“For production deployments — especially SAP managed n8n instances behind a proxy — you can configure a BTP destination instead of a plain base URL.”
Triggers n8n workflows from CAP Java through the outbox
com.sap.cds:cds-feature-remote-odatacom.sap.cds:cds-feature-remote-odataRemote Services for consuming OData V2 and V4 APIs in CAP Javasap official, cap
optionally used by
derived
optionally used by com.sap.cds:cds-feature-remote-odata
The remote service is configured with a destination rather than a service binding.
“If you're using the SAP BTP Destination Service, this is the name you used when you defined the destination there.”
Remote Services for consuming OData V2 and V4 APIs in CAP Java
LISALISAMCP server for reading and writing ABAP object translationsindependent, abap
optionally used by
derived
optionally used by LISA
deployed to SAP BTP Cloud Foundry, the production path
the destination that carries the principal propagation from the caller to the ABAP system
“- For production: an **SAP BTP** subaccount (Cloud Foundry) with XSUAA, Destination and Connectivity services.”“principal propagation via the Destination + Connectivity services”
MCP server for reading and writing ABAP object translations
SAP-samples/digital-manufacturing-extension-samplesSAP-samples/digital-manufacturing-extension-samplesSamples for the six extension types of SAP Digital Manufacturingsap official, digital-manufacturing
optionally used by
derived
optionally used by SAP-samples/digital-manufacturing-extension-samples
The dm-custom-api in-app service extension sample is deployed.
The sample service reaches the product's APIs through a named destination, SAP_DMC_DEFAULT_SERVICE_KEY, rather than a URL of its own.
“Below we are going to use destination SAP_DMC_DEFAULT_SERVICE_KEY to fetch the reason codes.”
Samples for the six extension types of SAP Digital Manufacturing
@cap-js/n8n@cap-js/n8nTriggers n8n workflows from a CAP applicationsap official, cap
used by
derived
used by @cap-js/n8n
Triggers n8n workflows from a CAP application
@salvatorela/cap-plugin-adobe-forms@salvatorela/cap-plugin-adobe-formsCAP plugin wrapping the SAP Forms service by Adobe on BTPindependent, cap
used by
derived
used by @salvatorela/cap-plugin-adobe-forms
CAP plugin wrapping the SAP Forms service by Adobe on BTP
@sap-cloud-sdk/connectivity@sap-cloud-sdk/connectivityDestination lookup and connectivity proxy for the Cloud SDKsap official, cap
used by
derived
used by @sap-cloud-sdk/connectivity
Destination lookup and connectivity proxy for the Cloud SDK
@sap-cloud-sdk/http-client@sap-cloud-sdk/http-clientHTTP client carrying a destination's credentialssap official, cap
used by
derived
used by @sap-cloud-sdk/http-client
HTTP client carrying a destination's credentials
@sap/approuter@sap/approuterSAP's Node.js application router in front of business applicationssap official, btp
used by
derived
used by @sap/approuter
Reading the destination a route forwards to, where that configuration is not written into the router's own environment.
“Destination configuration can also be read from `destination service`.”
SAP's Node.js application router in front of business applications
cap-oauth-destinationcap-oauth-destinationOAuth2UserTokenExchange destination declared in mta.yamlindependent, cap
used by
derived
used by cap-oauth-destination
OAuth2UserTokenExchange destination declared in mta.yaml
cap-openaicap-openaiCAP service actions calling OpenAI chat completions two waysindependent, cap
used by
derived
used by cap-openai
The production profile replaces the OpenAI url with a destination named `openai`, so once deployed the address comes from the destination rather than from the configuration.
“"[production]": { "credentials": { "destination": "openai", "path": "/v1" } }”
CAP service actions calling OpenAI chat completions two ways
cap-openapicap-openapiCAP Java service calling role collection APIs via a generated clientindependent, cap
used by
derived
used by cap-openapi
The generated client is constructed on a destination read at runtime, so the endpoint and the credentials of the API it calls come from there.
“HttpDestination destination = DestinationAccessor.getDestination("xsuaa").asHttp();”
CAP Java service calling role collection APIs via a generated client
cap-principal-propagationcap-principal-propagationOn-premise ABAP OData V2 service read from CAP over Connectivityindependent, cap
used by
derived
used by cap-principal-propagation
The remote service's credentials name a destination rather than an address, and the MTA binds a destination instance to the service module.
“"credentials": { "destination": "abaptrialPP", "path": "/sap/opu/odata/sap/EPM_REF_APPS_PO_APV_SRV" }”
On-premise ABAP OData V2 service read from CAP over Connectivity
cap-reuse-html5cap-reuse-html5Fiori elements app in the HTML5 Application Repository with cdm.jsonindependent, cap
used by
derived
used by cap-reuse-html5
The destination service holds both the instance destinations the content module creates and the subaccount destination that points at the content descriptor.
“- name: cap-reuse-html5-destination-service
type: org.cloudfoundry.managed-service
parameters:
config:
HTML5Runtime_enabled: true”
Fiori elements app in the HTML5 Application Repository with cdm.json
cap-rfccap-rfcCAP Node.js action calling BAPI_EPM_BP_CREATE over RFCindependent, cap
used by
derived
used by cap-rfc
The production profile reaches the ABAP system through a destination of the same name, and the MTA binds a destination instance to the service module.
“"[production]": {
"credentials": {
"destination": "abaptrialRFC"
}
}”
CAP Node.js action calling BAPI_EPM_BP_CREATE over RFC
cap-uicap-uiMTA deploying CAP, HDI container and a Fiori elements appindependent, cap
used by
derived
used by cap-ui
Both routes from the app to the CAP service are destinations: one created as an instance destination from the xsuaa service key, one in the destination service's own init_data.
“- name: cap-ui-destination-service
type: org.cloudfoundry.managed-service
requires:
- name: srv-api # Add
parameters:
config:
HTML5Runtime_enabled: true”
MTA deploying CAP, HDI container and a Fiori elements app
teched2025-AI163teched2025-AI163TechEd 2025 lab building a Joule Agent for Global Track and Tracesap official, btp
used by
derived
used by teched2025-AI163
how the pre-built Build actions reach the GTT system; the session provides two destinations by name.
“BTP Destinations (`gttwriteservice` & `gttGetService`) are available in SAP Build.”
TechEd 2025 lab building a Joule Agent for Global Track and Trace
Download
Learn more
Readings
- The ECC-to-CAP Starter KitThe ECC-to-CAP Starter KitA Devtoberfest 2026 session that builds a CAP service and a Fiori elements list report over an SAP ECC gateway service, on the argument that the CAP project, its contract and its UI survive a later move to SAP S/4HANA while the APIs behind them change. The service integration edge is the body of the demo: the metadata of the ECC flight service is saved as an EDMX file, imported with cds import so the model holds the structure and none of the data, projected read-only into a flight service, and one line of handler code forwards each read to ECC, with filtering, sorting and paging translated down to the older OData version the system speaks. The SAP Destination service edge covers the on-premise destination and the additional properties the walkthrough insists on, and the SAP Business Application Studio edge covers the full-stack dev space, the CAP project wizard, the service center plugin for picking up another OData service, and cds watch run under the profile that uses those credentials.published 2026-10-09Sebastiano Marchesini, YouTube — SAP Developers playlists
- Secure Service Consumption Across HyperscalersSecure Service Consumption Across HyperscalersSAP's design for a workload on SAP BTP that calls Amazon Web Services or Google Cloud services with short-lived credentials instead of stored keys, which is the outbound side of authentication: the BTP application proving who it is to another cloud. On AWS it draws two paths, an ID token from Identity Authentication in Cloud Identity Services exchanged through AWS STS for an IAM role, or an X.509 certificate kept in SAP Destination service and presented to IAM Roles Anywhere; on Google Cloud only the token path, through Workload Identity Federation and an impersonated service account. It is drawn for those two hyperscalers only, and Microsoft Azure has no page in it.published 2025-05-14SAP Architecture Center, SAP Architecture Center
Others providing
Compare all 13 on the Destinations page →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
- com.sap.cds:cds-feature-remote-odatacom.sap.cds:cds-feature-remote-odataA CAP Java feature for consuming remote OData V2 and V4 services as Remote Services, translating CQN queries into OData requests against a destination or a service binding.sap official, capRemote Services for consuming OData V2 and V4 APIs in CAP Java
- com.sap.cds:cds-integration-cloud-sdkcom.sap.cds:cds-integration-cloud-sdkA CAP Java feature that integrates the SAP Cloud SDK, so features such as remote OData and enterprise messaging resolve a destination or service binding and reach a remote REST-based service.sap official, capSAP Cloud SDK integration for remote REST services in CAP Java
- capire/s4capire/s4A pre-built integration package for SAP S/4HANA, holding the imported service definitions a CAP project would otherwise generate for itself.sap official, capPrebuilt SAP S/4HANA integration package for CAP projects
- cdsecdseResolves a destination from a CAP project's own configuration, then makes the outbound call with axios: the url, the method and the body are written at the call site.independent, capDestination resolution and axios calls from CAP configuration
- @sap/cds@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, capCAP Node.js runtime
- @sap-cloud-sdk/connectivity@sap-cloud-sdk/connectivityDestination lookup and the connectivity proxy — the package that turns a destination name into a reachable endpoint with credentials attached.sap official, capDestination lookup and connectivity proxy for the Cloud SDK
- @sap-cloud-sdk/http-client@sap-cloud-sdk/http-clientThe HTTP client that carries a destination's credentials, so an outbound call inherits the authentication rather than assembling it.sap official, capHTTP client carrying a destination's credentials
- @sap-cloud-sdk/odata-common@sap-cloud-sdk/odata-commonThe shared machinery under the SDK's OData and OpenAPI client generators; a dependency of the generated clients rather than something written against directly.sap official, capShared machinery under the Cloud SDK's OData and OpenAPI clients
- @sap-cloud-sdk/openapi@sap-cloud-sdk/openapiGenerated OpenAPI clients for the Cloud SDK, so a REST API described by a specification is called through typed functions.sap official, capGenerated OpenAPI clients for the Cloud SDK
- @sap-cloud-sdk/resilience@sap-cloud-sdk/resilienceTimeouts, retries and circuit breaking around a remote call, so one slow downstream system does not take the application with it.sap official, capTimeouts, retries and circuit breaking around remote calls
- @sap-cloud-sdk/util@sap-cloud-sdk/utilGeneral utilities shared across the Cloud SDK packages — a dependency, not a thing to reach for on its own.sap official, capGeneral utilities shared across the Cloud SDK packages
- @sapmentors/cds-scp-api@sapmentors/cds-scp-apiA Node module for CAP that calls an external API through a destination instead of a hardcoded endpoint, taking its address, credentials and on-premise tunnel from the SAP Destination and Connectivity services.community org, capNode module for CAP calling external APIs through a destination
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 viaSAP-samples/btp-service-metadata · btp-service-metadata
first seen in the atlas
ecosystem and domainbtp, integration-and-messaging
History in the atlas
- The destination is resolved by the router or the service, not by UI5 code, so the decision is made on the CAP and BTP doors.
- First seen.
For your agent
- Ref
artifact:btp-destination- JSON
- /artifacts/btp-destination.json
- MCP
- Connecting an agent