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 Payments API

Payment Services

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

This API exposes 12 operations across 10 paths, and defines 31 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.

12 operations 10 paths 31 schemas 6 GET6 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 Payments 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 12

Across 10 paths, the API surfaces 12 operations — 6 GET, 6 POST. Each is listed below with its method, path, parameters, and response codes.

Payments 12

Payment Services

POST
/payments/external_accounts
Create external account
2 params body → 201400403404500503
GET
/payments/external_accounts
List external accounts
7 params → 200400403404500503
POST
/payments/external_accounts/{external_account_id}/close
Close external account
3 params body → 200400403404500503
POST
/payments
Create payment
3 params body → 201400403404500503
GET
/payments
List payments
7 params → 200400403404500503
GET
/payments/{payment_id}
Get payment by id
3 params → 200400403404500503
GET
/payments/settlements
List pending ACH settlements
7 params → 200400403404500503
POST
/payments/{transaction_id}/retry
Retry a fiat payment
3 params → 200400403404500503
GET
/payments/history
List fiat transaction history
7 params → 200400403404500503
GET
/payments/status
List fiat transaction statuses
10 params → 200400403404500503
POST
/payments/rfq
Request payment quote
2 params body → 200400403404500503
POST
/payments/execute
Execute payment quote
2 params body → 200400403404500503

Schemas 31

The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are Payment (17 properties), ACHTransactionStatus (13 properties), ACHTransactionHistory (12 properties), PostPaymentsExecutePaymentRequest (7 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
ExternalAccount
object
PendingACHTransactions
object
5 properties
PostCreateExternalAccountRequest
object
PostCloseExternalAccountRequest
object
1 property 1 required
GetPendingACHTransactionsResponse
object
5 properties
Payment
object
17 properties
GetACHTransactionStatusResponse
object
5 properties
GetPaymentByIDResponse
object
2 properties
OBOParticipantEntity
object
3 properties
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
ACHTransactionHistory
object
12 properties
PostPaymentsRequestForQuoteRequest
object
7 properties 4 required
GetACHTransactionHistoryResponse
object
5 properties
PostCreateExternalAccountResponse
object
ACHTransactionStatus
object
13 properties
PostPaymentsRetryResponse
object
1 property
PostPaymentsResponse
object
UnderlyingCurrency
string
the underlying asset
PostPaymentsRequest
object
Exactly one of the following payload shapes must be submitted. Providing both total and quantity on a payout is rejected by the validator.
PostPaymentsExecutePaymentResponse
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
ACHStatus
object
2 properties
PostCloseExternalAccountResponse
object
2 properties
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
Code404
object
The requested resource does not exist or is not visible to the caller.
1 property 1 required
QuotedCurrency
string
the quoted asset
GetPaymentsResponse
object
4 properties
PostPaymentsExecutePaymentRequest
object
7 properties 4 required
PostPaymentsRequestForQuoteResponse
object
1 property
GetExternalAccountsResponse
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zero-hash-payments-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 Payments 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.