---
title: "Atualizar acordo (close-and-replace via pedido)"
method: PUT
path: "/api/socios/{partner_id}/agreements/{agreement_id}"
tags: ["Sócios (Protected)"]
---

# Atualizar acordo (close-and-replace via pedido)

`PUT /api/socios/{partner_id}/agreements/{agreement_id}`

## Path parameters

- `partner_id` integer, required
- `agreement_id` integer, required

## Headers

- `x-api-token` string, nullable

## Request body

- AgreementUpdate — Body for PUT /api/socios/{id}/agreements/{agreement_id}. The apply step is close-and-replace: the in-flight row gets fim/active=0/ superseded_by, and a new row with the new percentagem is inserted.
  - `percentagem` union
    - number
    - string
  - `fim` string, date, nullable — Set to end the agreement on a future date without a successor

## Response `200`

Successful Response

- ChangeRequestSubmitResponse — Return shape for any mutation endpoint. If the request applied immediately (bootstrap / requester is sole sócio), `status` is APPLIED and the new entity's id (if any) is in `applied_entity_id`. Otherwise status is PENDING and the caller waits on votes.
  - `change_request_id` integer, required
  - `status` 'PENDING' | 'APPROVED' | 'REJECTED' | 'EXPIRED' | 'APPLIED', required
  - `approvers_pending` PendingApprover[]
    - `partner_id` integer, required
    - `utilizador_id` integer, nullable
    - `nome` string, nullable
  - `applied_entity_id` integer, nullable

## Other responses

- `422` — Validation Error

---

[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-service-production.skmtc.workers.dev/v1/apis/multigest/multigest-protected-api/revisions/ace841cc41cc/schema)