Skip to main content
POST
Discover pay-in (source) bridging routes for one or more payout destinations.

Authorizations

X-Client-Secret
string
header
required

Contact Mesh to get client Secret

X-Client-Id
string
header
required

Contact Mesh to get client Id

Body

application/json

Request body for POST /api/v1/bridging/routes/deposit — discover pay-in (source) options for fixed payout destinations.

destinations
object[]
required

Destination networks and assets Mesh should match against configured bridging directions (CAIP-2 network + symbol per entry). At least one is required.

Minimum array length: 1
optimized
boolean

When true (default), return at most one destination per distinct source. When false, return every matching origin→destination pair.

Response

Routes retrieved successfully. An empty routes array means no routes are currently available for the given destinations.

status
enum<string>
Available options:
ok,
serverFailure,
permissionDenied,
badRequest,
notFound,
conflict,
tooManyRequest,
locked,
unavailableForLegalReasons
message
string | null

A message generated by the API

displayMessage
string | null

User-friendly display message that can be presented to the end user

errorHash
string | null
read-only

An error grouping hash from string components and caller information. Used by bugsnag on FE for correct error grouping

teamCode
string | null
read-only

Opaque team code for error routing. Resolved from exception origin or caller file path via CODEOWNERS. Format: 2-character code (e.g., "7K", "M2"). Use for alerting/routing, not display.

errorType
string | null

Strictly-typed error type that is explaining the reason of an unsuccessful status of the operation. All possible error types are available in the documentation.

errorData
unknown
content
object | null

Response body for POST /api/v1/bridging/routes/deposit and POST /api/v1/bridging/routes/withdrawal.