From d1a9ef00d70033f6bdd3ae5c851a19c3fb1dc500 Mon Sep 17 00:00:00 2001 From: "dev-portal-updater[bot]" <149019135+dev-portal-updater[bot]@users.noreply.github.com> Date: Thu, 2 Oct 2025 15:18:05 +0000 Subject: [PATCH 1/3] feat: update `bitgo-api-docs` This commit updates the BitGo API. --- api.yaml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/api.yaml b/api.yaml index 7b5497d..b4f7857 100644 --- a/api.yaml +++ b/api.yaml @@ -7652,6 +7652,9 @@ paths: type: string notation: type: string + checkForDuplicates: + title: Boolean + type: boolean required: true /api/clearing/v1/enterprise/{enterpriseId}/account/{accountId}/settlement/{settlementId}: get: From f26b007e3e49856bc82cdfd73eb3f134fa45cb8e Mon Sep 17 00:00:00 2001 From: "dev-portal-updater[bot]" <149019135+dev-portal-updater[bot]@users.noreply.github.com> Date: Thu, 2 Oct 2025 15:33:31 +0000 Subject: [PATCH 2/3] feat: update `bitgo-api-docs` This commit updates the BitGo API. --- api.yaml | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/api.yaml b/api.yaml index b4f7857..37c7b21 100644 --- a/api.yaml +++ b/api.yaml @@ -6152,10 +6152,10 @@ paths: Partner route to perform a settlement. This endpoint allows partners without disputes enabled to create new settlements between client accounts, transferring funds according to the specified amounts. - Please note that this endpoint cannot be used by partners with disputes enabled, instead use the - V2 Settlement endpoint. This is because dispute enabled partners must have an asyncronous settlement - process to allow clients time to review the settlement and reconcile liabilities agains their trading - activity on your platform. In the event that you cal this endpoint and you have disputes enabled, you + Please note that this endpoint cannot be used by partners with disputes enabled, instead use the + V2 Settlement endpoint. This is because dispute enabled partners must have an asyncronous settlement + process to allow clients time to review the settlement and reconcile liabilities agains their trading + activity on your platform. In the event that you cal this endpoint and you have disputes enabled, you will recieve a 403 response. Error scenarios: @@ -6170,7 +6170,7 @@ paths: - 403: Permission Denied Error - Occurs when the authenticated partner doesn't have necessary permissions. - - Examples: Enterprise does not have OES license, partner is enabled for disputes. + - Examples: Enterprise does not have OES license, partner is enabled for disputes, partner is inactive. - 409: Conflict Error - Occurs when the request conflicts with current state. @@ -6693,7 +6693,7 @@ paths: description: |- Partner route for providing external deposit information tied to an on-chain settlement. This endpoint allows partners to submit information about on-chain deposits that are - associated with a specific settlement. The deposits will be tracked and reconciled + associated with a specific settlement. The deposits will be tracked and reconciled with the settlement transaction. @@ -6710,9 +6710,9 @@ paths: - Occurs when the authenticated partner doesn't have access to the specified settlement. - Examples: Enterprise does not have OES license. - - 404: Not Found Error + - 404: Not Found Error - Occurs when the referenced settlement was not found. - - Examples: Settlement ID doesn't exist, settlement exists but for different partner. + - Examples: Settlement ID doesn't exist, settlement exists but for different partner, partner is inactive. - 409: Conflict Error - Occurs when Deposit information is in conflict. @@ -7041,7 +7041,7 @@ paths: post: summary: Initiate partner settlement description: |- - Used by dispute enabled exchange partners to stage a settlement for connected clients. + Used by dispute enabled exchange partners to stage a settlement for connected clients. This endpoint will: 1. Authenticate the request by verifying the payload and signature provided. @@ -7049,19 +7049,19 @@ paths: a. Create the settlement entity b. Map provided settlement amounts to settlement transfer records for execution. 3. Assign closed, unassigned disputes from prior settlements to this settlement - a. Pull in any adjustedSettlementTransfers from said disputes. + a. Pull in any adjustedSettlementTransfers from said disputes. b. Update the settledInSettlementId on said disputes. - 4. Verify the relevant connection balances against liabilities based on provided settlementAmounts + 4. Verify the relevant connection balances against liabilities based on provided settlementAmounts and assigned settlement transfers from disputes being assigned. - 5. Notify connection owners of a new settlement. + 5. Notify connection owners of a new settlement. 6. Queue an event to finalize the settlement once the dispute window ends. This endpoint is idempotent and can safely be called again with the same exact request body without worrying about creating multiple settlements. - Please note that provided settlement amounts should be based solely on new trading activity + Please note that provided settlement amounts should be based solely on new trading activity that was not included in the last settlement. Instructions from closed, unsettled disputes should - not be included in the calculation of settlement instructions on the + not be included in the calculation of settlement instructions on the Settlement will be processed asynchronously once initiated, after dispute / top up window have elapsed. * Error scenarios: @@ -7076,7 +7076,7 @@ paths: - 403: Permission Denied Error - Occurs when the authenticated partner doesn't have necessary permissions. - - Examples: Enterprise does not have OES license + - Examples: Enterprise does not have OES license, partner is inactive - 409: Conflict Error - Occurs when the request conflicts with current state. From 8038c57f302a6f3ef5a1646c26650b5b7ba636c8 Mon Sep 17 00:00:00 2001 From: "dev-portal-updater[bot]" <149019135+dev-portal-updater[bot]@users.noreply.github.com> Date: Fri, 3 Oct 2025 15:57:46 +0000 Subject: [PATCH 3/3] feat: update `bitgo-api-docs` This commit updates the BitGo API. --- api.yaml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/api.yaml b/api.yaml index 37c7b21..c051288 100644 --- a/api.yaml +++ b/api.yaml @@ -35625,6 +35625,12 @@ paths: schema: type: boolean default: false + - name: excludeEvmKeyringChildWallets + description: excludeEvmKeyringChildWallets - Supports filtering out EVM keyring child wallets via excludeEvmKeyringChildWallets parameter + in: query + schema: + type: boolean + default: false - name: limit description: Maximum number of results to return. If the result set is truncated, use the "nextBatchPrevId" value to get the next batch. in: query