API ReferenceSubaccounts API

Approve a pending move

View as Markdown
Approves a single move in **CREATED** status and settles it immediately. The move must belong to your entity. Moves are internal transfers between subaccounts — they settle synchronously without bank processing. **Response body** | Field | Type | Description | |-------|------|-------------| | `data` | Object | The move object (`status` reflects the state at response time) | | `warning` | String | Present on **207** when settlement had a recoverable issue | **Success responses** | Status Code | Description | |-------------|-------------| | **201** | The move was approved and settled. | | **207** | The move was approved but settlement failed; see `warning`. | **Error responses** | Status Code | Description | |-------------|-------------| | **400** | The move cannot be approved in its current state. | | **404** | Move not found for this entity. |

Authentication

x-api-keystring

RootPay API key sent in the x-api-key header. Keys are environment-scoped: live_* for production, test_* for sandbox.

Path parameters

move_idstringRequiredformat: "uuid"
ID of the move to approve

Response

Move approved and settled

Errors

400
Bad Request Error
404
Not Found Error