Bearer API keys
Protected endpoints use a Bearer API key. Keep production secrets server-side and never hard-code them into public applications.
Authorization: Bearer YOUR_API_KEYConnect applications to trusted credentials, evidence and blockchain-backed verification through a production developer API.
Make your first authenticated request in minutes.
Protected endpoints use a Bearer API key. Keep production secrets server-side and never hard-code them into public applications.
Authorization: Bearer YOUR_API_KEYThe health endpoint is public and does not require a key.
GET https://api.waterchain.tech/v1/healthProduction endpoints exposed by WaterChain API v1.
/v1/healthReturns service status, network, chain ID, contract and RPC state.
PUBLIC/v1/certificatesLists certificate records with pagination.
certificate:read/v1/certificates/{certificateNo}Retrieves a certificate record by its canonical WaterChain certificate number.
certificate:read/v1/verify/{certificateNo}Returns a machine-readable verification record for integrations.
certificate:verifyRun live requests against the production API. Keys are used only for the current request and are never stored.
https://api.waterchain.tech/v1/healthSelect an endpoint and run the request.
Patterns for production integrations.
Store production credentials in your server environment or secret manager. Do not commit them to source control or browser JavaScript.
Use the verification endpoint to reconcile certificate identity and evidence before accepting a credential in your workflow.
400 Invalid Request · 401 Unauthorized · 403 Forbidden · 404 Not Found · 409 Conflict · 422 Invalid SHA-256 · 429 Rate Limited · 500 Internal Error.
WaterChain API connects application workflows to Blockcerts, evidence and Avalanche C-Chain state.