> ## Documentation Index
> Fetch the complete documentation index at: https://docs.finsync.ar/llms.txt
> Use this file to discover all available pages before exploring further.

# Infer a mesa trade from an operation

> Suggests side / localAmount / fx from completed non-commission legs. Pass operation_id as a query param (GET or POST) or in the POST body.



## OpenAPI

````yaml /docs/openapi.json post /api/mesas/{id}/infer
openapi: 3.0.0
info:
  title: FinSync API Documentation
  version: 1.0.0
  description: API documentation for FinSync application
  contact:
    name: FinSync Support
    email: support@finsync.com
servers:
  - url: https://api.finsync.ar
    description: Direct Fly API (preferred for API keys and webhooks)
  - url: https://finsync.ar
    description: Same-origin via finsync.ar (Vercel rewrite)
security:
  - apiKey: []
tags:
  - name: Clients
    description: Operations related to clients and their accounts
  - name: Tags
    description: >-
      Company-scoped client labels (Configuración > Etiquetas). Distinct from
      the special Centro de resultados / Centro de costos tag used for budget
      clients.
  - name: Accounts
    description: Operations related to account balances
  - name: Cost Centers
    description: Company centros de resultados (cost_center_id) and their budgets
  - name: Operations
    description: Operations for creating and managing financial operations
  - name: Operation Types
    description: Company operation types management
  - name: Transaction Types
    description: Company transaction types management
  - name: WhatsApp Tools
    description: >-
      Company-scoped WhatsApp bot operation tools (Configuración > WhatsApp >
      Tools). Same WhatsAppOperationTool rows as the dashboard. Authenticate
      with x-api-key.
  - name: External client
    description: >-
      Exports for external (portal-linked) clients. Authenticate with
      `x-api-key` (company-owned client ID) or `Authorization: Bearer` (Auth.js
      session for an ExternalAccessGrant).
  - name: Mesas
    description: >-
      Company FX trading desks (mesas). Same records and paths as the dashboard
      Mesas module. Integrators authenticate with x-api-key; the dashboard uses
      an employee session. Superadmin must set mesas_enabled first; there is no
      public PATCH for that flag. created_by / opened_by / closed_by are null
      for API-key callers.
  - name: Home metrics
    description: >-
      Named dashboard home metrics (list + values). API keys receive the
      Métricas-group cards (day P&L, commissions, cost centers) without the
      metrics-password cookie. Employee sessions need the matching view
      permission; they still skip the UI password gate on this surface.
paths:
  /api/mesas/{id}/infer:
    post:
      tags:
        - Mesas
      summary: Infer a mesa trade from an operation
      description: >-
        Suggests side / localAmount / fx from completed non-commission legs.
        Pass operation_id as a query param (GET or POST) or in the POST body.
      parameters:
        - in: path
          name: id
          required: true
          schema:
            type: integer
          description: Mesa ID
        - in: query
          name: operation_id
          schema:
            type: integer
          description: Operation ID (required on GET; optional on POST if sent in the body)
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
              properties:
                operation_id:
                  type: integer
                  example: 88
            example:
              operation_id: 88
      responses:
        '200':
          description: Suggestion plus legs
          content:
            application/json:
              schema:
                type: object
              example:
                operationId: 88
                suggestion:
                  side: buy
                  localAmount: 125000
                  quoteAmount: 100
                  fx: 1250
                  fallback: false
                legs: []
        '400':
          description: Invalid mesa ID or operation_id
        '401':
          description: Unauthorized - Missing or invalid API key
        '403':
          description: >-
            Mesas module not enabled for this company (superadmin must set
            mesas_enabled). No public PATCH for that flag.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MesasDisabledError'
              example:
                error: Mesas module not enabled for this company
                code: MESAS_DISABLED
        '404':
          description: Mesa or operation not found
        '500':
          description: Server error
      security:
        - apiKey: []
components:
  schemas:
    MesasDisabledError:
      type: object
      properties:
        error:
          type: string
          example: Mesas module not enabled for this company
        code:
          type: string
          example: MESAS_DISABLED
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: x-api-key
      description: API Key for authentication

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.