> ## Documentation Index > Fetch the complete documentation index at: https://docs.0xmonaco.com/llms.txt > Use this file to discover all available pages before exploring further. # Post apiv1marginrisk bucketscollateraltransfer in > Fund a risk bucket from the parent margin account's unallocated collateral (no wallet movement; the bucket is created if needed). Since 0XM-2632, funding an ISOLATED bucket that holds an open position also credits that position's stored margin — the same behavior as the deprecated `TransferCollateralToMarginAccount` Adjust Margin rail — so adding collateral to support a position has one behavior on every route. A flat isolated bucket and the cross bucket stay plain allocations. ## OpenAPI ````yaml /proto-openapi/api/openapi.yaml post /api/v1/margin/risk-buckets/collateral/transfer-in openapi: 3.0.3 info: title: Monaco Protocol API description: REST API for the Monaco Protocol hybrid CLOB exchange. version: 1.0.0 servers: - url: https://staging.apimonaco.xyz description: Staging server (Testnet) security: [] tags: - name: AccountsService - name: ApplicationsService - name: AuthService - name: BuildercodeRewardsService - name: CopyTradingService - name: DelegatedAgentsService - name: FaucetService - name: FeesService - name: HealthService - name: ManagedMarketsService description: |- Wallet-authenticated maker assignments. The signed session must match both configured maker user and application. Owner IDs are process fences, never auth. Only wallet sessions are supported; delegated-agent sessions receive 403. - name: MarginAccountsService description: |- Current public isolated-margin semantics: - a user has one parent margin account per application scope - opening orders create or reuse isolated position buckets under that parent - parent account creation is handled internally by margin workflows - name: MarketService - name: OrderbookService - name: OrdersService - name: PositionsService description: |- Current public isolated-margin semantics: - positions link to a parent margin account and, when applicable, a bucket id - opening orders create or reuse isolated position buckets under the parent - users can open another isolated position by reusing the parent account with a different market bucket - name: PulseService - name: SweeperService - name: TraderCodeService - name: TradesService - name: WhitelistService - name: WithdrawalsService paths: /api/v1/margin/risk-buckets/collateral/transfer-in: post: tags: - MarginAccountsService description: |- Fund a risk bucket from the parent margin account's unallocated collateral (no wallet movement; the bucket is created if needed). Since 0XM-2632, funding an ISOLATED bucket that holds an open position also credits that position's stored margin — the same behavior as the deprecated `TransferCollateralToMarginAccount` Adjust Margin rail — so adding collateral to support a position has one behavior on every route. A flat isolated bucket and the cross bucket stay plain allocations. operationId: transfer_collateral_to_risk_bucket requestBody: content: application/json: schema: $ref: '#/components/schemas/TransferCollateralToRiskBucketRequest' required: true responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/TransferCollateralToMarginAccountResponse' '429': description: >- Movement rate limit exceeded — withdrawals and collateral transfers share a per-user budget; retry after the interval in details.retryAfter security: - monacoSignature: [] - monacoHttpSignature: [] components: schemas: TransferCollateralToRiskBucketRequest: type: object properties: asset: type: string nullable: true amount: type: string nullable: true tradingPairId: type: string description: |- Trading pair UUID whose isolated risk bucket receives collateral. Required for isolated risk buckets; omitted for cross risk buckets. nullable: true format: uuid strategyKey: type: string nullable: true marginMode: type: string description: >- Risk bucket mode. Defaults to ISOLATED. Values: ISOLATED, CROSS. A CROSS transfer names no pairs: the cross bucket's scope is derived from trading — a pair joins when a cross order on it succeeds and leaves when its positions close — so funding the bucket has nothing to declare. nullable: true selectedTradingPairIds: deprecated: true type: array items: type: string minLength: 1 format: uuid description: >- Deprecated: accepted and ignored. Cross scope is derived from trading (a pair joins the cross bucket when a cross order on it succeeds; after its positions close it stays listed until a later successful cross order on another pair reconciles the bucket), so a cross transfer-in has nothing to declare and can no longer replace the scope. Rejected for ISOLATED, as before. Read the current scope from the cross bucket's row in the margin-accounts list or from this response's selectedTradingPairIds; the parent row carries no scope. Pairs declared before scope became derived stay recorded until they trade and their positions close. nullable: true applyToPositionMargin: type: boolean description: >- What the transferred collateral becomes when the ISOLATED bucket holds an open position. The two intents want opposite fates for the same dollars, so the caller states theirs: - true (and UNSET — the default is the human "Adjust Margin" gesture): the amount is COMMITTED to the position's stored margin. Effective leverage drops and stays down, initial margin required rises by the amount, free collateral is unchanged — new orders cannot spend it. - false: plain allocation. Free collateral rises and the next order can spend it. Programmatic funding loops that top a bucket up to a free collateral target MUST pass false, or each top-up converts into requirement and the loop never converges. Either way the liquidation cushion improves identically (the breach check is bucket-equity based). On a FLAT isolated bucket there is no position to commit to and both values are a plain allocation. Explicit true is rejected for CROSS buckets (cross has no per-position margin); unset/false is a plain allocation there. The response reports what actually happened in `position_margin_credited` — a credit can degrade to a plain allocation when the persisted position row is stale (close/reopen race). nullable: true marginAccountId: type: string description: |- The margin account whose risk bucket is funded: the default margin account (the default) or any of the caller's open sub-accounts, which fund their own risk buckets from their own collateral. A copy-trading sub-account's buckets belong to its follow and are refused. nullable: true TransferCollateralToMarginAccountResponse: type: object properties: movementId: type: string nullable: true marginAccountId: type: string nullable: true asset: type: string nullable: true amount: type: string nullable: true status: type: string nullable: true newEquity: type: string nullable: true newTotalCollateralValue: type: string nullable: true newWithdrawableCollateral: type: string description: >- The largest amount a further transfer-out will accept after this one. See `MarginAccountSummary.withdrawable_collateral`: this is an allocation-bounded figure, not clamped equity headroom. Truncated toward zero at the collateral asset's precision. nullable: true strategyKey: type: string nullable: true riskBucketId: type: string description: Present when collateral was allocated to a risk bucket. nullable: true marginMode: type: string description: >- Present when collateral was allocated to a risk bucket. Values: ISOLATED, CROSS. nullable: true selectedTradingPairIds: type: array items: type: string minLength: 1 format: uuid description: >- The cross bucket's recorded pair scope: what trading has recorded (a pair joins when a cross order on it fills and leaves when its positions close), plus any pair declared before scope became derived, until it trades and its positions close. Only on cross risk-bucket transfers, and omitted while empty — i.e. until a cross order on the bucket has filled. nullable: true positionMarginCredited: type: boolean description: |- Whether the transfer was committed to a position's stored margin. Present only when a position-margin credit was in play: true — the credit landed; false — a credit was requested (or defaulted) but degraded to a plain allocation because the bucket's persisted position row was stale (close/reopen race) — re-issue the Adjust Margin once the new position row lands if the commitment still matters. Absent on plain allocations, parent deposits, and releases. nullable: true securitySchemes: monacoSignature: type: apiKey description: >- Ed25519 session-key request signing. Every authenticated request carries three headers: `X-Monaco-PublicKey` (64-char lowercase-hex session public key), `X-Monaco-Timestamp` (Unix milliseconds, within 30s of server time), and `X-Monaco-Signature` (hex ed25519 signature). The signature is over `METHOD\npath?query\ntimestamp_ms\nSHA256_hex(body)`, where the body hash is the SHA-256 of the empty byte string when there is no body. Obtain the session keypair from `POST /api/v1/auth/challenge` followed by `POST /api/v1/auth/verify`. name: X-Monaco-Signature in: header monacoHttpSignature: type: apiKey description: >- RFC 9421 Ed25519 session-key request signatures. Send Signature-Input, Signature, and Content-Digest together; never combine them with X-Monaco-* credentials. The monaco signature covers @method, @path, @query, and content-digest in that order, with created (Unix seconds within 30s of server time), keyid (registered lowercase-hex session public key), and alg=ed25519 parameters. Content-Digest uses RFC 9530 sha-256 over the exact body bytes, including the empty body. Query coverage retains ordering and percent encoding. Timestamp freshness does not reject repeated identical requests; use endpoint idempotency where supported. Existing legacy signing remains supported during server-first migration; SDK RFC 9421 signing is opt-in. See https://docs.0xmonaco.com/reference/http-message-signatures for the complete profile and trust model. name: Signature in: header ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.