iSHARE Developer Portal
Other resources
Version 2.1 (current version)
Version 2.1 (current version)
  • Welcome to the iSHARE Developer Portal
  • Introduction
    • Getting started
      • Test certificates
      • Test participants
      • Postman collections
    • Release info
    • Help & support
    • Specific technical standards
      • JSON Web Token (JWT)
      • OAuth 2.0
      • OpenID Connect 1.0
      • PKI
      • TLS
      • XACML 3.0
      • Caching
      • DID
      • UTC
      • X.509
      • HTTP response codes
    • UI Guidelines
    • Conformance test tool
  • Roles
    • Roles
  • All roles (common endpoints)
    • Access token (M2M)
    • Capabilities
  • Authorisation Registry Role
    • Getting started
    • Access token (M2M)
    • Capabilities
    • Delegation
    • Delegation Policy
  • Entitled Party
    • Getting started
  • Identity Provider
    • Getting started
    • Authorize
    • Login
    • Access token
    • User info
    • Capabilities
  • Participant Registry role
    • Getting started
    • Access token (M2M)
    • Capabilities
    • Parties
    • Parties (single party)
    • Trusted list
    • Versions
    • Data Spaces
    • Create Entitled Party / Service Consumer
  • Service Consumer Role
    • Getting started
  • Service Provider Role
    • Getting started
      • Service
    • Access token (M2M)
    • Capabilities
    • Return
  • Reference
    • iSHARE JWT
      • Client Assertion
    • Authentication
    • Authorization
    • Authorisation rules
Powered by GitBook
LogoLogo

  • Cookie Policy

  • Privacy Policy

  • Imprint

  • Contact Us

Copyright © 2024 iSHARE Foundation

Welcome to the iSHARE Developer Portal

NextGetting started

Last updated 2 months ago

Version information

This documentation is in line with the iSHARE Trust Framework 2.1.

Older versions of the framework can be accessed through the top menu. Version 1.11 is available .

In the iSHARE technical specifications, both snake_case and camelCase are used interchangeably. With every iteration of updates, the specifications will incrementally be changed to camelCase.

Part of this documentation is formal Framework specification

Part of this documentation must be considered part of the formal iSHARE Trust Framework Specification. Where applicable, this is clearly marked.

The iSHARE Trust Framework is a collaborative effort to improve the exchange of data between organisations in and across data spaces. The iSHARE Trust Framework is available .

Technical Approach

Unlike traditional software infrastructures, iSHARE offers a “soft infrastructure” focusing on:

  • Identification, authentication, and authorization for machine-to-machine (M2M) and human-to-machine (H2M) communication via REST API.

  • Public Key Infrastructure (PKI) for authentication.

  • Signed JSON Web Tokens (JWTs) for message integrity.

Data sharing transactions must align with the , each with specific responsibilities and interactions. This portal provides everything needed to technically implement iSHARE in your organisation, including:

  • How to get started for each role.

  • All iSHARE technical specifications.

  • Definitions for all endpoints required per role.

Additional content

If you are looking for additional content before getting started with your implementation, the contains the , try the to understand how iSHARE Trust Framework works technically or make use of the reference implementations and open-source components on .

here
here
iSHARE Trust Framework’s roles
knowledge base
Technical standards used in iSHARE
postman collections
GitHub