nChain Event
Back to All
V.1.4.3
V.1.4.3
  • nChain Event User Guide
  • 📔Overview
    • Introduction
    • Configuration Symbols
    • Features and Benefits
    • Core Concepts
    • Encoded and Unencoded ‡ Records
  • 🤔Using nChain Event
    • How to Use nChain Event
    • Initial Set-Up
  • 🔏Independent Records
    • Introduction
    • Functional Description
      • Write Record
      • Read Record
      • Verify Record †
    • Use Cases
      • Lucky Number Tickets
      • Internet of Things (IoT) Data
      • Intellectual Property Rights (IPR) Evidence
      • Car Dealership
    • Tutorials
      • Data Integrity
      • Blockchain Unique Identifiers
    • API Workflow
      • Configure API
      • Write Record
      • Get Location Status
      • Read Record
      • Verify Record †
  • 🔗Linked Records §
    • Introduction
    • Functional Description
      • Create Link Record §
      • Read Link Record §
      • Update Link Record §
      • Delete Link Record §
      • Verify Link Record § †
      • Navigate Linked Record § ¶
    • Use Cases
      • Luxury Handbag Provenance
      • Random Prize Draw
    • Tutorials
      • Collection Integrity
      • Provenance Integrity
    • API Workflow
      • Configure API
      • Create Link Record §
      • Get Link Location Status §
      • Read Link Record §
      • Update Link Record §
      • Delete Link Record §
      • Verify Link Record § †
      • Navigate Link Record § ¶
  • ⚙️API Documentation
    • nChain Event API
  • ⛓️Bitcoin SV Blockchain
    • Features and Benefits
    • Writing to Blockchain
    • Reading from Blockchain
    • Transaction Format
  • ⁉️Troubleshooting
    • Troubleshooting
    • Error Codes
    • Glossary
    • Contact Us
Powered by GitBook
On this page
  1. Linked Records §
  2. API Workflow

Get Link Location Status §

PreviousCreate Link Record §NextRead Link Record §

Check whether the record is on the blockchain at the link location:

  1. The record owner waits at least 10 minutes for any create, update or delete operation to be confirmed on the blockchain

  2. The record owner checks the status of the link location

  3. If not confirmed, the record owner either waits again waits again or retries the operation

  4. The record owner optionally sends or publishes the link Location to any other parties

Example code:

curl $URL/api/v1/linkedrecords/$LOC/status \
     -H "x-api-key: $KEY" \
     -H "accept: text/plain"
const response = await fetch('${url}/api/v1/linkedrecords/${loc}/status', {
  headers: {
    'x-api-key': '${key}',
    'accept': 'text/plain'
  }
});

Example cURL immediate response:

{
  "updatable": true,
  "confirmation": null
}

Example cURL response after waiting for 30 minutes:

{
  "updatable": true,
  "confirmation": {
    "confirmedBlocks": 3,
    "blockHash": "038ada8fba49a4972....3fb049b45553612c187cc",
    "blockTimestamp": "2024-01-02T13:20:05Z",
    "merkleProof": {
      "index": 2,
      "txOrId": "47175b2ee3345942....d58cd286198e1bcf97",
      "target": "00000020e1b721d55e....9c4ba58cf65ffff7f2000000000",
      "nodes": [
        "*",
        "d6e26a5e5ecbfa38923b....dcfc4bc99b29b4acda214c38"
      ],
      "targetType": "header",
      "proofType": null,
      "composite": null
    }
  }
}

The Merkle proof is described in the blockchain section.

🔗