# Quote Same-Entity Security Transfer

Returns a dry-run quote for a same-entity on-us security transfer (an `INTERNAL_REALLOCATION` of type `SECURITY_TRANSFER`), running the same validation and ruleset evaluation as creating the transfer but booking no trades and persisting nothing. The quote reports whether the transfer would be allowed, its settlement type, and the eligible transfer amount. Only the security-transfer type is quotable; other on-us types are rejected. It is indicative only: a successful quote is not a guarantee that the transfer will book.

Endpoint: POST /api/v1/transfers/on-us/quotes/
Version: Version: 25c7baee
Security: HTTPBearer

## Security:

  - `HTTPBearer` (unknown)
    http bearer

## Header parameters:

  - `x-jiko-idempotency` (string, required)
    A new UUID that you generate for each request, reads included. It is part of the request signature and prevents replay of a request. A value that was already sent in the last hour is rejected with `409 jiko.errors.DuplicateRequestError`, even if the first request failed. When you retry a request, generate a new value and sign the request again.

  - `x-jiko-signature` (string, required)
    Base64-encoded HMAC-SHA256 hash of `x-jiko-idempotency + request pathname + body`, keyed with your shared secret. See [Authentication](/products/partner-api/guides/building/auth) for the full algorithm and a code sample.

## Request fields (application/json):

  - `type` (string, required)

  - `transfer_type` (string, required)

  - `from_account` (object, required)

  - `from_account.id` (string, required)

  - `from_account.type` (string, required)

  - `amount` (object, required)
    Creates a transfer for a specific, requested amount.

  - `amount.amount_usdc` (integer, required)

  - `amount.type` (string, required)

## Response 200:

  - `200` (unknown)
    Successful Response

## Response 200 fields (application/json):

  - `is_allowed` (boolean, required)
    Whether the proposed transfer would be permitted at evaluation time.

  - `rejection_reason` (any)
    Partner-facing rejection reason when `is_allowed` is false; null otherwise.

  - `rejection_detail` (any)
    Human-readable explanation of the rejection; null when `is_allowed` is true.

  - `settlement_type` (string, required)
    Settlement type the transfer would receive, e.g. "T+0" or "T+1".

  - `eligible_transfer_amount` (object, required)

  - `eligible_transfer_amount.value` (integer, required)
    USD values are always in cents.

  - `eligible_transfer_amount.currency` (string, required)

  - `eligible_transfer_amount.formatted` (string)

  - `object_type` (string, required)

## Response 401:

  - `401` (unknown)
    The access token is missing, invalid or expired.

## Response 401 fields (application/json):

  - `type` (string, required)

  - `instance` (string, required)

  - `detail` (string, required)

  - `trace_id` (any)

  - `fields` (any)
    Present only on input validation errors. Each entry identifies one invalid field: `loc` is its location, `msg` is the problem, and `type` is the validation rule that failed.

## Response 403:

  - `403` (unknown)
    `x-jiko-signature` does not match the request, or the access token does not permit this action.

## Response 403 fields (application/json):

  - `type` (string, required)

  - `instance` (string, required)

  - `detail` (string, required)

  - `trace_id` (any)

  - `fields` (any)
    Present only on input validation errors. Each entry identifies one invalid field: `loc` is its location, `msg` is the problem, and `type` is the validation rule that failed.

## Response 422:

  - `422` (unknown)
    Validation Error

## Response 422 fields (application/json):

  - `detail` (array)

  - `detail.loc` (array, required)

  - `detail.msg` (string, required)

  - `detail.type` (string, required)

  - `detail.input` (any)

  - `detail.ctx` (object)

