---
title: "A fatura pode ser associada a um movimento novo?"
method: GET
path: "/api/financeiro/invoices/{fatura_id}/attach-check"
tags: ["Financeiro (Protected)"]
---

# A fatura pode ser associada a um movimento novo?

`GET /api/financeiro/invoices/{fatura_id}/attach-check`

Advisory pre-check for the #937 rule, used by the create dialogs.

Always 200: `{"ok": true}` or `{"ok": false, "detail": "<motivo>"}`. The
dialogs call this while the user is still filling the form, so a refusal is
data, not an error — anything that isn't a 200 with ok=false is treated by
the frontend as "not checked" and lets the save through.

Deliberately NOT behind INVOICE_ATTACH_RULE_ON_CREATE: the UI may warn about
an attach before the server starts refusing it. Company-scoped through
get_fatura_by_id, like every other read of an invoice.

Plain `def` — synchronous pyodbc must not run on the event loop.

## Path parameters

- `fatura_id` integer, required

## Query parameters

- `valor` number — Valor COM SINAL do movimento a criar (negativo = custo).

## Headers

- `x-api-token` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

## Changes

- **2026-09-15** `9f1d8d54e97f` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/multigest/apis/multigest-protected-api/changes/api/financeiro/invoices/:fatura_id/attach-check/get.md)

---

[API](https://skmtc.dev/multigest/apis/multigest-protected-api.md) · [All operations](https://skmtc.dev/multigest/apis/multigest-protected-api/llms.txt) · [OpenAPI document](https://skmtc.dev/multigest/apis/multigest-protected-api/revisions/447243444af4?raw)