How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Zero Hash Staking API

Staking, Unstaking and associated Rewards Services

Zero Hash Staking API is one of 31 APIs that Zero Hash publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Staking. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 9 operations across 9 paths, and defines 19 schemas. It is described by OpenAPI 3.2.0, at version 1.7.0.

Requests are made against a single base URL, https://api.cert.zerohash.com.

9 operations 9 paths 19 schemas 5 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.7.0
Base URL
https://api.zerohash.com
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Zero Hash Staking API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-SCX-API-KEY (apiKey). An API key is passed in the header as X-SCX-PASSPHRASE (apiPassphrase). By default, every request must be authenticated.

  • apiKey — Your API public key. See the [Authentication guide](https://docs.zerohash.com/reference/api-authentication) for how to obtain keys.
  • apiPassphrase — The passphrase associated with your API key, set when the key was created.

Paths & Operations 9

Across 9 paths, the API surfaces 9 operations — 5 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Staking 9

Staking, Unstaking and associated Rewards Services

POST
/stakes
Create a new stake
3 params body → 201400403404500503
POST
/stakes/unstake
Unstake assets
3 params body → 201400403404500503
POST
/stakes/{stake_id}/cancel
Cancel a stake
4 params → 200400403404500503
POST
/stakes/unstake/{unstake_id}/cancel
Cancel an unstake
4 params → 200400403404500503
GET
/stakes/{stake_id}/status
Get stake status
4 params → 200400403404500503
GET
/stakes/unstake/{unstake_id}/status
Get unstake status
4 params → 200400403404500503
GET
/stakes/{participant_code}
List participant stakes
8 params → 200400403404500503
GET
/stakes/{participant_code}/rewards
List staking rewards
10 params → 200400403404500503
GET
/stakes/{participant_code}/{asset}/summary
Get staking summary
4 params → 200400403404500503

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are StakeEntity (7 properties), StakingRewardEntity (5 properties), PostUnstakeBody (4 properties), GetStakesResponse (4 properties). Each schema is shown below with its type and property counts.

Code400
object
Request was rejected by validation or a downstream service. errors is an array of human-readable messages; each entry describes a single validation failure or…
1 property 1 required
PostUnstakeResponse
object
2 properties
StakingValidationErrorResponse
object
4 properties
GetStakeStatusResponse
object
2 properties
PostStakeResponse
object
2 properties
PostUnstakeBody
object
4 properties 4 required
Code500
object
An unexpected error occurred on the server. The request can be retried after a short delay, but the same inputs may reproduce the error.
1 property 1 required
PostCancelUnstakeResponse
object
2 properties
PostCancelStakeResponse
object
2 properties
GetUnstakeStatusResponse
object
2 properties
Code503
object
A downstream dependency was unavailable, timed out, or returned a retryable error. Safe to retry; the response carries a zh-allow-retry: true header.
1 property 1 required
StakeEntity
object
7 properties
GetStakingRewardsResponse
object
3 properties
PostStakeBody
object
4 properties 4 required
Code403
object
Authentication or authorization failed. error is always true; message explains which check failed (missing API key, bad signature, insufficient permission, etc…
2 properties 2 required
GetStakesResponse
object
4 properties
Code404
object
The requested resource does not exist or is not visible to the caller.
1 property 1 required
StakingRewardEntity
object
5 properties
GetSummaryResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zero-hash-staking-api-openapi.yml Raw ↑

Other APIs Zero Hash publishes across the network.

zerohash Private WebSocket API
Zero Hash Accounts API
Zero Hash Assets API
Zero Hash Awards API
Zero Hash CLOB API
Zero Hash Convert and Withdraw API
Zero Hash Customer Accounts (MTA) API
Zero Hash Deposits API
Zero Hash Entity Participants API
Zero Hash Fund API
Zero Hash Index API
Zero Hash Individual Participants API
Where this information came from

This is an independent, third-party profile of Zero Hash Staking API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.