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 Individual Participants API

Create and Manage Individual Participants

Zero Hash Individual Participants 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 Individual Participants. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 7 operations across 7 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.

7 operations 7 paths 19 schemas 3 PATCH4 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 Individual Participants 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 7

Across 7 paths, the API surfaces 7 operations — 3 PATCH, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Individual Participants 7

Create and Manage Individual Participants

POST
/participants/customers/new
Create customer
2 params body → 201400403404500503
POST
/participants/documents
Submit documents
2 params body → 201400403404500503
PATCH
/participants/customers/{participant_code}
Update customer
3 params body → 200400403404500503
POST
/participants/customers/{participant_code}/lock
Lock customer
3 params body → 200400403404500503
POST
/participants/beneficiaries/new
Create beneficiary
3 params body → 201400403404500503
PATCH
/participants/beneficiaries/{participant_code}
Update beneficiary
4 params body → 200400403404500503
PATCH
/participant/{participant_code}/limits
Update participant limits
3 params body → 200400403404500503

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are PostBeneficiariesBody (16 properties), PatchBeneficiariesBody (16 properties), AdditionalTaxResidence (2 properties), Code403 (2 properties). Each schema is shown below with its type and property counts.

PatchBeneficiariesBody
object
16 properties 5 required
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
PostCustomersResponse
object
1 property
PatchCustomersBody
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
PatchParticipantLimitsBody
object
1 property 1 required
PostCustomersBody
AdditionalTaxResidence
object
2 properties 2 required
LockCustomersBody
object
2 properties 2 required
PostBeneficiariesResponse
object
1 property
PostDocumentsResponse
object
1 property
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
PatchBeneficiariesResponse
object
1 property
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
PatchCustomersResponse
object
1 property
Code404
object
The requested resource does not exist or is not visible to the caller.
1 property 1 required
PostBeneficiariesBody
object
16 properties 6 required
PostDocumentsBody
PatchParticipantLimitsResponse
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zero-hash-individual-participants-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 Liquidity API
Where this information came from

This is an independent, third-party profile of Zero Hash Individual Participants 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.