---
api: 'Business API'
---

# Simulate a transfer state update (Sandbox only)

Simulate a transfer state change in the Sandbox environment. 

For example, after you make a transfer in Sandbox, you can change its state to `completed`. The resulting state is final and cannot be changed.

For more information, see the guides: [Test your flows with simulations (Sandbox only)](/docs/guides/manage-accounts/api-usage-and-testing/test-flows-with-simulations).

## Endpoint

POST `/sandbox/transactions/{id}/{action}`

## Parameters

### path parameters

- `id` (string, required)
  The ID of the transfer whose state you want to update.

- `action` (enum, required)
  Possible enum values:

  - `complete`
  - `revert`
  - `decline`
  - `fail`

## Returns

### 200

Information about the updated transfer state

#### Response attributes

- `id` (string)
    The ID of the transfer whose state was updated.
- `state` (enum)
    Indicates the simulated transaction state. Possible values:
    - `completed` - Transaction was successfully processed.
    - `reverted` - Transaction was reverted by the system or company, but not the user. This can happen for a variety of reasons, for example, the receiver being inaccessible.
    - `declined` - Transaction was declined to the user for a good reason, such as insufficient account balance, wrong receiver information, etc.
    - `failed` - Transaction failed during initiation or completion. This can happen for a variety of reasons, for example, invalid API calls, blocked payments, etc.
    Possible enum values:

    - `completed`
    - `reverted`
    - `declined`
    - `failed`
- `created_at` (string)
    The date and time the transfer was created in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format.
- `completed_at` (string, optional)
    The date and time the transfer was completed in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format.