--- title: Introducing a New Connect REST API Experience | daily.dev description: Salesforce is launching a redesigned Connect REST API reference documentation starting July 2026. The new experience consolidates previously fragmented pages... canonical: https://daily.dev/posts/introducing-a-new-connect-rest-api-experience-vzt9qfbc6 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Introducing a New Connect REST API Experience | daily.dev og:description: Salesforce is launching a redesigned Connect REST API reference documentation starting July 2026. The new experience consolidates previously fragmented pages... og:url: https://daily.dev/posts/introducing-a-new-connect-rest-api-experience-vzt9qfbc6 og:image: https://api.daily.dev/og/posts/vZt9qfBc6.png og:image:alt: Introducing a New Connect REST API Experience og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Introducing a New Connect REST API Experience **[Salesforce Developers Blog](https://daily.dev/sources/salesforcedevs)** · 5 min read · 2 upvotes · 0 comments ## Summary Salesforce is launching a redesigned Connect REST API reference documentation starting July 2026. The new experience consolidates previously fragmented pages into a single unified page with a three-column layout showing resources, details, and request/response examples side by side. The reference now follows the OpenAPI Specification, enabling downloads for use with AI agents or code generation. Version information is now inline throughout the page rather than requiring a version dropdown selection. Key changes include clickable endpoint paths for copying full URLs, field type patterns using regex, and the removal of deep-linking to standalone request/response body pages. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What changed in the Salesforce Connect REST API documentation starting July 2026? Salesforce replaced its legacy multi-page reference docs with a single unified three-column reference page covering the core Connect REST API and related families like Agentforce, Chatter, CMS, Commerce, Experience Cloud, Files and Folders, and Personalization. The new page shows resources, request bodies, and response bodies together, is built on the OpenAPI Specification, and replaces per-version snapshots with inline version notes. _Developers tracking Salesforce API doc changes can follow updates like this on daily.dev._ ### Can I still deep-link to a specific request or response body in the new Salesforce Connect REST API docs? No, direct deep-linking to a request or response body is no longer possible because those bodies are no longer separate standalone pages. Instead, link to the operation itself, and the associated request and response body will appear alongside it on the unified reference page. _Teams updating internal doc links after API reference redesigns can catch such breaking changes on daily.dev._ ### Is the new Salesforce Connect REST API reference documentation based on OpenAPI? Yes, the redesigned reference follows the OpenAPI Specification (OAS), the industry standard for describing REST APIs. Each API family's reference page includes a Download button to grab its OpenAPI spec file, which can be used with AI agents or code generation workflows. _Developers evaluating OpenAPI-based tooling for Salesforce integrations can follow such updates on daily.dev._ ## Similar posts on daily.dev - [Introducing the New Lightning Component Reference](https://daily.dev/posts/introducing-the-new-lightning-component-reference-kvbwuzwid) · Salesforce Developers Blog · 1 upvotes · 0 comments - [Pulumi Cloud REST API Docs, Now Generated from OpenAPI](https://daily.dev/posts/pulumi-cloud-rest-api-docs-now-generated-from-openapi-mfj8xkvl4) · Pulumi · 0 upvotes · 0 comments - [The Salesforce Developer’s Guide to the Winter ’27 Release](https://daily.dev/posts/the-salesforce-developer-s-guide-to-the-winter-27-release-aijafpfto) · Salesforce Developers Blog · 3 upvotes · 0 comments - [6 Ways Traditional API Design Has Changed Forever](https://daily.dev/posts/6-ways-traditional-api-design-has-changed-forever-aa4diizvs) · Nordic APIs · 0 upvotes · 0 comments - [REST API version 2026-03-10 is now available](https://daily.dev/posts/rest-api-version-2026-03-10-is-now-available-yuwv2fnu4) · GitHub Changelog · 59 upvotes · 2 comments --- Tags: [#backend](https://daily.dev/tags/backend), [#rest-api](https://daily.dev/tags/rest-api), [#salesforce](https://daily.dev/tags/salesforce), [#openapi](https://daily.dev/tags/openapi) [View this post on daily.dev](https://daily.dev/posts/introducing-a-new-connect-rest-api-experience-vzt9qfbc6) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Introducing a New Connect REST API Experience","url":"https://daily.dev/posts/introducing-a-new-connect-rest-api-experience-vzt9qfbc6","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/introducing-a-new-connect-rest-api-experience-vzt9qfbc6"},"datePublished":"2026-07-09T15:02:07.578Z","dateModified":"2026-09-14T08:18:00.746Z","description":"Salesforce is launching a redesigned Connect REST API reference documentation starting July 2026. The new experience consolidates previously fragmented pages...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e46922d4cdcfbde58800b4dd5faee24a?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e46922d4cdcfbde58800b4dd5faee24a?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Salesforce Developers Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Salesforce Developers Blog","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/662fb7dc7cd14ee59747ed58d75cf7c3","url":"https://daily.dev/sources/salesforcedevs"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/introducing-a-new-connect-rest-api-experience-vzt9qfbc6","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"backend,rest-api,salesforce,openapi","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Salesforce Developers Blog","item":"https://daily.dev/sources/salesforcedevs"},{"@type":"ListItem","position":3,"name":"Introducing a New Connect REST API Experience"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/introducing-a-new-connect-rest-api-experience-vzt9qfbc6#faq","mainEntity":[{"@type":"Question","name":"What changed in the Salesforce Connect REST API documentation starting July 2026?","acceptedAnswer":{"@type":"Answer","text":"Salesforce replaced its legacy multi-page reference docs with a single unified three-column reference page covering the core Connect REST API and related families like Agentforce, Chatter, CMS, Commerce, Experience Cloud, Files and Folders, and Personalization. The new page shows resources, request bodies, and response bodies together, is built on the OpenAPI Specification, and replaces per-version snapshots with inline version notes. Developers tracking Salesforce API doc changes can follow updates like this on daily.dev."}},{"@type":"Question","name":"Can I still deep-link to a specific request or response body in the new Salesforce Connect REST API docs?","acceptedAnswer":{"@type":"Answer","text":"No, direct deep-linking to a request or response body is no longer possible because those bodies are no longer separate standalone pages. Instead, link to the operation itself, and the associated request and response body will appear alongside it on the unified reference page. Teams updating internal doc links after API reference redesigns can catch such breaking changes on daily.dev."}},{"@type":"Question","name":"Is the new Salesforce Connect REST API reference documentation based on OpenAPI?","acceptedAnswer":{"@type":"Answer","text":"Yes, the redesigned reference follows the OpenAPI Specification (OAS), the industry standard for describing REST APIs. Each API family's reference page includes a Download button to grab its OpenAPI spec file, which can be used with AI agents or code generation workflows. Developers evaluating OpenAPI-based tooling for Salesforce integrations can follow such updates on daily.dev."}}]} ```