NDAX Tickets API
The Tickets API from NDAX — 19 operation(s) for tickets.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/ndax:ndax-tickets-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Ndax Pro Tickets API
version: '2026-10-13'
description: 'Generated by API Evangelist from the Ndax Pro API reference at https://apidoc.ndax.io (Slate). Ndax is built on AlphaPoint: every function is documented as a JSON payload sent inside a message frame {m,i,n,o} over wss://api.ndax.io/WSGateway/. Public functions also answer over HTTP at https://api.ndax.io:8443/AP/{FunctionName} (Ping, GetInstruments and GetProducts verified live 2026-10-13). Each path here is a documented function name; this is NOT a provider-published contract.'
contact:
url: https://ndax.io/support
termsOfService: https://ndax.io/en/legal/account-agreements
x-generated-from: documentation
x-provenance: generated
x-authored-by: API Evangelist
x-generated: '2026-10-13'
x-generator: deterministic parse of https://apidoc.ndax.io section headings, Category/Permissions/CallType lines and request/response examples (no model)
servers:
- url: https://api.ndax.io:8443/AP
description: Ndax AlphaPoint HTTP gateway
security:
- apiKeySignature: []
tags:
- name: Tickets
paths:
/AddDepositTicketAttachment:
post:
operationId: addDepositTicketAttachment
summary: Add Deposit Ticket Attachment
description: Adds an attachment to a deposit ticket. User with Trading permission can add an attachment only to their own deposit tickets; users with Operator permission can add an attachment to any deposit ticket. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
tags:
- Tickets
x-category: System
x-permissions: Operator, Trading
x-call-type: Synchronous
x-docs-url: https://apidoc.ndax.io/#adddepositticketattachment
x-websocket-function: AddDepositTicketAttachment
requestBody:
required: false
content:
application/json:
schema:
type: object
example:
base64Attachment: ''
attachmentId: 0
submittedByUserId: 0
submittedByUserName: ''
uploadDate: '0001-01-01T00:00:00'
uploadIP: ''
ticketNumber: 0
description: ''
responses:
'200':
description: Function reply payload.
content:
application/json:
schema: {}
example:
success: true
attachmentid: 100000002
x-requires-session: true
/AddWithdrawTicketAttachment:
post:
operationId: addWithdrawTicketAttachment
summary: Add Withdraw Ticket Attachment
description: Adds an attachment to a withdraw ticket. Users with Trading permission can add an attachment only to their own withdraw tickets; users with Operator permission can add an attachment to any withdraw ticket. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
tags:
- Tickets
x-category: System
x-permissions: Operator, Trading
x-call-type: Synchronous
x-docs-url: https://apidoc.ndax.io/#addwithdrawticketattachment
x-websocket-function: AddWithdrawTicketAttachment
requestBody:
required: false
content:
application/json:
schema:
type: object
example:
base64Attachment: ''
attachmentId: 0
submittedByUserId: 0
submittedByUserName: ''
uploadDate: '0001-01-01T00:00:00'
uploadIP: ''
ticketNumber: 0
description: ''
responses:
'200':
description: Function reply payload.
content:
application/json:
schema: {}
example:
success: true
attachmentid: 100000002
x-requires-session: true
/ConfirmWithdraw:
post:
operationId: confirmWithdraw
summary: Confirm Withdraw
description: Checks whether the user has clicked the confirmation link in an email. The email confirms whether the user issued the withdrawal request.
tags:
- Tickets
x-category: System
x-permissions: Public
x-call-type: Synchronous
x-docs-url: https://apidoc.ndax.io/#confirmwithdraw
x-websocket-function: ConfirmWithdraw
requestBody:
required: false
content:
application/json:
schema:
type: object
example:
UserId: 1
VerifyCode: Verify Code GUID
responses:
'200':
description: Function reply payload.
content:
application/json:
schema: {}
example:
result: true
/CreateDepositTicket:
post:
operationId: createDepositTicket
summary: Create Deposit Ticket
description: CreateDepositTicket records a deposit ticket for deposits of fiat money (non-crypto national currencies, for example). Crypto-currencies, such as BitCoin or Monero are handled by a different deposit mechanism described in GetDepositInfo. The ticketing mechanism of the Order Management System tracks deposits and withdrawals, interacting with the Asset Manager. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
tags:
- Tickets
x-category: System
x-permissions: Operator, Trading
x-call-type: Synchronous
x-docs-url: https://apidoc.ndax.io/#createdepositticket
x-websocket-function: CreateDepositTicket
requestBody:
required: false
content:
application/json:
schema:
type: object
example:
assetManagerId: 0
accountId: 0
assetId: 0
assetName: null
amount: 0.0
omsId: 0
requestCode: null
requestIP: null
requestUser: 0
requestUserName: null
operatorId: 0
Status: 0
feeAmt: 0.0
updatedByUser: 0
updatedByUserName: null
ticketNumber: 0
depositInfo: ''
createdTimestamp: '0001-01-01T00:00:00'
lastUpdateTimeStamp: '0001-01-01T00:00:00'
comments: null
attachments: null
responses:
'200':
description: Function reply payload.
content:
application/json:
schema: {}
example:
success: true
requestcode: 866f21fe-3461-41d1-91aa-5689bc38503f
x-requires-session: true
/GetAccountDepositTransactions:
post:
operationId: getAccountDepositTransactions
summary: Get Account Deposit Transactions
description: 'Obtains a list of deposits for the account. Users with Trading and AccountReadOnly permission can return deposit transactions only from an account with which they are associated. The owner of the trading venue determines how long to retain transaction history before archiving. Note: Depth in this call is a count of how many deposit transactions to report. It is not "depth of market." Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).'
tags:
- Tickets
x-category: User
x-permissions: Trading, AccountReadOnly
x-call-type: Synchronous
x-docs-url: https://apidoc.ndax.io/#getaccountdeposittransactions
x-websocket-function: GetAccountDepositTransactions
requestBody:
required: false
content:
application/json:
schema:
type: object
example:
OMSId: 1
AccountId: 1
Depth: 200
responses:
'200':
description: Function reply payload.
content:
application/json:
schema: {}
example:
- transactionId: 0
omsId: 0
accountId: 0
cr: 0.0
dr: 0.0
counterparty: 0
transactionType: 0
referenceId: 0
referenceType: 0
productId: 0
balance: 0.0
timeStamp: 0
x-requires-session: true
/GetAccountWithdrawTransactions:
post:
operationId: getAccountWithdrawTransactions
summary: Get Account Withdraw Transactions
description: 'Obtains a list of withdrawals for an account. Users with Trading and AccountReadOnly permission can return withdrawal transactions only from an account with which they are associated. The owner of the trading venue determines how long to retain transaction history before archiving. Note: Depth in this call is a count of how many withdrawal transactions to report. It is not "depth of market." Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).'
tags:
- Tickets
x-category: User
x-permissions: Trading, AccountReadOnly
x-call-type: Synchronous
x-docs-url: https://apidoc.ndax.io/#getaccountwithdrawtransactions
x-websocket-function: GetAccountWithdrawTransactions
requestBody:
required: false
content:
application/json:
schema:
type: object
example:
OMSId: 1
AccountId: 1
Depth: 200
responses:
'200':
description: Function reply payload.
content:
application/json:
schema: {}
example:
- transactionId: 0
omsId: 0
accountId: 0
cr: 0.0
dr: 0.0
counterparty: 0
transactionType: 0
referenceId: 0
referenceType: 0
productId: 0
balance: 0.0
timeStamp: 0
x-requires-session: true
/GetAllDepositRequestInfoTemplates:
post:
operationId: getAllDepositRequestInfoTemplates
summary: Get All Deposit Request Info Templates
description: Returns an array of all templates available to the caller that describe a deposit form for a specific product. An Account Provider may require specific deposit information. Deposit templates answer than need. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
tags:
- Tickets
x-category: System
x-permissions: Operator, Trading
x-call-type: Synchronous
x-docs-url: https://apidoc.ndax.io/#getalldepositrequestinfotemplates
x-websocket-function: GetAllDepositRequestInfoTemplates
requestBody:
required: false
content:
application/json:
schema:
type: object
example:
OMSId: 1
ProductId: 1
responses:
'200':
description: Function reply payload.
content:
application/json:
schema: {}
example:
- Template:
ProviderType: BitcoinRpc
Template: '{}'
ProcessInfo: ''
UseGetDepositWorkflow: true
DepositWorkflow: CryptoWallet
result: true
errormsg: null
statuscode: 0
x-requires-session: true
/GetDepositRequestInfoTemplate:
post:
operationId: getDepositRequestInfoTemplate
summary: Get Deposit Request Info Template
description: Returns a single object describing a single deposit form template that is available to the caller and the caller's account, and appropriate to the product being deposited. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
tags:
- Tickets
x-category: System
x-permissions: Operator, Trading
x-call-type: Synchronous
x-docs-url: https://apidoc.ndax.io/#getdepositrequestinfotemplate
x-websocket-function: GetDepositRequestInfoTemplate
requestBody:
required: false
content:
application/json:
schema:
type: object
example:
OMSId: 1
ProductId: 1
AccountId: 1
TemplateType: TrustPay
responses:
'200':
description: Function reply payload.
content:
application/json:
schema: {}
example:
Template:
ProviderType: BitcoinRpc
Template: '{}'
ProcessInfo: ''
UseGetDepositWorkflow: true
DepositWorkflow: CryptoWallet
result: true
errormsg: null
statuscode: 0
x-requires-session: true
/GetDeposits:
post:
operationId: getDeposits
summary: Get Deposits
description: Returns an array of deposit objects with information about the deposits of a specific account. Users with Trading permission can get deposit information only for their own accounts; users with Operator permission can get deposit information for any account. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
tags:
- Tickets
x-category: System
x-permissions: Operator, Trading
x-call-type: Synchronous
x-docs-url: https://apidoc.ndax.io/#getdeposits
x-websocket-function: GetDeposits
requestBody:
required: false
content:
application/json:
schema:
type: object
example:
OMSId: 1
AccountId: 1
responses:
'200':
description: Function reply payload.
content:
application/json:
schema: {}
example:
- omsId: 0
depositId: 0
accountId: 0
subAccountId: 0
productId: 0
amount: 0.0
x-requires-session: true
/GetDepositTicket:
post:
operationId: getDepositTicket
summary: Get Deposit Ticket
description: Returns details about a single deposit ticket. A deposit ticket documents that a deposit was made or attempted. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
tags:
- Tickets
x-category: System
x-permissions: Operator, Trading
x-call-type: Synchronous
x-docs-url: https://apidoc.ndax.io/#getdepositticket
x-websocket-function: GetDepositTicket
requestBody:
required: false
content:
application/json:
schema:
type: object
example:
OMSId: 1
AccountId: 1
RequestCode: Request Code GUID
TicketId: 100000002
responses:
'200':
description: Function reply payload.
content:
application/json:
schema: {}
example:
assetManagerId: 0
accountId: 0
assetId: 0
assetName: null
amount: 0.0
omsId: 0
requestCode: null
requestIP: null
requestUser: 0
requestUserName: null
operatorId: 0
Status: 0
feeAmt: 0.0
updatedByUser: 0
updatedByUserName: null
ticketNumber: 0
depositInfo: null
createdTimestamp: '0001-01-01T00:00:00'
lastUpdateTimeStamp: '0001-01-01T00:00:00'
comments: null
attachments: null
x-requires-session: true
/GetDepositTicketAttachment:
post:
operationId: getDepositTicketAttachment
summary: Get Deposit Ticket Attachment
description: Returns a single specific deposit ticket attachment based solely on the attachment ID. A user with Trading permission can return an attachment only from a deposit made to that user's associated account; a user with Operator permission can return any attachment. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
tags:
- Tickets
x-category: System
x-permissions: Operator, Trading
x-call-type: Synchronous
x-docs-url: https://apidoc.ndax.io/#getdepositticketattachment
x-websocket-function: GetDepositTicketAttachment
requestBody:
required: false
content:
application/json:
schema:
type: object
example:
attachmentId: 0
responses:
'200':
description: Function reply payload.
content:
application/json:
schema: {}
example:
base64Attachment: null
attachmentId: 0
submittedByUserId: 0
submittedByUserName: null
uploadDate: '0001-01-01T00:00:00'
uploadIP: null
ticketNumber: 0
description: null
x-requires-session: true
/GetDepositTickets:
post:
operationId: getDepositTickets
summary: Get Deposit Tickets
description: Returns an array of deposit ticket objects for a specific account. The call returns all tickets for a given account. Use GetDepositTicket to return a single ticket. Operators (only) can use GetAllDepositTickets to return a subset of tickets. Users with Trading permission can return deposit ticket information only for accounts with which they're associated; users with Operator permission can return deposit ticket information for any account. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
tags:
- Tickets
x-category: System
x-permissions: Operator, Trading
x-call-type: Synchronous
x-docs-url: https://apidoc.ndax.io/#getdeposittickets
x-websocket-function: GetDepositTickets
requestBody:
required: false
content:
application/json:
schema:
type: object
example:
OMSId: 1
OperatorId: 1
AccountId: 1
responses:
'200':
description: Function reply payload.
content:
application/json:
schema: {}
example:
- assetManagerId: 0
accountId: 0
assetId: 0
assetName: null
amount: 0.0
omsId: 0
requestCode: ''
requestIP: ''
requestUser: 0
requestUserName: ''
operatorId: 0
Status: 0
feeAmt: 0.0
updatedByUser: 0
updatedByUserName: ''
ticketNumber: 0
depositInfo: null
createdTimestamp: '0001-01-01T00:00:00'
lastUpdateTimeStamp: '0001-01-01T00:00:00'
comments: null
attachments: null
x-requires-session: true
/GetWithdrawFee:
post:
operationId: getWithdrawFee
summary: Get Withdraw Fee
description: Gets an estimate of a fee for a withdrawal. The Products function of the AlphaPoint Admin can set withdraw fees OMS-wide. You can also set a withdraw fee programmatically using SetOMSFee, but SetOMSFee is a System (not User) call with permission reserved to an exchange operator. Exchange-wide withdrawal fees cannot be overridden. A user with Trading or Withdraw permissions can obtain withdrawal fee estimates only for products and accounts with which the user is associated; a user with Operator permission can obtain withdrawal fee estimates for any product or account. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
tags:
- Tickets
x-category: User
x-permissions: Operator, Trading, Withdraw
x-call-type: Synchronous
x-docs-url: https://apidoc.ndax.io/#getwithdrawfee
x-websocket-function: GetWithdrawFee
requestBody:
required: false
content:
application/json:
schema:
type: object
example:
OMSId: 1
AccountId: 1
ProductId: 1
Amount: 1
responses:
'200':
description: Function reply payload.
content:
application/json:
schema: {}
example:
FeeAmount: 1.06
x-requires-session: true
/GetWithdraws:
post:
operationId: getWithdraws
summary: Get Withdraws
description: Returns a list of withdrawals for a given account ID. Users with Trading permission can return withdrawals only for an account with which they are associated; users with Operator permission can return withdrawals for any account. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
tags:
- Tickets
x-category: System
x-permissions: Operator, Trading
x-call-type: Synchronous
x-docs-url: https://apidoc.ndax.io/#getwithdraws
x-websocket-function: GetWithdraws
requestBody:
required: false
content:
application/json:
schema:
type: object
example:
OMSId: 1
AccountId: 1
responses:
'200':
description: Function reply payload.
content:
application/json:
schema: {}
x-requires-session: true
/GetWithdrawTicket:
post:
operationId: getWithdrawTicket
summary: Get Withdraw Ticket
description: Returns a single withdrawal ticket that matches all values in the Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
tags:
- Tickets
x-category: System
x-permissions: Operator, Trading
x-call-type: Synchronous
x-docs-url: https://apidoc.ndax.io/#getwithdrawticket
x-websocket-function: GetWithdrawTicket
requestBody:
required: false
content:
application/json:
schema:
type: object
example:
OMSId: 1
AccountId: 1
RequestCode: 1d3d01eb-9e7b-47e0-9056-db420bf157ee
responses:
'200':
description: Function reply payload.
content:
application/json:
schema: {}
x-requires-session: true
/GetWithdrawTicketAttachment:
post:
operationId: getWithdrawTicketAttachment
summary: Get Withdraw Ticket Attachment
description: Retrieves an attachment from a withdrawal ticket. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
tags:
- Tickets
x-category: System
x-permissions: Operator, Trading
x-call-type: Synchronous
x-docs-url: https://apidoc.ndax.io/#getwithdrawticketattachment
x-websocket-function: GetWithdrawTicketAttachment
requestBody:
required: false
content:
application/json:
schema:
type: object
example:
attachmentId: 0
responses:
'200':
description: Function reply payload.
content:
application/json:
schema: {}
example:
base64Attachment: ''
attachmentId: 0
submittedByUserId: 0
submittedByUserName: ''
uploadDate: '0001-01-01T00:00:00'
uploadIP: ''
ticketNumber: 0
description: ''
x-requires-session: true
/GetWithdrawTickets:
post:
operationId: getWithdrawTickets
summary: Get Withdraw Tickets
description: Returns a limited array of withdrawal tickets from the specified Order Management System and account. GetWithdrawTickets is usable with Operator and Trading permissions. It returns tickets from a single account. A similar call, GetAllWithdrawTickets, can be used only with Operator permission and returns tickets from all accounts. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
tags:
- Tickets
x-category: System
x-permissions: Operator, Trading
x-call-type: Synchronous
x-docs-url: https://apidoc.ndax.io/#getwithdrawtickets
x-websocket-function: GetWithdrawTickets
requestBody:
required: false
content:
application/json:
schema:
type: object
example:
OMSId: 1
AccountId: 1
StartIndex: 0
Limit: 200
responses:
'200':
description: Function reply payload.
content:
application/json:
schema: {}
x-requires-session: true
/SubmitDepositTicketComment:
post:
operationId: submitDepositTicketComment
summary: Submit Deposit Ticket Comment
description: Creates a comment and attaches that comment to a specific deposit ticket. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
tags:
- Tickets
x-category: System
x-permissions: Operator, Trading
x-call-type: Synchronous
x-docs-url: https://apidoc.ndax.io/#submitdepositticketcomment
x-websocket-function: SubmitDepositTicketComment
requestBody:
required: false
content:
application/json:
schema:
type: object
example:
commentId: 0
enteredBy: 0
enteredDateTime: '0001-01-01T00:00:00'
comment: ''
operatorId: 0
omsId: 0
ticketCode: 43d1a9f0-8dc3-46f9-b457-297c800d8c9c
ticketId: 0
responses:
'200':
description: Function reply payload.
content:
application/json:
schema: {}
example:
success: true
commentid: 10000002
x-requires-session: true
/SubmitWithdrawTicketComment:
post:
operationId: submitWithdrawTicketComment
summary: Submit Withdraw Ticket Comment
description: Creates a comment and attaches that comment to a specific withdrawal ticket. Requires an authenticated session; the documentation states authentication happens over the WebSocket gateway (wss://api.ndax.io/WSGateway/).
tags:
- Tickets
x-category: System
x-permissions: Operator, Trading
x-call-type: Synchronous
x-docs-url: https://apidoc.ndax.io/#submitwithdrawticketcomment
x-websocket-function: SubmitWithdrawTicketComment
requestBody:
required: false
content:
application/json:
schema:
type: object
example:
commentId: 0
enteredBy: 0
enteredDateTime: '0001-01-01T00:00:00'
comment: ''
operatorId: 0
omsId: 0
ticketCode: 43d1a9f0-8dc3-46f9-b457-297c800d8c9c
ticketId: 0
responses:
'200':
description: Function reply payload.
content:
application/json:
schema: {}
example:
success: true
commentid: 10000002
x-requires-session: true
components:
securitySchemes:
apiKeySignature:
type: apiKey
in: header
name: Authorization
x-source: https://apidoc.ndax.io/#authenticateuser