nChain Identity
Back to All
  • nChain Identity user documentation
  • 📑INTRODUCTION
    • Introduction to nChain Identity
    • Why choose nChain Identity?
      • DiD differentiators
    • How does nChain Identity work?
      • Data flows
      • Use cases and applications
    • Standards and regulations
  • 📄nChain Identity Issuers
    • What is an issuer?
    • How to become an issuer?
    • Operating an issuer
    • What do issuers do?
    • Issuer API
      • Overview
      • Getting Started
      • Examples
        • Issue an email credential
        • Revoke a claimed email credential
      • API Documentation
        • Credential Offers
        • Agent
        • Claims
  • 📑NCHAIN IDENTITY VERIFIER
    • What is a Verifier?
    • Operating a verifier
    • How to become a verifier?
    • Verifier API
      • Overview
      • Getting Started
      • Examples
        • Verify an email credential
      • API Documentation
        • Verifiable Presentation
        • Verifying
        • Agent
        • SIOP
        • Templates
  • 📄NCHAIN IDENTITY WALLET
    • What is the wallet for?
    • How to receive a Verifiable Credential?
    • How to share a Verifiable Credential?
  • 📑Privacy and Security
    • Privacy and Security Measures: NChain Identity Services
    • Revocation and data deletion
  • 🗃️SELF-SOVEREIGN IDENTITY KNOWLEDGE
    • Self-Sovereign Identity
    • Actors
    • Decentralized vs Self-Sovereign Identity
    • Key Principles of Self-Sovereign Identity
    • Self-Sovereign Identity – Use Cases
    • Digital Trust
    • Some of the critical components of Self Sovereign Identity
      • Trust over IP
    • Some of the critical components of Decentralise ID
      • A Blockchain Tailored for Decentralized Identity
      • Decentralise Identifiers (DiD)
      • Verifiable Credentials
      • Verifiable Presentations
  • 📑GLOSSARY
    • Glossary
  • 📄FAQs / HELP
    • Help & FAQs
      • What is a digital identity?
      • What is nChain Identity, and how does it work?
      • How is blockchain used in nChain Identity?
      • Compatible Blockchains for nChain Identity.
      • How can my business sign up for nChain Identity?
      • How is nChain Identity different to other identity solutions in the market?
      • Can nChain Identity communicate with other identity solutions?
      • What is nChain Identity doing with my data, and does it act as a data processor or controller?
      • What measures does nChain Identity take to protect user data?
      • What support is available for nChain Identity?
      • Can nChain Identity be integrated into our existing systems?
      • How can I get started with nChain Identity?
      • What countries is nChain Identity available in?
Powered by GitBook
On this page
  1. nChain Identity Issuers
  2. Issuer API
  3. API Documentation

Agent

OpenAPI documentation for the Agent module

PreviousCredential OffersNextClaims

Last updated 6 months ago

📄
get

This endpoint facilitates the retrieval of a DID document id.

Responses
200Success
text/plain
503
The service is unavailable
get
GET /public/did HTTP/1.1
Host: ..
Accept: */*
did:bsv:1234
get

Returns all the information needed to see the status of the services running

Responses
200Success
application/json
503
The service is unavailable
get
GET /public/getStatus HTTP/1.1
Host: ..
Accept: */*
{
  "state": "starting",
  "did": {
    "did": "did:bsv:1234",
    "ready": true,
    "controller": "https://did.identity.controller.nchainplatform.com/",
    "resolver": "https://did.identity.resolver.nchainplatform.com/"
  },
  "started": "2011-10-05T14:48:00.000Z",
  "timestamp": "2011-10-05T14:48:00.000Z",
  "version": {
    "version": "v1.1.0",
    "commit": "4bfccdd063f6d21d34beba1c48eb6e82170d99f0",
    "development": true,
    "buildTime": "2011-10-05T14:48:00.000Z"
  }
}

Retrieve information about credential types and configurations

get

Endpoint facilitates the retrieval of a list of credentials that can be issued based on the provided correlationId. This endpoint expects the correlationId to be passed as a path parameter. Upon receiving a request, the server searches for JSON files located in the /dev/oid4vci_metadata directory, matching the correlationId with the correlationId property in the JSON files. It also returns metadata, which has fields credential_issuer (tells web address where issuer is located) and credential_endpoint (tells web address endpoint where credential can be claimed). It also returns display object and credential_supplier_configobject. display field name will be displayed in wallet app as Authority Name when accepting a credential. Object credential_supplier_config returns all templates and mappings for the credential supplier.

Path parameters
correlationIdstringRequired

The correlation ID defined on the server (nchain in our case).

Responses
200Success
application/json
503
The service is unavailable
get
GET /public/{correlationId}/.well-known/openid-credential-issuer HTTP/1.1
Host: ..
Accept: */*
{
  "credential_issuer": "text",
  "credential_endpoint": "text",
  "display": {
    "name": "Organisation Issuer",
    "description": "Organisation Issuer"
  },
  "credentials_supported": [
    {
      "display": {
        "name": "Email Credential",
        "description": "Email Credential for Organisation"
      },
      "order": [
        "name-of-claim"
      ],
      "credentialSubject": {
        "name-of-claim": "value"
      }
    }
  ]
}
  • GET/public/did
  • GET/public/getStatus
  • GETRetrieve information about credential types and configurations