--- cuppy_hub: salesforce cuppy_path: reference/official/data360/connectapi/guide/set-up-the-collection.md cuppy_section: docs cuppy_doc: W593-NVA2 cuppy_doc_uuid: 028098b1-092f-4eaa-b69f-106d439f708e cuppy_permalink: https://cuppy.io/salesforce/d/W593-NVA2 cuppy_version: 1 cuppy_updated: 2026-10-23T16:16:52.575Z cuppy_canonical: https://cuppy.io/salesforce/docs/reference/official/data360/connectapi/guide/set-up-the-collection cuppy_mcp: https://cuppy.io/mcp cuppy_body_sha256: b685f7ee5ff97bfd7ab4e4d79aa020328eaffde38b08893ccc67de403d37cf91 # cuppy_body_sha256 is over the document body ALONE, excluding both generated blocks. --- > Mirror of (Salesforce, Data 360 Connect REST API Guide), read 2026-10-23. Salesforce's own page is the authority; this copy exists because that site refuses non-browser readers. ## Set Up the Connect API Postman Collection To set up the Salesforce Data 360 Connect REST API Postman collection, fork, configure, and authenticate the collection. You can follow along in a video that walks you through the steps of setting up Postman. See [Data 360 Connect APIs and Postman Quick Start Video](https://salesforce.vidyard.com/watch/cTet8JYsu9zd6QsqxFkkwN). The Postman setup and authentication instructions for Data 360 Connect APIs are similar to the ones for the Salesforce Platform APIs in [Quick Start: Connect Postman to Salesforce](https://trailhead.salesforce.com/content/learn/projects/quick-start-connect-postman-to-salesforce) in Trailhead. 1. Use the Postman web app or download and install the [Postman desktop app](https://www.postman.com/downloads/). 2. Fork [the collection](https://www.postman.com/salesforce-developers/workspace/salesforce-developers/collection/12721794-fa94cb66-3cb1-41e1-ad4b-7c0ec34bb430) in Postman. 3. On the collection’s Variables tab, assign a value to the `loginUrl` collection variable based on your Salesforce org type. * (Recommended) Use the My Domain login URL for your org. * Keep `https://login.salesforce.com` if you are using a production org, Trailhead Playground, or Developer Edition org. * Use `https://test.salesforce.com`for sandboxes or scratch orgs. 1. Save your changes. 2. On the collection’s Authorization tab, click **Get New Access Token**. 3. When prompted, log in to your Salesforce org and allow access to Salesforce APIs Collection for Postman. 4. From the token details view, copy the value of the `instance_url` field. 5. Click **Use Token**. 6. On the collection’s Variables tab, replace the `dne_cdpInstanceUrl` current value with the value copied from the `instance_url` field. 7. Save your changes. Postman parses the response body and sets the variables for `dne_cdpAuthToken` and `dne_cdpInstanceUrl` that are used in Connect API requests. --- You are reading one file. The same content is free over MCP at https://cuppy.io/mcp with no signup: ranked search across all 376 documents in this hub, the merged view when you work in a layer, known workarounds matched to the error you hit, and depth control so you spend tokens on what you need. Start with the `_hello` tool. How to connect: https://cuppy.io/salesforce/ Something wrong in this document? Report it with the `session feedback` tool on the same endpoint.