Overview

Chainpoint anchors any data hash to the Bitcoin blockchain, creating a tamper-proof proof of existence for documents, records, or any digital content. It returns a cryptographic proof you can verify independently.

Beginner Tip

Submit a SHA-256 hash of your data (not the raw data itself) — this keeps your content private while still creating an immutable timestamp on the blockchain.

Available Data

The kind of data this API exposes, based on its documentation. We could not call the endpoint to confirm the exact field names.

coin price in USD/EUR
market capitalization
24h price change
trading volume
circulating supply

Example Response

Illustrative shape only — we were not able to call this endpoint (it requires credentials or exposes no public sample URL), so the fields below show the kind of data this API returns rather than a recorded response.

JSON Response · Illustrative
{
  "id": "bitcoin",
  "symbol": "btc",
  "current_price": 65432.1,
  "market_cap": 1280000000000,
  "price_change_24h": 1250.5,
  "price_change_percentage_24h": 1.95,
  "total_volume": 28500000000
}

Field Reference

hash_id_node UUID that identifies your submitted hash on this specific node; save it to retrieve the proof later.
hash Echo of the SHA-256 hash you submitted for anchoring.
submitted_at ISO 8601 timestamp of when the hash was accepted by the node.
processing_hints.btc Estimated ISO 8601 timestamp for when the Bitcoin anchor proof will be available (typically ~60-90 minutes).

Implementation Example

Calls a real endpoint of this API. Replace any placeholder credentials with your own key.

Request
const url = "https://a.chainpoint.org/hashes";
const response = await fetch(url);
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

Generated guidance based on this API's documentation, not observed by us. Treat it as a starting point and check against the provider's own error reference.

400 – invalid hash format Submitting a hash that is not a valid hex-encoded SHA-256 string
Ensure your hash is exactly 64 lowercase hexadecimal characters; use SHA-256 (not MD5 or SHA-1).
Proof not ready yet Bitcoin block anchoring takes ~10 minutes; the proof won't be available immediately after submission
Poll the proof retrieval endpoint with the hash_id_node returned on submission; retry every few minutes until the proof is available.
Node endpoint unreachable Chainpoint nodes are community-run and individual nodes may go offline
Submit to multiple nodes simultaneously for redundancy; the API returns a list of nodes to try.

Metadata Score Breakdown

Estimated from metadata — endpoint not independently tested

This score is estimated from observable metadata — HTTPS support, authentication model, declared CORS, and documentation reachability — because the API requires authentication or exposes no publicly testable endpoint. The five-signal breakdown is only shown for live-tested APIs.

Metadata estimate · endpoint not independently tested

Technical Specifications

Auth No Auth
HTTPS REQUIRED
CORS UNKNOWN
Category Blockchain
Difficulty Beginner
Listing details not endpoint-verified

Related Tags

Similar APIs

View All →