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

Brale Orders API

The Orders API from Brale — 8 operation(s) for orders.

Brale Orders API is one of 6 APIs that Brale publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Order. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 12 operations across 8 paths, and defines 37 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.brale.xyz.

12 operations 8 paths 37 schemas 8 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.brale.xyz
Authentication
OAuth 2.0
Terms of Service
Resource Areas
1

Authentication & Security 1

Brale Orders API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth) using the clientCredentials flow, exposing 11 scopes.

Paths & Operations 12

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

Orders 12
GET
/accounts/{account_id}/tokens/mints
List Mints
list_mints 4 params → 200401403404
POST
/accounts/{account_id}/tokens/mints
Mint Tokens
create_mint 1 param body → 201400401403
GET
/accounts/{account_id}/tokens/transfers
List Tokenization Transfers
list_tokenization_transfers 4 params → 200401403404
POST
/accounts/{account_id}/tokens/transfers
Transfer Tokens
create_tokenization_transfer 1 param body → 201400401403
GET
/accounts/{account_id}/tokens/burns
List Burns
list_burns 4 params → 200401403404
POST
/accounts/{account_id}/tokens/burns
Burn Tokens
create_burn 1 param body → 201400401403
GET
/accounts/{account_id}/transfers
List transfers for an account
list_transfers 8 params → 200400401403404500
POST
/accounts/{account_id}/transfers
Create Transfer
create_transfer 1 param body → 201400401403
GET
/accounts/{account_id}/tokens/mints/{mint_id}
Get Mint
get_mint 2 params → 200401403404
GET
/accounts/{account_id}/transfers/{transfer_id}
Get Transfer
get_transfer 2 params → 200400401403404
GET
/accounts/{account_id}/tokens/burns/{burn_id}
Get Burn
get_burn 2 params → 200401403404
GET
/accounts/{account_id}/tokens/transfers/{transfer_id}
Get Tokenization Transfer
get_tokenization_transfer 2 params → 200401403404

Schemas 37

The contract defines 37 schemas that model the data the API accepts and returns. The most detailed are PaymentDetails (12 properties), BaseTransfer (10 properties), ApiError (8 properties), WireInstructions (7 properties). Each schema is shown below with its type and property counts.

Failure
object
3 properties 1 required
AddressPaymentData
object
3 properties 3 required
MintsList
object
List of mint transactions with pagination metadata
2 properties
TransferDestination
object
4 properties 3 required
MintDestination
object
4 properties 3 required
PaymentData
object
5 properties 2 required
FinancialInstitutionPaymentData
object
6 properties 3 required
Link
object
1 property 1 required
PaymentDataView
object
DateTime
string
ISO-8601 timestamp that includes date and time
ID
string
ID of the resource
BurnsList
object
List of burn transactions with pagination metadata
2 properties
CreateMint
object
2 properties 2 required
ApiErrorV2
object
5 properties 1 required
ThirdPartyFinancialInstitutionPaymentData
object
6 properties 3 required
PaymentDetails
object
12 properties
TransferWithWireInstructions
object
ApiError
object
8 properties
BurnResponse
object
6 properties
CreateBurn
object
3 properties 2 required
BaseTransfer
object
10 properties
Transfer
object
CreateTransfer
object
5 properties 3 required
BurnSource
object
4 properties 3 required
TokenizationTransfersList
object
List of tokenization transfer transactions with pagination metadata
2 properties
TransferSource
object
4 properties 3 required
TransfersList
object
List of transfers with pagination metadata
2 properties
WireInstructions
object
7 properties 6 required
AutomationsTransfer
object
CreateTokenizationTransfer
object
3 properties 3 required
PagingParameters
object
Paging query parameters
3 properties
AddressPaymentDataWithTransaction
object
4 properties 3 required
TokenizationTransferResponse
object
7 properties
Amount
object
2 properties 2 required
BasePaymentData
object
4 properties 2 required
BrandData
objectnull
1 property 1 required
MintResponse
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

brale-orders-api-openapi.yml Raw ↑

Other APIs Brale publishes across the network.

Brale Accounts API
Brale Addresses API
Brale Automations API
Brale Financial Institutions API
Brale Webhooks API
Where this information came from

This is an independent, third-party profile of Brale Orders 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.