> ## 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 apiv1marginparent margin accountcollateraltransfer in ## OpenAPI ````yaml /proto-openapi/api/openapi.yaml post /api/v1/margin/parent-margin-account/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/parent-margin-account/collateral/transfer-in: post: tags: - MarginAccountsService operationId: transfer_collateral_to_parent_margin_account requestBody: content: application/json: schema: $ref: >- #/components/schemas/TransferCollateralToParentMarginAccountRequest 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: TransferCollateralToParentMarginAccountRequest: type: object properties: asset: type: string nullable: true amount: type: string 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.