LearnCard Documentation
GithubStatusSupportLaunch App
  • 🚀Introduction
    • What is LearnCard?
    • Use Cases & Possibilities
    • Ecosystem Architecture
  • ⚡Quick Start
    • Setup & Prerequisites
    • Your First Integration
  • 📚Tutorials
    • Create a Credential
    • Create a Boost
    • Create a ConsentFlow
    • Create a Connected Website
    • Send xAPI Statements
    • Listen to Webhooks
  • ✅How-To Guides
    • Verify My Issuer
    • Connect Systems
      • Connect a Website
      • Connect a Game
    • Implement Flows
      • Claim Data after Guardian Consent
      • Connect via CHAPI
        • ⭐CHAPI Wallet Setup Guide
        • ↔️Translating to CHAPI documentation
        • 🖥️Demo Application
        • 🔰Using LearnCard to Interact with a CHAPI Wallet
        • 📝Cheat Sheets
          • Issuers
          • Wallets
    • Deploy Infrastructure
      • Remote Key Management
      • Generate API Tokens
      • Signing Authority
      • Connect to Independent Network
      • Build a Plugin
  • 🛠️SDKs & API Reference
    • LearnCard Wallet SDK
      • Authentication
      • Usage Examples
      • SDK Reference
      • Plugin API Reference
      • Integration Strategies
      • Deployment
      • Troubleshooting
      • Changelog
    • LearnCloud Network API
      • Authentication
      • Usage Examples
      • Architecture
      • Notifications & Webhooks
      • Profiles
      • Profile Managers
      • Credentials
      • Boosts
      • Presentations
      • Storage
      • Contracts
      • DID Metadata
      • Claim Hooks
      • Auth Grants
      • Utilities
      • Models
      • OpenAPI
    • LearnCloud Storage API
      • Authentication
      • Usage Examples
      • Architecture
      • Storage
      • Index
      • User
      • Custom Storage
      • Utilities
      • Models
      • xAPI Reference
    • Plugins
      • Crypto
      • DIDKit
      • DID Key
      • Dynamic Loader
      • VC
        • Expiration Sub-Plugin
      • VC-Templates
      • VC-API
      • Ceramic
      • IDX
      • VPQR
      • Ethereum
      • CHAPI
      • LearnCard Network
      • LearnCloud
      • LearnCard
      • Simple Signing
      • Claimable Boosts
    • LearnCard CLI
  • 🧠Core Concepts
    • Identities & Keys
      • Decentralized Identifiers (DIDs)
      • Seed Phrases
      • Network Profiles
      • Signing Authorities
      • Trust Registries
    • Credentials & Data
      • Verifiable Credentials (VCs)
      • Credential Lifecycle
      • Schemas, Types, & Categories
      • Building Verifiable Credentials
      • Boost Credentials
      • Getting Started with Boosts
      • Credential URIs
      • xAPI Data
      • General Best Practices & Troubleshooting
    • Consent & Permissions
      • ConsentFlow Overview
      • Consent Contracts
      • User Consent & Terms
      • Consent Transactions
      • Auto-Boosts
      • Writing Consented Data
      • Accessing Consented Data
      • GameFlow Overview
    • Network & Interactions
      • Network Vision & Principles
      • Key Network Procedures
      • Core Interaction Workflows
    • Architecture & Principles
      • Control Planes
      • Plugin System
      • Auth Grants and API Tokens
  • 🔗Development
    • Contributing
Powered by GitBook
On this page
  • What is this section about?
  • Why is this important for you to understand?
  • What you'll learn:
  • 🌐 LearnCloud Network API
  • 🌎 Open & Interoperable Exchange
  • 🔄 Defined Interaction Protocols

Was this helpful?

  1. Core Concepts

Network & Interactions

LearnCloud Network principles, API interaction patterns, Sequencing

What is this section about?

This section details how the various components and participants within the LearnCard ecosystem—users, services, and the LearnCloud Network itself—communicate and interact. It covers the underlying principles of these interactions, common patterns for using APIs, and the typical order of operations (Sequencing) for key processes.

Why is this important for you to understand?

To build robust integrations or applications that effectively leverage LearnCard, you need to understand the "rules of the road" for communication. This includes how to make requests to services, what kind of responses to expect, and the typical sequence of calls needed to achieve common tasks like issuing a credential or verifying a presentation. This ensures your integrations are smooth, predictable, and use the system efficiently. It's like knowing the right way to address a letter, the expected format for a reply, and the steps involved in a complex transaction.

What you'll learn:

You'll get an overview of how the LearnCloud Network facilitates interactions, common design patterns for using LearnCard APIs, and the typical sequence of events for important workflows.


🌐 LearnCloud Network API

The LearnCloud Network API lets developers:

  • Send and receive credentials, boosts, and presentations

  • Create and claim credentials through peer-to-peer or QR flows

  • Register and manage Signing Authorities

  • Trigger and validate ConsentFlows

  • Monitor health and fetch metadata (like DIDs or challenge keys)

It’s the backbone of interaction between LearnCard users and applications.

🌎 Open & Interoperable Exchange

The LearnCloud Network is designed for broad participation and seamless data flow. Our approach emphasizes:

  • Standardization: Adherence to W3C standards (like Verifiable Credentials and DIDs) to ensure data can be understood and used across different systems.

  • Portability: Credentials and data aren't locked into silos; they can be securely shared and recognized across diverse applications and platforms.

  • Connectivity: Enabling a rich ecosystem where different services and users can confidently exchange verifiable information. This focus on open, interoperable exchange is key to unlocking the full potential of verifiable data.

🔄 Defined Interaction Protocols

Interactions within the LearnCard ecosystem, such as issuing a credential, presenting proof, or managing connections, follow clear, defined procedures and protocols. This means:

  • Predictability: Developers can build with confidence, knowing the expected sequence and behavior for common operations.

  • Reliability: Standardized interactions reduce errors and ensure smoother communication between different parts of the system.

  • Clarity: The "rules of engagement" are explicit, making it easier to integrate and troubleshoot. Understanding these protocols is fundamental to building applications that interact effectively and securely within the network.

PreviousGameFlow OverviewNextNetwork Vision & Principles

Last updated 9 days ago

Was this helpful?

🧠