> ## 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.

# Answer last look

> Answer last look.

 A selected maker rejects, or improves its frozen terms, before the
 last-look deadline. There is no accept: silence executes.



## OpenAPI

````yaml /proto-openapi/api/openapi.yaml post /api/v1/rfqs/{rfqId}/last-look
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://apimonaco.xyz
    description: Production (Sei mainnet)
security: []
tags:
  - name: AccountsService
  - name: AnalyticsService
  - name: ApplicationsService
  - name: AuthService
  - name: BuildercodeRewardsService
  - name: ComplianceService
  - 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: RfqService
  - name: SweeperService
  - name: TraderCodeService
  - name: TradesService
  - name: WithdrawalsService
paths:
  /api/v1/rfqs/{rfqId}/last-look:
    post:
      tags:
        - RfqService
        - RFQ
      summary: Answer last look
      description: |-
        Answer last look.

         A selected maker rejects, or improves its frozen terms, before the
         last-look deadline. There is no accept: silence executes.
      operationId: respond_rfq_last_look
      parameters:
        - name: rfqId
          in: path
          required: true
          schema:
            type: string
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/RespondRfqLastLookRequest'
        required: true
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RespondRfqLastLookResponse'
        '400':
          description: Invalid response, or the improvement is not strictly better
        '401':
          description: Authentication required
        '403':
          description: RFQ is not enabled for this account (RFQ_DISABLED)
        '404':
          description: RFQ or acceptance not found
        '409':
          description: The last-look deadline passed, or the caller already answered
        '503':
          description: RFQ service unavailable; retry
      security:
        - monacoSignature: []
        - monacoHttpSignature: []
components:
  schemas:
    RespondRfqLastLookRequest:
      required:
        - idempotencyKey
        - acceptanceId
        - response
      type: object
      properties:
        improvedTerms:
          $ref: '#/components/schemas/RfqQuoteTerms'
        idempotencyKey:
          type: string
        acceptanceId:
          type: string
          format: uuid
        response:
          type: string
          description: REJECT or IMPROVE
      additionalProperties: false
    RespondRfqLastLookResponse:
      type: object
      properties:
        acceptanceId:
          type: string
          nullable: true
          format: uuid
        response:
          type: string
          description: REJECT or IMPROVE as recorded
          nullable: true
        recordedAtMs:
          type: integer
          format: int64
          nullable: true
    RfqQuoteTerms:
      required:
        - price
        - capacity
      type: object
      properties:
        price:
          example: '65000.5'
          type: string
          description: Price in quote units per base unit, exact decimal string
        capacity:
          example: '10'
          type: string
          description: Capacity in base units, exact decimal string
      additionalProperties: false
      description: A quote's price and capacity.
  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.