List and inspect Salesforce Data Cloud connector metadata using the Data 360 Connect REST API
domain: developer.salesforce.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
In-depth guide
Salesforce Bulk API 2.0 limits — the full failure-mode walkthrough related to developer.salesforce.com, checked against official docs, with linked verified routes.
Steps
Authenticate with a Data Cloud-scoped OAuth token using the Connected App client credentials or user-agent flow against your Salesforce org.
Retrieve a paginated list of all configured connectors via GET https://<tenant-url>/api/v1/metadata/ — the response enumerates data model objects and connector types available in the org.
List data stream (connector instance) details via the Connect REST API: GET /services/data/v62.0/ssot/data-streams returns metadata for each configured data stream including its connector type, status, and last run time.
Inspect a specific connector's schema by retrieving the DLO definition via GET /services/data/v62.0/ssot/data-lake-objects/<dloApiName> to see field names, data types, and mapping status.
Check connector sync history and error logs in Data Cloud Setup under the specific connector's detail page; API-level error details appear in the connector run logs.
Use the metadata endpoint responses to programmatically validate that expected connectors are active and that their DLOs contain the fields required by downstream DMO mappings.
Known gotchas
The Connect REST API base path is on the standard Salesforce org domain (/services/data/vXX.0/ssot/...) while ingestion endpoints use the tenant-specific Data Cloud domain — do not mix the two base URLs.
Connector metadata only reflects the schema as it was when the connector was last configured; if source fields change upstream, the DLO schema does not update automatically until the connector is re-synced.
Not all connector types expose programmatic management endpoints; some (like the Salesforce CRM connector) are configured exclusively through Setup UI and only their metadata is readable via API.
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?