--- cuppy_hub: salesforce cuppy_path: changelog/2026-10-23-data360-official-api-reference-mirror.md cuppy_section: docs cuppy_doc: ZGZD-QSX8 cuppy_doc_uuid: be1dae54-cdf9-4acd-b500-572e047695bd cuppy_permalink: https://cuppy.io/salesforce/d/ZGZD-QSX8 cuppy_version: 1 cuppy_updated: 2026-10-23T16:16:52.575Z cuppy_canonical: https://cuppy.io/salesforce/docs/changelog/2026-10-23-data360-official-api-reference-mirror cuppy_mcp: https://cuppy.io/mcp cuppy_body_sha256: b9976bad933dfc808aa3771f32ac0ab87c82f669b3cf3a5222e4574db7df49df # cuppy_body_sha256 is over the document body ALONE, excluding both generated blocks. --- # Salesforce hub — Data 360 official API reference mirror (2026-10-23) ## What this release adds A verbatim mirror of Salesforce's Data 360 developer documentation under `reference/official/data360/`, keeping Salesforce's own path tree (hub standard: a source keeps its native tree; `reference/official/` holds a vendor's own documentation). The index is `reference/official/data360/index.md`; `_boot/START.md` and `reference/overview/families.md` (family 7) now point to it. | guide | folder | pages | |---|---|---| | Data 360 Query Guide — Query API reference (v1, v2, v3), Profile API, Metadata API, Calculated Insights, Data Graphs, Universal ID lookup, status codes, migration, and the Data 360 SQL reference (statements, data types, functions, external tables) | `data-cloud-query-guide/` | the Query API reference and SQL reference pages the guide's own table of contents lists | | Data 360 Connect REST API guide | `connectapi/` | the guide's overview and get-started pages | | Data 360 Developer guide — architecture, object model, quick start, APIs and SDKs, Postman, packaging and data kits, jobs, cost and usage, end-of-life notices | `data-cloud-dev/` | the guide's table of contents | The per-page counts are in the index, which is generated from the run; this note does not retype them. ## How the pages were read developer.salesforce.com answers HTTP 403 to every non-browser client (curl, fetch tools, datacenter addresses), and its own document-content endpoints answer the same. The pages were rendered through the r.jina.ai reader, which returns the rendered page as markdown; the reader's envelope (title, source, timestamp, warnings, trailing link list) was stripped and the body stored otherwise unchanged. The guides' tables of contents are not in the page text (they are client-rendered), so the page list came from the Internet Archive's snapshots of each guide's landing page, which carry the navigation tree. The generator is `work/tools/data360_mirror.py`; its record is `work/MIRROR-data360.json`. Every page carries: - `provenance[0].url` — the Salesforce page it mirrors, and the date it was read; - `freshness.verified_at` set to the page's published time, with `tier: asserted` because the platform lets an author write no stronger tier (the crawl itself is recorded in `provenance.note`) — the hub's own `reference/data360/` documents are the interpreted layer and remain `recheck`-dated separately; - `facets.service: data360`, `facets.trust: official`, `facets.source: developer.salesforce.com`, `facets.guide`; - a first line naming the source, so an agent reading the body knows the page is a mirror. The platform's address floor refuses email addresses in a body, so the generator replaces any address with `@`. ## What is deliberately left out - **The Connect REST API's OpenAPI viewer** (`connectapi/references/spec`, and its per-operation `?meta=` pages). It is rendered by a JavaScript component from a Swagger file that is not reachable at any address the run tried; the reader returns an empty page. The Query Connect API operations it describes are covered by the Query Guide pages and by the hub's own `reference/data360/object-model-and-apis.md`. - **The Data 360 Integration guide** (`data-cloud-int/`, about two hundred pages). It is per-connector setup documentation (one page per source system and data stream), not API reference. Owed to a later release if the hub takes on ingestion. - **Four SQL reference pages** named in the June 2026 table of contents that now answer 404 at Salesforce (`conditional`, `comparison`, `every`, `math`). The topics are covered by the sibling pages that remain. - One Connect API page (`references/about-sample-api/about-connect-api`) that renders only client-side and returned no text. ## Known limits - A mirror is as current as its read date. Salesforce's page is the authority; a fact that matters should be re-read there before it is relied on, and the page's `freshness.verified_at` says when this copy was taken. - The mirror doubles the hub's token count. The capacity allowance was raised for it; `hub-set-capacity.mjs --show` reads the live figures. - The pages are Salesforce's prose, not the hub's: they use "Data Cloud" and "Data 360" interchangeably (the rebrand was October 14, 2025) and some carry Salesforce's own cross-links, which resolve to developer.salesforce.com, not into the hub. --- 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.