Archives multiple transactions identified by their transaction IDs. Archiving removes each transaction from funding and hides it from default transaction lists without deleting it. Each transaction keeps all of its details, records when it was archived, who archived it, and why, and can be unarchived at any time.
Only settled transactions that have not been submitted for funding can be archived. These are transactions with a status of In Queue, On Hold, or Rejected. If any listed transaction cannot be archived, the request fails and no transactions are archived. Transactions that are already archived are skipped, and duplicate IDs are ignored. Providing a reason for archiving the transactions is required. The reason is applied to every transaction in the request.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
400The request was rejected and no transactions were archived. This occurs when the request body or reason is missing, the reason is longer than 1,024 characters, no transaction IDs are provided, a transaction ID does not exist, or a transaction has been submitted for funding or is not settled. The response body describes the problem and lists the transaction IDs that caused it.
404The specified tenant was not found.

