Destination Anywhere

The REST client for SAP BTP developers.
Send HTTP and OData requests straight from VS Code — with zero-config destination resolution.

dest:// for BTP subaccount destinations  ·  mdk:// for Mobile Services app destinations  ·  Variables & environments  ·  Sidebar browser  ·  On-premise support

Why Destination Anywhere?

You're coding in VS Code, you need to test an API call against your BTP backend, and suddenly you're out of your editor — opening the BTP cockpit to look up a destination URL, switching to Postman to craft the request, grabbing a bearer token from another tool, and hoping it's still valid by the time you paste it in. Every round-trip breaks your flow.

Destination Anywhere keeps you where you already are. Type dest://MY_DESTINATION/path in a .dest file, press Cmd+Alt+R, and the extension resolves the real URL, handles authentication, and shows you the response — without ever leaving VS Code.

No cockpit. No Postman. No token juggling. Just your editor.

Write a request, click Send, get the response. That's it.

From Install to First Request

Here's what happens the first time you open the extension — no setup guide needed, the sidebar walks you through it.

1. You're not logged in yet

Open the Destination Anywhere panel in the sidebar. If you're not logged in to Cloud Foundry, the extension tells you immediately and offers a one-click login button.

The sidebar detects your CF login state automatically.

2. Log in without leaving VS Code

Click Login with CF Tools and the CF sign-in form opens right inside VS Code. Enter your SSO passcode or credentials — no terminal needed.

CF Tools sign-in, right inside VS Code. SSO passcode or credentials — your choice.

3. No Destination Service? No problem.

Don't have a Destination Service instance? Most SAP BTP projects already have one — if yours does, the extension reuses it automatically and you'll never see this step. If not, here's why you need one: Destinations in SAP BTP are configured at the subaccount level in the BTP cockpit — they exist independently of any service instance. But the only way to read those destinations programmatically is through the Destination Service REST API. That API requires OAuth2 credentials (clientid, clientsecret, uri) which you can only obtain from a Destination Service instance and its service key in your CF space. So even though you never need an instance to create destinations, SAP BTP requires one just to query them. No instance, no credentials, no API access.

🔓 Full transparency — this extension and the router app are both open source. When you use on-premise destinations, Destination Anywhere deploys a small Express app to your CF space to relay requests through Cloud Connector. The entire source code — both the extension and the router app — is right here in this repository. The router is a single-file Express server (~100 lines) under router-app/ that you can read, audit, and even deploy manually yourself if you prefer:

cd router-app
# Edit manifest.yml with your service instance names, then:
cf push

See router-app/README.md for full manual deployment instructions. Nothing hidden, nothing proprietary — you're always in control of what runs in your CF space.

When you open the sidebar, the extension scans your CF space for any existing destination service instance. If you already have one — from another project, a managed app router, or manual setup — it reuses that. Nothing is created, nothing changes.

If no instance exists, the sidebar shows a "Create Destination Service instance…" link. Click it and the extension creates a lite plan instance named dest-anywhere-dest with a service key dest-anywhere-dest-key. This is free, one-time, and persists across sessions.

No Destination Service instance in this space — click to create one on the free lite plan.

Auto-provisioning in action: the extension creates a service instance, generates keys, and loads your destinations.

4. Browse your destinations

After provisioning, your BTP destinations appear in the sidebar tree. Each destination shows its type (Internet / OnPremise) and authentication method. Right-click any destination to insert a sample request into your .dest file or view its full configuration.

Right-click a destination: insert a ready-to-send request or inspect its properties.

One click inserts a complete request block with the right URL and headers.

5. Inspect destination details

Want to see what a destination resolves to? Click Destination Info and a panel opens showing the resolved URL, authentication type, proxy settings, and all configuration properties — with sensitive values masked.

Full destination properties at a glance — URL, auth type, token endpoint, and more.

Mobile Services (mdk://)

Destination Anywhere also supports SAP Mobile Services destinations via the mdk:// protocol. The first time you use it, the extension opens your browser for SAP BTP authentication — no extra confirmation needed.

Your browser opens to the SAP BTP login page. Once authenticated, the sidebar shows your Mobile Services apps and their destinations alongside BTP destinations. Use mdk://AppId/DestName/path to send requests:

### Equipment list via Mobile Services
GET mdk://SAM2405/DEST_SAM2405_PPROP/MyEquipments?$top=10&$format=json
Accept: application/json

Mobile Services authenticated (✓). Both dest:// and mdk:// requests in a single .dest file.

Usage Examples

BTP Destinations (dest://)

@system = MY_S4_SYSTEM
@service = /sap/opu/odata/sap/API_BUSINESS_PARTNER

### Metadata
GET dest://{{system}}{{service}}/$metadata
Accept: application/xml

### Business partners with filter + expand
GET dest://{{system}}{{service}}/A_BusinessPartner?$filter=BusinessPartnerCategory eq '1'&$expand=to_BusinessPartnerAddress&$top=5&$format=json
Accept: application/json

### Create a business partner
POST dest://{{system}}{{service}}/A_BusinessPartner
Content-Type: application/json

{
  "BusinessPartnerCategory": "1",
  "BusinessPartnerFullName": "Acme Corp"
}

Mobile Services Destinations (mdk://)

### Equipment list via MDK
GET mdk://SAM2405.SAM.WIN/DEST_SAM2405_PPROP/MyEquipments?$top=10&$format=json
Accept: application/json

### Create a notification
POST mdk://SAM2405.SAM.WIN/DEST_SAM2405_PPROP/Notifications
Content-Type: application/json

{
  "NotificationType": "PM",
  "Description": "Equipment failure reported via MDK"
}

Plain HTTP (no BTP)

@host = https://jsonplaceholder.typicode.com

### Get a post
GET {{host}}/posts/1

### Create a post
POST {{host}}/posts
Content-Type: application/json

{
  "title": "Hello from Destination Anywhere",
  "body": "Works with any HTTP endpoint.",
  "userId": 1
}

Variables & Environments

Define @var = value inline, use .env files, or configure per-environment variable sets in VS Code settings:

"destinationAnywhere.environmentVariables": {
  "dev":  { "system": "MY_DEV_SYSTEM",  "base": "/sap/opu/odata/sap" },
  "prod": { "system": "MY_PROD_SYSTEM", "base": "/sap/opu/odata/sap" }
}

Then in your .dest file:

### Switches based on active environment
GET dest://{{system}}{{base}}/API_BUSINESS_PARTNER/A_BusinessPartner?$top=5

Switch via Command Palette → Destination Anywhere: Switch Environment.

On-Premise Destinations

On-premise destinations route through SAP Cloud Connector, which is only reachable from inside Cloud Foundry. Destination Anywhere gives you two options:

Deploy the router from the sidebar: expand BTP Destinations, and click Deploy On-Premise Router. The extension provisions Connectivity and XSUAA service instances automatically.

Key Features

Commands

All commands are available in the Command Palette (Cmd+Shift+P / Ctrl+Shift+P):

Keyboard shortcut: Cmd+Alt+R / Ctrl+Alt+R → Send Request

Configuration

Requirements

• VS Code 1.87+
• CF CLI — for dest:// and mdk:// features (install guide)
• SAP BTP subaccount

Plain HTTP requests (https://...) work without CF CLI or any SAP services.

License

See LICENSE for details.