Virtual Assistant

Saturn EDCs (version 0.11.x and later) introduce a new protocol version and updated policy structure. These changes follow the Catena-X standard: <a href="https://catenax-ev.github.io/docs/next/standards/CX-0018-DataspaceConnectivity#26-participant-agent-management" rel="nofollow noopener noreferrer" target="_blank">CX-0018 Dataspace Connectivity v4.2</a><a href="https://catenax-ev.github.io/docs/next/standards/CX-0018-DataspaceConnectivity#26-participant-agent-management" rel="nofollow noopener noreferrer" target="_blank">.</a>

This update is important for Dataspace OS API users, as it affects how the Catalog is queried and how policies are configured for Saturn EDCs.

The Catalog must now be requested using the updated protocol version and endpoint structure:

POST: {{Consumer-Saturn-EDC-URL}}/management/v3/catalog/request { "@context": { "dct": "http://purl.org/dc/terms/", "edc": "https://w3id.org/edc/v0.0.1/ns/" }, "protocol": "dataspace-protocol-http:2025-1", "counterPartyAddress": "{{Provider-Saturn-EDC-URL}}/api/v1/dsp/2025-1", "counterPartyId": "did:web:portal-backend.beta.cofinity-x.com:api:administration:staticdata:did:{{Provider-BPNL}}", "querySpec": { "@type": "QuerySpec", "edc:offset": 0, "edc:limit": 500, "edc:filterExpression": [ ] } }

The following updates apply compared to previous (Jupiter) EDC versions:

- New value: <code>"dataspace-protocol-http:2025-1"</code>
- Replaces Jupiter value: <code>"dataspace-protocol-http"</code>

- Saturn EDCs now require the versioned endpoint:
  /2025-1

- Now uses a DID-based identifier:
  did:web:portal-backend.beta.cofinity-x.com:api:administration:staticdata:did:{{Provider-BPNL}}
- Instead of using only the BPNL (as in Jupiter EDCs)

- Protocol version updated
 - New value: <code>"dataspace-protocol-http:2025-1"</code>
 - Replaces Jupiter value: <code>"dataspace-protocol-http"</code>
- Counter Party Address updated
 - Saturn EDCs now require the versioned endpoint:
 /2025-1
- Counter Party ID format changed
 - Now uses a DID-based identifier:
 did:web:portal-backend.beta.cofinity-x.com:api:administration:staticdata:did:{{Provider-BPNL}}
 - Instead of using only the BPNL (as in Jupiter EDCs)

How to Determine the Provider EDC Version

A Provider exposes a public version discovery endpoint:

GET: {{Provider-Saturn-EDC-URL}}/api/v1/dsp/.well-known/dspace-version

{ "protocolVersions": [ { "version": "v0.8", "path": "/", "binding": "HTTPS" }, { "version": "2025-1", "path": "/2025-1", "binding": "HTTPS" } ] }

- v0.8 → Jupiter EDCs
- 2025-1 → Saturn EDCs

If the Provider supports <code>2025-1</code>, the Consumer must use <code>/2025-1</code> endpoints.

If only <code>v0.8</code> is supported, endpoints (<code>/</code>) are used.

- If the Provider supports <code>2025-1</code>, the Consumer must use <code>/2025-1</code> endpoints.
- If only <code>v0.8</code> is supported, endpoints (<code>/</code>) are used.

Catalog query would work in the following way:

In this article you can find out how to check the endpoints of an EDC for the Saturn EDCs (0.11.x and later)

Protocol Version Handling for Saturn EDC (0.11.x and later)

Blog

Home

Find answers and get help from Intercom Support and Community Experts

Conversations you've started through the messenger will appear here.

No conversations created by you

Try using different keywords or checking for typos.

No conversations found

Title

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Empty Help Center

Uh oh. That page doesn’t exist.

Search results

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

Protocol Version Handling for Saturn EDC (0.11.x and later)

Catalog Query for Saturn EDCs

Key Changes:

How to Determine the Provider EDC Version

Compatibility Note

Consumer	Provider	Protocol	CounterPartyAddress	CounterPartyId
Saturn	Saturn	dataspace-protocol-http:2025-1	{{Provider-Saturn-EDC-URL}}/api/v1/dsp/2025-1	did:web:portal-backend.beta.cofinity-x.com:api:administration:staticdata:did:{{Provider-BPNL}}
Saturn	Jupiter	dataspace-protocol-http	{{Provider-EDC-URL}}/api/v1/dsp	{{Provider-BPNL}}
Jupiter	Saturn	dataspace-protocol-http	{{Provider-EDC-URL}}/api/v1/dsp	{{Provider-BPNL}}