Query API V1 Call Overview

The Query API V1 provides a powerful way to query and analyze data in Data Cloud. This API allows you to execute SQL queries against data streams, profile or engagement data model objects, and unified data model objects. The Query API V1 supports only synchronous calls, making it suitable for data extraction, external application integration, or interactive querying on the data lake.

  • SQL Support: Execute ANSI standard SQL queries against your Data Cloud data
  • Synchronous Processing: Get immediate results for your queries
  • Pagination Support: Use limit and offset parameters for controlled data retrieval
  • Flexible Querying: Query across data streams, profile, engagement, and unified data model objects
  • Browser Compatibility: Ideal for browser-based clients with pagination support

A newer version of the Query API is available. We recommend using Query API V2 to take advantage of GET calls in addition to POST calls, subsequent requests, and larger response sizes.
  • Data Cloud licenses must be provisioned for your org
  • Users must have appropriate roles and permissions assigned
  • Authentication requires a valid access token
  • Connected App must be properly configured
  • Maximum return limit of 49,999 rows per query
  • No explicit limit exists for:
    • SQL call length
    • Number of nested subqueries
    • Number of joins
    • Number of filters
    • Number of column projections
    • Specific data types (VARCHAR, DECIMAL, TIMESTAMP, etc.)
  • Pagination is supported via limit, offset, and orderby parameters:
    • When the done flag is true in the response, there are no more records to query
    • When the response is false, use orderby with offset to retrieve the next set of records
  • POST /api/v1/query
    • Executes SQL queries against Data Cloud data
    • Returns query results with metadata
    • Supports pagination and filtering
  • The API follows REST standards for consistency and ease of use
  • All API endpoints require proper authentication using an access token
  • Example URLs use {TSE} to represent your tenant-specific endpoint
  • Data access is subject to user permissions and role assignments