---
cuppy_hub: salesforce
cuppy_path: reference/orgs/orgs-and-editions.md
cuppy_section: docs
cuppy_doc: F3AP-D788
cuppy_doc_uuid: 35216e48-b5f8-4f48-a20b-2640d3143d74
cuppy_permalink: https://cuppy.io/salesforce/d/F3AP-D788
cuppy_version: 1
cuppy_updated: 2026-10-23T16:16:52.575Z
cuppy_canonical: https://cuppy.io/salesforce/docs/reference/orgs/orgs-and-editions
cuppy_mcp: https://cuppy.io/mcp
cuppy_body_sha256: 0c2c210cb55298c2733ee098fe56f4d13b766f410767e5da420647a98c28942d
# cuppy_body_sha256 is over the document body ALONE, excluding both generated blocks.
---


# Orgs for Agentforce work

## Which org

| Org | Use it for | Notes |
|---|---|---|
| **Developer Edition** (sign up at `developer.salesforce.com/signup`) | Building and demoing agents, prompts and Data 360 grounding for free | Since March 2025 it includes **Agentforce and Data 360** (**Data 360 is Data Cloud's new name**). It doesn't expire while you keep logging in. Since April 2026 it also includes Agentforce Vibes and Salesforce-hosted MCP servers |
| **Scratch org** (from a Dev Hub) | Repeatable, disposable builds in CI | Needs the AI features in its definition file (below). A Dev Hub that creates scratch orgs or sandboxes still needs a **connected app** for CLI authorization: `reference/auth/external-client-apps-and-oauth-flows.md` |
| **Sandbox** (`sf org create sandbox --name <name> --license-type Developer --target-org <prod>`) | Testing against a copy of production | Data 360 works in sandboxes once production has it: turn it on in the sandbox's **Data Cloud Setup** (sandboxes created before August 1, 2024 needed a refresh first). Partial Copy and Full sandboxes copy CRM data; Data 360 connections are copied **without their authorization**, so re-authorize each before ingesting. Move Data 360 configuration between orgs with data kits |
| **Production** | The real thing | Licences and consumption: family 10 |

The hub's reading: start in a Developer Edition. The agent-force demo's "live Dev org" is one, and it is the cheapest place to get Agentforce, Data 360 and the Agent API working together.

## Scratch org definition for Agentforce and Data 360

Trimmed to the AI-related parts of Salesforce's Coral Cloud sample app (Agentforce + Data 360); the full file also turns on Communities, Live Agent and Sites for its website:

```json
{
  "edition": "Developer",
  "features": ["CustomerDataPlatform", "Einstein1AIPlatform", "ServiceCloud", "EmbeddedServiceMessaging"],
  "settings": {
    "customerDataPlatformSettings": { "enableCustomerDataPlatform": true },
    "EinsteinGptSettings": { "enableEinsteinGptPlatform": true },
    "agentPlatformSettings": { "enableAgentPlatform": true }
  }
}
```

Create it with `sf org create scratch --definition-file config/project-scratch-def.json --alias agentforce --duration-days 7 --target-dev-hub <hub>`. Coral Cloud's README adds steps that the definition file can't do:
- wait for Data 360 provisioning to finish (**Data Cloud Setup** shows a **Get Started** button until it does);
- turn on Einstein, then switch on **Agentforce** under **Agentforce Agents**;
- install a **data kit** for the Data 360 parts.

## My Domain: the URL everything uses

Every org has a My Domain, such as `https://<my-domain>.my.salesforce.com`. Use it, not `login.salesforce.com`:
- for **client credentials** token requests, which fail on the generic login host;
- as the Agent API's `instanceConfig.endpoint` (family 5);
- as the `instance_url` your API calls go to.

JWT bearer logins can use `https://login.salesforce.com` (or `https://test.salesforce.com` for sandboxes) or the My Domain.

## Releases and API versions

| Release (docs release number) | API version |
|---|---|
| Spring '26 (260) | 66.0 |
| Summer '26 (262) | 67.0 |
| Winter '27 (264) | 68.0. The Apex Developer Guide marks Winter '27 (API 68.0) "Latest"; the SOAP API guide's selector still says "preview" |

The 264 = 68.0 row is from Salesforce's version selector. The other two rows follow the same two-per-version pattern (Spring '25 was 254 and API 63.0): the hub's reading.

**Read the org's own maximum** rather than assuming one:
- `sf org display --target-org <alias>` shows it (**Api Version**).
- `sf api request rest /services/data/ --target-org <alias>` lists every version the org serves.

Libraries have their own defaults. **jsforce defaults to 50.0**, so always set `version` (`guides/auth/server-to-server-from-typescript.md`).

Retirements that bite old integrations:
- SOAP `login()` retires in **Summer '27**.
- API versions 21.0–30.0 were retired in Summer '25.
- 31.0–40.0 become unsupported in Summer '27 and are retired in Summer '28.


---
<!-- cuppy -->
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.
<!-- /cuppy -->