Approve or cancel an account movement

Approve an account movement when you want Vitesse to proceed with the transfer. Cancel it when you no longer want to move the funds.

You can only approve or cancel a movement with a Pending status.

Endpoints

EnvironmentMethod and URL
StagingPUT https://staging-api.vitessepsp.com/api/accountmovements/{accountMovementId}
Production – UK HubPUT https://api.vitessepsp.com/api/accountmovements/{accountMovementId}
Production – US HubPUT https://api.us.vitesse.io/api/accountmovements/{accountMovementId}

Replace {accountMovementId} with the movement’s AccountMovementId.

For help choosing an environment, see Environment.

Access requirements

Configure the following access:

OAuth scopeIdentity client role
APIAccountMovements.Create

For more information about scopes, see Authentication. For information about the access granted by specific roles, see Identity client roles.

Before you begin

Obtain the AccountMovementId from the create response or by listing movements.

Retrieve the movement to check its accounts, amounts, fee, status and ExpiresOn time before approving it. You cannot update an expired movement.

Send the request

This example uses Staging to approve movement 98321:

curl --request PUT \
  --url 'https://staging-api.vitessepsp.com/api/accountmovements/98321' \
  --header 'Authorization: Bearer <access-token>' \
  --header 'Content-Type: application/json' \
  --header 'Accept: application/json' \
  --data '{
  "Status": "Approved"
}'

Replace <access-token> with a valid access token that contains the required scope, and any example values with your own details.

To cancel the movement instead, use the same endpoint with this request body:

{
  "Status": "Cancelled"
}

Example response

The API Reference documents successful responses of 200 OK and 202 Accepted, without response bodies.

Retrieve the account movement to check its resulting status. After approval, check for Completed to confirm that Vitesse has completed the movement.

Troubleshoot the request

If the request fails, use the returned HTTP status code to identify the likely cause and corrective action.

If Vitesse rejects the status change, retrieve the account movement and check whether it still has a Pending status and has not expired.

If the request times out or returns an unexpected error, check the account movement’s status before deciding whether to submit the request again.

For error response formats, additional HTTP status codes and error-handling guidance, see Error responses.

Next steps

Check the account movement's status with List account movements, or view its details with Retrieve an account movement. To create another account movement, see Create an account movement.