BTP Destination Configuration for API Testing
A destination in SAP Business Technology Platform (SAP BTP) is a configuration object that defines the connection parameters needed to enable communication between an application and a remote service or system. Developers create and manage destinations in the SAP BTP cockpit to connect to external resources such as on-premise systems, OData services, or other subaccounts. Destinations can be configured to support various authentication methods — such as SAML assertion authentication — and connectivity scenarios, including on-premise connectivity via HTTP or RFC.
Tutorials that teach this
- Tutorial Create Sales Order Action Project in SAP Build Actions
- Tutorial Setup Connectivity to CAP Service
- Tutorial Set Up Prerequisites for SAP Build CodeJam
- Tutorial Test the Business Rules API from SAP API Business Hub
- Tutorial Install a Mock Server in the SAP BTP, Cloud Foundry Runtime
- Tutorial Create Action Project for simple CAP Service in SAP Build Actions
- Tutorial Set Up Postman to Call Service Ticket Intelligence APIs
- Tutorial Create a Destination to Connect Google Drive
Docs explaining this concept
- Doc Cloud Controller Access Destination
- Doc Configure Consumer Subaccount
- Doc Configuring SAML Assertion Authentication
- Doc Create Destinations
- Doc Create a Destination
- Doc Create a Destination
- Doc Creating a Destination for Cross-Subaccount Communication
- Doc Creating a Destination to the ABAP System for SAP Business Application Studio
Prerequisites
- Concept SAP S/4HANA Cloud system connectivity and data retrieval No concept was provided, and the available source snippets contain only tutorial titles without substantive content to ground a definition. A meaningful, source-grounded definition cannot be written without a named concept and supporting source material.
- Concept SAP BTP Connectivity Configuration The concept name was not provided and cannot be determined from the available sources. The sources reference integrating on-premise systems with SAP BTP using the [Cloud Connector](https://help.sap.com/docs/btp/sap-business-technology-platform/c95327fbed6c4efeb1855f12f826301d?locale=en-US&state=PRODUCTION&version=Cloud) to enable communication from cloud applications to on-premise back-end systems, but without a defined concept name, a precise reference definition cannot be written. Please provide the concept name to proceed.
- Concept SAP Gateway Configuration A **Service Group** is a logical grouping of related OData services in SAP that a developer publishes together to make them accessible for consumption. Based on the tutorial "Publish Service Group," developers use this concept to activate and expose their services so that client applications can discover and connect to them.
- Concept SAP BTP Account Model (Global Accounts, Subaccounts, Spaces) The concept name provided is "undefined," which does not correspond to a identifiable SAP developer concept. Based on the available sources — which cover topics such as global account administration, subaccount creation, the Cloud Foundry environment, and SAP BTP account management — there is insufficient information to produce a grounded definition for a concept labeled "undefined." Please provide a valid SAP concept name so an accurate and source-grounded definition can be written.
- Concept SAP BTP Subaccount and Entitlement Setup The provided sources do not contain sufficient information to define this concept. The concept name is "undefined" and none of the source snippets supply grounded content that could be used to write an accurate, sourced definition.
- Concept Business Process Automation fundamentals
- Concept SAP S/4HANA Cloud Integration The concept provided is **undefined** — no valid concept name was supplied for this entry. A definition cannot be written without a clearly identified concept to describe, and the available source snippets do not converge on a single, nameable SAP developer concept. Please provide a specific concept name so that an accurate, source-grounded definition can be authored.
- Concept BTP Service Entitlements Configuration The concept name is missing or undefined, so a precise definition cannot be provided. Based on the available sources, the provided snippets cover topics such as [SAP BTP trial account setup](https://help.sap.com/docs/btp/sap-business-technology-platform/fa5deb9cc4be4ca58070456cd2c47647?locale=en-US&state=PRODUCTION&version=Cloud), free service plans, the btp CLI, Kyma environment management, and [account administration via the SAP Cloud Management Service APIs](https://help.sap.com/docs/btp/sap-business-technology-platform/17b6a171552544a6804f12ea83112a3f?locale=en-US&state=PRODUCTION&version=Cloud), but no specific concept is identified for definition. Please provide a valid concept name to generate an accurate reference definition.
- Concept Deploying CAP Applications to SAP BTP The concept name was not provided (marked as "undefined"), and the supplied source snippets — one covering securing a CAP application with SAP Cloud Identity Services and another covering deploying an SAP SuccessFactors extension database to SAP HANA Cloud — do not contain enough shared or specific detail to reliably define a single, identifiable SAP developer concept. A meaningful and source-grounded definition cannot be written without a valid concept name and supporting snippet content.
- Concept Custom Business Object Logic Implementation in SAP S/4HANA Cloud The concept name was not provided (received "undefined"), so a definition cannot be accurately produced. Please supply a valid SAP developer concept name so that a grounded, accurate definition can be written from the available source snippets.
- Concept OData CRUD Operations (Create and Update) The concept name is not defined in the provided sources, which cover SAP Git repository management API operations — such as [creating branches](https://help.sap.com/docs/btp/sap-business-technology-platform/a9ce22e685144dc88894067ead3b2778?locale=en-US&state=PRODUCTION&version=Cloud), clones, pulls, tags, and execution logs — all exposed via the `MANAGE_GIT_REPOSITORY` OData service. Developers use these endpoints to programmatically manage Git-based source code repositories on SAP Business Technology Platform. Without a defined concept name, no further specific definition can be provided based solely on the available sources.
- Concept SAP BTP ABAP Environment (Steampunk) The concept name provided is "undefined," and the supplied sources do not contain a definition or description of a concept by that name. Based on the available source snippets — which cover topics such as the [XCO Library](https://help.sap.com/docs/btp/sap-business-technology-platform/c154dffe892b4d9ea4566722f0bcd5f1?locale=en-US&state=PRODUCTION&version=Cloud), ATC configurations, abapGit, and the Cloud Connector — no grounded definition can be written for an "undefined" concept. Please provide a valid SAP developer concept name so an accurate, source-grounded definition can be produced.
- Concept Communication Arrangement in SAP BTP ABAP Environment The concept name is not defined in the provided sources, and the available source snippets do not contain sufficient shared context to identify and describe a single, specific SAP developer concept. A meaningful, source-grounded definition cannot be produced.
- Concept Service Bindings and Service Keys The concept name is missing or undefined, so a precise definition cannot be provided. Based on the available source, the [SAP SaaS Provisioning Service](https://help.sap.com/docs/btp/sap-business-technology-platform/ed08c7dcb35d4082936c045e7d7b3ecd?locale=en-US&state=PRODUCTION&version=Cloud) provides APIs that developers use to manage multitenant applications on SAP Business Technology Platform. These APIs allow developers to handle the lifecycle of multitenant SaaS solutions, such as provisioning and managing subscriptions across multiple tenants.
- Concept SAP BTP Service Instance and Service Key Creation The concept provided is `undefined`, and the supplied sources do not contain sufficient content to ground a meaningful definition of any specific SAP developer concept. Without a valid concept name or substantive source snippets, a documentation-quality definition cannot be written accurately or responsibly.
- Concept SAP Business Technology Platform [SAP Business Technology Platform (SAP BTP)](https://help.sap.com/docs/btp/sap-business-technology-platform/6a2c1ab5a31b4ed9a2ce17a5329e1dd8?locale=en-US&state=PRODUCTION&version=Cloud) is an integrated offering that enables developers to turn data into business value by building, extending, and integrating applications in the cloud. It brings together capabilities such as database and data management, analytics, application development, automation, and integration into a single platform. Developers use SAP BTP to compose business processes, extend existing SAP solutions, and connect data and processes across an organization using the [basic platform concepts](https://help.sap.com/docs/btp/sap-business-technology-platform/73beb06e127f4e47b849aa95344aabe1?locale=en-US&state=PRODUCTION&version=Cloud) such as accounts, environments, and services.
- Concept Cloud Integration and Connectivity SAP Private Link Service enables private connectivity between SAP BTP and services hosted on hyperscaler infrastructure, such as Google Cloud, without routing traffic over the public internet. A developer uses it to securely connect SAP BTP applications to Google Cloud services via [Google Cloud Private Service Connect](https://cloud.google.com/vpc/docs/private-service-connect), keeping network traffic within a private network boundary.
- Concept OAuth 2.0 Client Credentials Retrieval The provided sources do not contain sufficient information to define the concept "undefined." The sources cover topics such as Communication Arrangements, audit log access, credential retrieval, and API configuration on SAP BTP, but none of them define or describe a concept explicitly named "undefined." A reliable definition cannot be grounded solely in the provided snippets.
- Concept SAP BTP Fundamentals and Platform Navigation
- Concept Key User Extensibility in SAP S/4HANA Cloud The provided sources do not contain sufficient information to define a concept named "undefined." The sources cover topics such as transporting configurations, business event log data, CDS views, BAdI definitions, and tenant business types in SAP BTP and SAP S/4HANA Cloud, but none of them describe or reference a concept called "undefined."
- Concept SAP BTP Cockpit The concept name was not provided and the supplied source snippets do not define or describe a single, identifiable SAP developer concept — they cover a range of unrelated SAP BTP topics such as Kyma environment setup, Cloud Foundry org deletion, subaccount management, and service instances. A focused definition cannot be grounded solely in these sources without a clearly stated concept to define.
- Concept SAP BTP Communication Management (Scenario, System, Arrangement) The provided sources do not contain sufficient information to define the concept "undefined." The sources reference SAP BTP integration services such as [Certificates - Read Integration](https://help.sap.com/docs/btp/sap-business-technology-platform/10010aed8eac402184a84c222ebe75f2?locale=en-US&state=PRODUCTION&version=Cloud) and [Communication Arrangement - Read Integration](https://help.sap.com/docs/btp/sap-business-technology-platform/3ccd9a56e00441de93d8b519861dc56d?locale=en-US&state=PRODUCTION&version=Cloud), but none of them define or describe a concept named "undefined." No definition can be responsibly produced from the available source material.
- Concept SAP Destination Service Configuration The concept name is not defined in the provided sources, so a grounded definition cannot be written. The sources cover related topics such as [inbound communication via principal propagation](https://help.sap.com/docs/btp/sap-business-technology-platform/387b3deb12474762b593d4b1f2b392ad?locale=en-US&state=PRODUCTION&version=Cloud), OAuth 2.0 SAML Bearer Assertion Grant, client certificate authentication, and [routing via destination](https://help.sap.com/docs/btp/sap-business-technology-platform/97d7a02cd6fd4f579fd96f41ee0d0c1d?locale=en-US&state=PRODUCTION&version=Cloud) in the ABAP environment on SAP BTP, but without a defined concept name, no accurate definition can be produced from these snippets alone.
- Concept SAP S/4HANA Cloud Public Edition integration The concept is not defined in the provided sources. No source snippets contain sufficient information to write a grounded, accurate definition for an undefined concept.
- Concept SAP BTP trial and free tier account setup The concept name was not provided (marked as "undefined"), and the supplied sources do not converge on a single, clearly identifiable SAP developer concept. The sources reference a variety of topics — [Trial Accounts and Free Tier](https://help.sap.com/docs/btp/sap-business-technology-platform/046f127f2a614438b616ccfc575fdb16?locale=en-US&state=PRODUCTION&version=Cloud) and [Getting Started with SAP BTP](https://help.sap.com/docs/btp/sap-business-technology-platform/144e1733d0d64d58a7176e817fa6aeb3?locale=en-US&state=PRODUCTION&version=Cloud) — without a shared concept to define. A valid concept name is required to produce an accurate, grounded definition.
- Concept SAP Cloud Connector Setup and Configuration The concept name provided is "undefined," and the supplied sources do not contain a definition or description of a concept by that name. Based on the available source snippets — which cover topics such as [Communication Systems](https://help.sap.com/docs/btp/sap-business-technology-platform/e695a4a640a9455f9a3e18675d7084d0?locale=en-US&state=PRODUCTION&version=Cloud), communication arrangements, and integration reference architectures — there is insufficient grounding to produce an accurate definition. Please provide a valid SAP developer concept name and relevant source snippets to generate a definition.
- Concept CAP service development The concept provided is **undefined** and no valid concept name was supplied. Without a specific SAP developer concept to define, and with the available sources covering topics such as CAP services, SAP Build Actions, SAP Business Application Studio, and SAP SuccessFactors extensions, it is not possible to generate an accurate, source-grounded definition. Please provide a valid concept name so a precise definition can be written.
- Concept OAuth2 Client Credentials Grant Flow The provided sources do not contain sufficient information to define a specific, identifiable SAP developer concept — the concept name is listed as "undefined" and the source snippets cover a broad range of unrelated topics (OAuth2 Proxy, JWT security, API calls, service instances, and various tutorials) without converging on a single definable concept. A meaningful, source-grounded definition cannot be produced.
- Concept Custom Inbound API Creation in SAP S/4HANA Cloud A **Communication Arrangement** is a configuration object in SAP BTP's ABAP Environment and SAP S/4HANA Cloud that defines how two systems communicate by linking a communication scenario to a communication system and user. Developers use it to set up inbound and outbound integrations — for example, connecting the ABAP Environment with SAP S/4HANA Cloud — and can manage arrangements programmatically via the [Communication Arrangement - Read and Write Integration](https://help.sap.com/docs/btp/sap-business-technology-platform/f7c8929df1234eb6bd221a41ad6feac8?locale=en-US&state=PRODUCTION&version=Cloud) service. Arrangements can also be provisioned automatically using [YAML or JSON descriptor files](https://help.sap.com/docs/btp/sap-business-technology-platform/80a7613a0d2346b6ac93fcdbb2489de8?locale=en-US&state=PRODUCTION&version=Cloud), enabling automated setup as part of deployment pipelines.
- Concept SAP BTP Cloud Foundry Space Configuration The concept name provided is "undefined," and the supplied sources do not contain a definition or description of a specific, identifiable SAP developer concept that can be accurately and exclusively grounded in the given snippets. A reliable definition cannot be produced without a valid concept name and supporting source content.
Concepts that build on this
- Concept API Integration in SAP Build
- Concept Application Frontend Service Deployment for HTML5 Apps
- Concept Content Federation from SAP S/4HANA to SAP Build Work Zone
- Concept SAP Business Application Studio Setup
- Concept SAP Fiori UI Development
- Concept SAP BTP Service Instance and Service Key Creation
- Concept Role Collection Assignment
- Concept SAP Destination Service Configuration
- Concept SAP Build Process Automation Integration with SAP BTP ABAP Environment
- Concept Integrating cloud and on-premise applications
- Concept SAPUI5 App Integration with SAP Launchpad Service
- Concept OAuth2 User Token Exchange Authentication
- Concept Mock Server Deployment on SAP BTP Cloud Foundry
- Concept Cross-Domain Mapping Configuration for SAP Document Management Service
- Concept WebIDE Destination Properties
- Concept SAP Build Work Zone configuration
- Concept SOAP Web Service Consumption in Node.js
- Concept SAP Fiori Launchpad Catalog Management
- Concept SAP Build Actions Project Creation and Management
- Concept SAP Build Process Automation workflow design
- Concept SAP Business Client Cloud Launchpad Configuration
- Concept Central launchpad entry point setup
- Concept Web Dynpro ABAP App Integration in SAP Build Work Zone
- Concept SAP Cloud Transport Management Service
- Concept OData service consumption
- Concept SAP Business Rules Service Deployment to Cloud Runtime
- Concept SAP Content Agent Service Export Connection Setup
- Concept Cloud Foundry deployment
- Concept Connecting Joule to SAP business systems
- Concept Trust configuration between SAP Cloud Identity Services and SAP BTP