Skip to content

chore: update OpenAPI specs #304

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
github-actions merged 1 commit into from
Oct 13, 2026
Merged

chore: update OpenAPI specs #304

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 26 additions & 6 deletions fern/openapi-cross-chain.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,17 @@
"type": "string",
"default": ""
},
"description": "The trading fee amounts in basis points to charge on the origin chain (supports single or comma-separated values). Must be used together with feeRecipient. When multiple values are provided, must match the length of feeRecipient. Note: integrator fee collection is not yet supported for Tron-originated routes."
"description": "The trading fee amounts in basis points to charge on the origin chain (supports single or comma-separated values). Mutually exclusive with `feePpm`. Must be used together with feeRecipient. When multiple values are provided, must match the length of feeRecipient. Note: integrator fee collection is not yet supported for Tron-originated routes."
},
{
"name": "feePpm",
"in": "query",
"required": false,
"schema": {
"type": "string",
"default": ""
},
"description": "The trading fee amounts in parts-per-million (PPM) to charge on the origin chain (supports single or comma-separated values). Mutually exclusive with `feeBps`. Must be used together with feeRecipient. Each value must be an integer from 0 to 1000000. When multiple values are provided, must match the length of feeRecipient. e.g. 5000 PPM = 50 BPS = 0.5%. Note: integrator fee collection is not yet supported for Tron-originated routes."
},
{
"name": "feeRecipient",
Expand All @@ -173,7 +183,7 @@
"type": "string",
"default": ""
},
"description": "The wallet addresses to receive trading fees on the origin chain (supports single or comma-separated values). Must be used together with feeBps. When multiple values are provided, must match the length of feeBps. Note: integrator fee collection is not yet supported for Tron-originated routes."
"description": "The wallet addresses to receive trading fees on the origin chain (supports single or comma-separated values). Must be used together with feeBps or feePpm. When multiple values are provided, must match the length of feeBps or feePpm. Note: integrator fee collection is not yet supported for Tron-originated routes."
},
{
"name": "feeToken",
Expand All @@ -183,7 +193,7 @@
"type": "string",
"default": ""
},
"description": "The token addresses for fee collection on the origin chain (supports single or comma-separated values). Must be the same as sellToken. When multiple values are provided, must match the length of feeBps. If omitted, defaults to sellToken. Some routes collect the integrator fee through the bridge provider instead of on-chain; the fee still goes to feeRecipient, but it comes out of the token entering the bridge, which is not sellToken when the route swaps before bridging. Read fees.integratorFee.token for the token actually charged. Note: integrator fee collection is not yet supported for Tron-originated routes."
"description": "The token addresses for fee collection on the origin chain (supports single or comma-separated values). Must be the same as sellToken. When multiple values are provided, must match the length of feeBps or feePpm. If omitted, defaults to sellToken. Some routes collect the integrator fee through the bridge provider instead of on-chain; the fee still goes to feeRecipient, but it comes out of the token entering the bridge, which is not sellToken when the route swaps before bridging. Read fees.integratorFee.token for the token actually charged. Note: integrator fee collection is not yet supported for Tron-originated routes."
},
{
"name": "sortQuotesBy",
Expand Down Expand Up @@ -3036,7 +3046,17 @@
"type": "string",
"default": ""
},
"description": "The trading fee amounts in basis points to charge on the origin chain (supports single or comma-separated values). Must be used together with feeRecipient. When multiple values are provided, must match the length of feeRecipient. Note: integrator fee collection is not yet supported for Tron-originated routes."
"description": "The trading fee amounts in basis points to charge on the origin chain (supports single or comma-separated values). Mutually exclusive with `feePpm`. Must be used together with feeRecipient. When multiple values are provided, must match the length of feeRecipient. Note: integrator fee collection is not yet supported for Tron-originated routes."
},
{
"name": "feePpm",
"in": "query",
"required": false,
"schema": {
"type": "string",
"default": ""
},
"description": "The trading fee amounts in parts-per-million (PPM) to charge on the origin chain (supports single or comma-separated values). Mutually exclusive with `feeBps`. Must be used together with feeRecipient. Each value must be an integer from 0 to 1000000. When multiple values are provided, must match the length of feeRecipient. e.g. 5000 PPM = 50 BPS = 0.5%. Note: integrator fee collection is not yet supported for Tron-originated routes."
},
{
"name": "feeRecipient",
Expand All @@ -3046,7 +3066,7 @@
"type": "string",
"default": ""
},
"description": "The wallet addresses to receive trading fees on the origin chain (supports single or comma-separated values). Must be used together with feeBps. When multiple values are provided, must match the length of feeBps. Note: integrator fee collection is not yet supported for Tron-originated routes."
"description": "The wallet addresses to receive trading fees on the origin chain (supports single or comma-separated values). Must be used together with feeBps or feePpm. When multiple values are provided, must match the length of feeBps or feePpm. Note: integrator fee collection is not yet supported for Tron-originated routes."
},
{
"name": "feeToken",
Expand All @@ -3056,7 +3076,7 @@
"type": "string",
"default": ""
},
"description": "The token addresses for fee collection on the origin chain (supports single or comma-separated values). Must be the same as sellToken. When multiple values are provided, must match the length of feeBps. If omitted, defaults to sellToken. Some routes collect the integrator fee through the bridge provider instead of on-chain; the fee still goes to feeRecipient, but it comes out of the token entering the bridge, which is not sellToken when the route swaps before bridging. Read fees.integratorFee.token for the token actually charged. Note: integrator fee collection is not yet supported for Tron-originated routes."
"description": "The token addresses for fee collection on the origin chain (supports single or comma-separated values). Must be the same as sellToken. When multiple values are provided, must match the length of feeBps or feePpm. If omitted, defaults to sellToken. Some routes collect the integrator fee through the bridge provider instead of on-chain; the fee still goes to feeRecipient, but it comes out of the token entering the bridge, which is not sellToken when the route swaps before bridging. Read fees.integratorFee.token for the token actually charged. Note: integrator fee collection is not yet supported for Tron-originated routes."
},
{
"name": "maxNumQuotes",
Expand Down
Loading