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

Nym Technologies Ecash API

The Ecash API from Nym Technologies — 13 operation(s) for ecash.

Nym Technologies Ecash API is one of 23 APIs that Nym Technologies publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Ecash. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 13 operations across 13 paths, and defines 36 schemas. It is described by OpenAPI 3.2.0, at version 4.6.2.

Requests are made against a single base URL, https://validator.nymtech.net/api.

13 operations 13 paths 36 schemas 8 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
4.6.2
Base URL
https://validator.nymtech.net/api
Contact
Nym Technologies SA
License
Apache-2.0
Resource Areas
1

Paths & Operations 13

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

Ecash 13
POST
/v1/ecash/batch-redeem-ecash-tickets
batch_redeem_tickets 1 param body → 200400
POST
/v1/ecash/blind-sign
post_blind_sign 1 param body → 200400
GET
/v1/ecash/double-spending-filter-v1deprecated
double_spending_filter_v1 → 500
POST
/v1/ecash/issued-ticketbooks-challenge-commitment
issued_ticketbooks_challenge_commitment 1 param body → 200400
GET
/v1/ecash/issued-ticketbooks-count
Returns number of issued ticketbooks for given dates. Note: this endpoint will not be accurate for old dates
issued_ticketbooks_count 3 params → 200400
POST
/v1/ecash/issued-ticketbooks-data
issued_ticketbooks_data 1 param body → 200400
GET
/v1/ecash/issued-ticketbooks-for-count/{expiration_date}
Returns number of issued ticketbooks for particular expiration date. Note: this endpoint will not be accurate for old dates
issued_ticketbooks_for_count 2 params → 200400
GET
/v1/ecash/issued-ticketbooks-for/{expiration_date}
issued_ticketbooks_for 2 params → 200400
GET
/v1/ecash/issued-ticketbooks-on-count/{issuance_date}
Returns number of issued ticketbooks on particular date. Note: this endpoint will not be accurate for old dates
issued_ticketbooks_on_count 2 params → 200400
GET
/v1/ecash/partial-coin-indices-signatures
partial_coin_indices_signatures 2 params → 200400
GET
/v1/ecash/partial-expiration-date-signatures
partial_expiration_date_signatures 3 params → 200400
GET
/v1/ecash/signer-status
signer_status 1 param → 200
POST
/v1/ecash/verify-ecash-ticket
verify_ticket body → 200400

Schemas 36

The contract defines 36 schemas that model the data the API accepts and returns. The most detailed are BlockHeader (14 properties), BlindSignRequestBody (6 properties), AbciInfo (5 properties), WithdrawalRequest (4 properties). Each schema is shown below with its type and property counts.

PublicKeyUser
object
1 property 1 required
SerialNumberWrapper
array
IssuedTicketbooksOnCount
object
2 properties 2 required
EcashTicketVerificationResponse
object
1 property 1 required
EcashTicketVerificationResult
Used exclusively as part of OpenAPI docs
VerifyEcashTicketBody
object
2 properties 2 required
PartialCoinIndicesSignatureResponse
object
2 properties 2 required
BlockHeader
object
Block Header values contain metadata about the block and about the consensus, as well as commitments to the data in the current block, the previous block, and…
14 properties 9 required
EcashBatchTicketRedemptionResponse
object
1 property 1 required
ChainBlocksStatusResponseBody
object
3 properties 2 required
BlockInfo
object
2 properties 2 required
FullBlockInfo
object
1 property 1 required
DetailedChainStatus
object
2 properties 2 required
BlindedSignatureResponse
object
1 property 1 required
IssuedTicketbooksForCount
object
2 properties 2 required
u64
integer
AnnotatedCoinIndexSignature
object
2 properties 2 required
HeaderVersion
object
Version contains the protocol version for the blockchain and the application.
2 properties 2 required
SignedMessage
object
2 properties 2 required
BlindedSignature
object
2 properties 2 required
Signature
object
2 properties 2 required
WithdrawalRequest
object
4 properties 4 required
AbciInfo
object
5 properties 5 required
PartSetHeader
object
Block parts header
2 properties 2 required
BlockId
object
Block identifiers which contain two distinct Merkle roots of the block, as well as the number of parts in the block. Default implementation is an empty Id as d…
2 properties 2 required
WithdrawalReqProof
object
4 properties 4 required
IssuedTicketbooksCount
object
3 properties 3 required
IssuedTicketbooksForCountResponse
object
3 properties 3 required
AnnotatedExpirationDateSignature
object
3 properties 3 required
BatchRedeemTicketsBody
object
4 properties 4 required
PartialExpirationDateSignatureResponse
object
3 properties 3 required
ChainStatus
IssuedTicketbooksOnCountResponse
object
3 properties 3 required
Output
string
BlindSignRequestBody
object
6 properties 6 required
IssuedTicketbooksCountResponse
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nym-technologies-ecash-api-openapi.yml Raw ↑

Other APIs Nym Technologies publishes across the network.

Nym Technologies API Status API
Nym Technologies circulating-supply API
Nym Technologies contract-cache API
Nym Technologies dVPN Directory Cache API
Nym Technologies Ecash Global Data API
Nym Technologies Gateways API
Nym Technologies Mixnodes API
Nym Technologies network API
Nym Technologies network-monitor-status API
Nym Technologies Node Families API
Nym Technologies Nym Explorer API
Nym Technologies Nym Nodes API
Where this information came from

This is an independent, third-party profile of Nym Technologies Ecash 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.