Dinari Withdrawals API
**`Withdrawals` represent the transfer of stablecoins from an `Account` connected to a managed `Wallet` to another `Account` that is owned by the `Entity`.**Since the `Account` is backed by a managed `Wallet`, the `Withdrawal` must be processed by Dinari and the corresponding transaction is submitted on chain.Upon requesting a withdrawal, a `WithdrawalRequest` is created, which is then submitted on chain by Dinari. Once the transfer is submitted on chain, the corresponding `Withdrawal` is created.Currently, withdrawals are made in USDC on the Arbitrum network (Chain ID `eip155:42161`).
Dinari Withdrawals API is one of 10 APIs that Dinari publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.
Tagged areas include Withdrawals. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and an AsyncAPI specification.
This API exposes 5 operations across 4 paths, and defines 17 schemas. It is described by OpenAPI 3.1.0, at version v20260709-097f56a.
Requests are made against a single base URL, https://api-enterprise.sbt.dinari.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Dinari Withdrawals API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as X-API-Key-Id (ApiKeyId).
An API key is passed in the header as X-API-Secret-Key (ApiSecretKey).
ApiKeyId— The API key ID provided on the [Partners Dashboard](https://partners.dinari.com).ApiSecretKey— API Secret Key that is only shown once at API Key creation.
Paths & Operations 5
Across 4 paths, the API surfaces 5 operations — 4 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Withdrawals represent the transfer of stablecoins from an Account connected to a managed Wallet to another Account that is owned by the Entity. Since the Account is backed by a ma…
Schemas 17
The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are Withdrawal (10 properties), Withdrawal1 (10 properties), WithdrawalRequest (7 properties), WithdrawalRequest1 (7 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Dinari 9
Other APIs Dinari publishes across the network.
This is an independent, third-party profile of Dinari Withdrawals 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.