Query Data 360 Data using Query API

Use the Data 360 Query API to execute SQL queries against your Data 360 data using Connect REST endpoints and Apex methods. This API supports Data 360 SQL syntax and is optimized for all Data 360 use cases, from simple data retrieval to complex analytics and integration scenarios.

The Query API enables you to:

• Execute SQL queries against unified data model, data lake, profile, and engagement objects
• Process large result sets with built-in pagination
• Access data through REST endpoints or Apex methods
• Integrate Data 360 data into external applications and workflows

Choose the method that best fits your integration scenario.

Use the Connect REST API for most integration scenarios. It provides comprehensive features and integrates seamlessly with Salesforce Platform capabilities.

• Submit SQL Query

  • POST https://{dne_cdpInstanceUrl}/services/data/v64.0/ssot/query-sql
  • Execute SQL queries synchronously and asynchronously
  • Returns query ID for tracking and result retrieval. You can pass this queryId to result_scan to query the cached results in a subsequent SQL statement.

• Get SQL Query Status

  • GET https://{dne_cdpInstanceUrl}/services/data/v64.0/ssot/query-sql/{queryId}
  • Check query execution status and metadata
  • Monitor progress for long-running queries

• Get SQL Query Rows

  • GET https://{dne_cdpInstanceUrl}/services/data/v64.0/ssot/query-sql/{queryId}/rows
  • Retrieve query results with pagination support
  • Handle large datasets efficiently

• Cancel SQL Query

  • DELETE https://{dne_cdpInstanceUrl}/services/data/v64.0/ssot/query-sql/{queryId}
  • Cancel running queries to free up resources
  • Useful for query timeout management

The Data 360 REST API is an HTTP interface for executing SQL queries directly against your Data 360 data. It includes improved asynchronous execution, richer schema introspection, and consistent error reporting.

• Submit SQL Query

  • POST /api/v3/query
  • Execute queries in ASYNC or ADAPTIVE mode
  • Returns a queryId in the x-hyperdb-status response header for polling.

• Get SQL Query Status

  • GET /api/v3/query/{queryId}
  • Poll for query completion status
  • Returns status, row count, chunk count, and execution statistics.

• Get SQL Query Rows

  • GET /api/v3/query/{queryId}/rows
  • Retrieve results using offset-based pagination.

• Get SQL Query Chunks

  • GET /api/v3/query/{queryId}/chunks/{chunkId}
  • Retrieve results by chunk ID (preferred for large result sets).

• Get SQL Query Metadata

  • GET /api/v3/query/{queryId}/metadata
  • Retrieve output schema without fetching data rows.

• Cancel SQL Query

  • DELETE /api/v3/query/{queryId}
  • Cancel a running query and free server resources.

All Data 360 REST API endpoints return JSON by default. Apache Arrow IPC streaming format is also supported as a columnar binary format that reduces payload size and deserialization overhead, making it the better choice for large result sets. These endpoints support Apache Arrow as an alternative to JSON.

• Submit SQL Query
• Get SQL Query Rows
• Get SQL Query Chunks
• Get SQL Query Metadata.

To request an Arrow response, set the Accept header to application/vnd.apache.arrow.stream. The response body is a binary Arrow IPC stream rather than JSON. Use an Arrow-compatible client library (such as PyArrow or the Apache Arrow Java library) to read the stream.

For server-side integration within your Salesforce org, use Apex methods to query Data 360 data.

The sfsqlquery namespace provides object-oriented Apex classes for managing Data 360 SQL query execution with iterators and asynchronous queueables. It includes classes like SqlStatement, SqlRowIterator, Row, QueryHandle, and SqlQueueable for structured query lifecycle management. This namespace is the recommended approach for querying Data 360 data with Apex.

For workflows and usage patterns, see Query Data 360 Data with Apex.

The ConnectApi.CdpQuery class provides Apex methods that mirror the Connect REST API endpoints:

• Submit SQL Query - Execute SQL queries
• Get SQL Query Status - Check query status
• Get SQL Query Rows - Retrieve paginated results
• Cancel SQL Query - Cancel running queries

Authentication requirements vary by access method.

See OAuth 2.0 Client Credentials Flow for Server-to-Server Integration in Salesforce Help. All REST API calls require a valid OAuth 2.0 access token:

1Authorization: Bearer YOUR_ACCESS_TOKEN
2Content-Type: application/json

Apex methods use the current user’s session context and permissions automatically. See Getting Started with Apex in the Apex Developer Guide.

• Filter early: Use WHERE clauses to reduce data scanned
• Select specific columns: Avoid SELECT * statements
• Limit results: Use LIMIT for large datasets
• Optimize joins: Include key qualifiers and proper indexing
• Consider your data’s indexed field: Use the DMOs primary index or consider using a secondary index
• Implement asynchronous handling: Data 360 queries use both asynchronous and synchronous responses to optimize performance. Set up your application to handle both synchronous and asynchronous responses.
• Paginate result sets: Use the Connect API getSqlQueryRows endpoint with offset and rowLimit. You can query your createSqlQuery results for 24 hours without incurring more consumption charges. Because Data 360 stores results, getSqlQueryRows returns data faster than calls to createSqlQuery.

1-- ✅ Good: Use WHERE clauses to filter data
2SELECT ssot__FirstName__c, ssot__LastName__c
3FROM ssot__Individual__dlm
4WHERE ssot__CreatedDate__c >= '2024-01-01'
5AND ssot__IsActive__c = true
6LIMIT 1000
7
8-- ❌ Avoid: Selecting all data without filters
9SELECT * FROM ssot__Individual__dlm

Include key qualifier fields in table joins for optimal performance:

1SELECT * FROM ssot__ContactPointEmail__dlm email
2LEFT JOIN ssot__Individual__dlm individual
3ON email.ssot__PartyId__c = individual.ssot__Id__c
4AND email.KQ_PartyId__c IS NOT DISTINCT FROM individual.KQ_Id__c
5LIMIT 10

When key qualifiers aren’t configured on data lake object fields, the value is null. Use IS NOT DISTINCT FROM for null-safe joins.

• Query Services Status Codes - Error handling reference
• Get Started With Data 360 SQL - SQL tutorial and examples
• Data 360 Metadata API - Explore available data objects
• API Limits and Guidelines - Usage limits and best practices
• Salesforce Developers Blog: Boost Data 360 Integrations with the New Query Connect API