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 Customer Accounts (MTA) API

Create and Manage Customer Accounts (MTA)

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

This API exposes 14 operations across 14 paths, and defines 17 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.

14 operations 14 paths 17 schemas 2 DELETE2 GET1 PATCH9 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 Customer Accounts (MTA) 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 14

Across 14 paths, the API surfaces 14 operations — 2 DELETE, 2 GET, 1 PATCH, 9 POST. Each is listed below with its method, path, parameters, and response codes.

Customer Accounts (MTA) 14

Create and Manage Customer Accounts (MTA)

POST
/accounts
Create customer account
2 params body → 202400403404500503
PATCH
/accounts/{zrn}
Update customer account
3 params body → 202400403404500503
GET
/accounts/{zrn}/details
Get account details
3 params → 200400403404500503
POST
/accounts/{zrn}/lock
Lock customer account
3 params body → 202400403404500503
POST
/accounts/{zrn}/unlock
Unlock customer account
3 params body → 202400403404500503
POST
/accounts/{zrn}/withdraw_lock
Withdraw lock customer account
3 params body → 202400403404500503
POST
/accounts/{zrn}/withdraw_unlock
Withdraw unlock customer account
3 params body → 202400403404500503
POST
/accounts/{zrn}/divest
Divest customer account
3 params body → 202400403404500503
POST
/accounts/{zrn}/advisors
Add advisor to customer account
3 params body → 202400403404500503
POST
/accounts/{zrn}/tenants
Add tenant to customer account
3 params body → 202400403404500503
DELETE
/accounts/{zrn}/advisors/{financial_advisor}
Remove advisor from customer account
4 params → 202400403404500503
DELETE
/accounts/{zrn}/tenants/{tenant}
Remove tenant from customer account
4 params → 202400403404500503
POST
/accounts/{zrn}/close
Close customer account
3 params body → 202400403404500503
GET
/account/{zrn}/status_reason
Get customer account status reason
3 params → 200400403404500503

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are Code403 (2 properties), UpdateCustomerAccountBody (2 properties), Code404 (1 property), Code500 (1 property). 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
CloseCustomerAccountBody
object
PostCustomerAccountRequest
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
LockCustomerAccountBody
object
AddTenantToCustomerAccountBody
object
1 property 1 required
GetCustomerAccountStatusReasonBody
object
1 property
AddAdvisorToCustomerAccountBody
object
1 property 1 required
WithdrawUnlockCustomerAccountBody
object
Request body for withdraw-unlocking a customer account. Withdraw-unlocking an account removes the restriction on creating new withdrawal requests on the accoun…
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
WithdrawLockCustomerAccountBody
object
Request body for withdraw-locking a customer account. Withdraw-locking an account prevents any new withdrawal requests from being created on the account, but d…
UpdateCustomerAccountBody
object
2 properties 2 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
Code404
object
The requested resource does not exist or is not visible to the caller.
1 property 1 required
DivestCustomerAccountBody
object
Request body for divesting a customer account. Divesting an account initiates the process of liquidating the account's assets and closing the account. This is…
CustomerAccountResponse
object
1 property
UnlockCustomerAccountBody
object

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zero-hash-customer-accounts-mta-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 Deposits API
Zero Hash Entity Participants API
Zero Hash Fund API
Zero Hash Index API
Zero Hash Individual Participants API
Zero Hash Liquidity API
Where this information came from

This is an independent, third-party profile of Zero Hash Customer Accounts (MTA) 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.