Skip to main content
Sitecore Documentation
  • Learn
  • Downloads
  • Changelog
  • Roadmap
CDPCloud Portal
Sitecore CDP Developer Documentation
  • Developing with Sitecore CDP
    • Base URL
    • Response codes
    • REST API Guest v2.1
    • REST API Guest data extension v2.1
    • REST API Order v2.1
    • REST API Order contact v2.1
    • REST API Order consumer v2.1
    • REST API Order data extension v2.1
    • REST API Order item data extension v2.1
    • REST API Audience export
            • Differences between v2 and v2.1
            • Create a guest (legacy)
            • Retrieve guests (legacy)
            • Retrieve a guest (legacy)
            • Update a guest (legacy)
  1. Guest REST API v2 (legacy)
  1. REST APIs
  2. Legacy REST APIs
  3. Guest REST API v2 (legacy)
  4. Differences between v2 and v2.1 of the Guest and Guest data extension REST APIs

Differences between v2 and v2.1 of the Guest and Guest data extension REST APIs

If your instance of Sitecore CDP is using the 2.1 data model, we recommend that you upgrade to the Guest and Guest data extension REST APIs version 2.1.

Here's an overview of the main differences between version 2 and version 2.1:

v2

v2.1

URI paths

URI paths contain /v2/.

URI paths contain /v2.1/.

Endpoints for partial operations

  • Partial updates and partial deletions are not available.

  • Updates and deletions affect the entire resource. Because of this, you must use a different data extension name for each source system so that updates from one source system do not overwrite the data from a different source system.

  • New PATCH endpoints let you partially update guests and partially update data extensions. For example, you can update certain key-value pairs without affecting others.

  • A new DELETE endpoint lets you delete certain key-value pairs from a guest data extension without affecting others.

  • With partial operations, you no longer have to use a different data extension name for each source system, but we still recommend it as a best practice.

Endpoints for data extensions

Endpoints for data extensions use the less developer-friendly data extension reference.

More developer-friendly data extension endpoints let you specify the name of the data extension (see the possible values) in the request body when you create a data extension. You can then use that name in the URI of other endpoints to work with the data extension.

If you have suggestions for improving this article, let us know!

Documentation Assistant

This assistant uses AI to generate responses based on Sitecore documentation. While it has access to official sources, answers may be incomplete or inaccurate and should not be considered official advice or support.
Powered by
k
kapa.ai
Protected by reCAPTCHA

© Copyright 2026, Sitecore A/S or a Sitecore affiliated company.
All rights reserved.

Privacy policySitecore Trust CenterTerms of use