PUT
/
v0
/
ledgers
/
{ledger_id}
/
transactions
/
{transaction_id}
curl --request PUT \
  --url https://api.sandbox.teal.dev/v0/ledgers/{ledger_id}/transactions/{transaction_id} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'teal-instance-id: <teal-instance-id>' \
  --data '{
  "review_status": "reviewed",
  "tag_ids": [
    "<string>"
  ],
  "metadata": {}
}'
This response has no body data.

Authorizations

Authorization
string
headerrequired

The access token received from the authorization server in the OAuth 2.0 flow.

Headers

teal-instance-id
string
required

The Teal instance ID

Path Parameters

transaction_id
string
required

The Transaction ID.

ledger_id
string
required

The Ledger ID.

Body

application/json
review_status
enum<string> | null

Indicates if the transaction has been reviewed. See the reviewing transactions for steps on how to use this.

Available options:
unreviewed,
reviewed
tag_ids
string[] | null

An array of IDs of the Tag objects associated with the Transaction.

Note that Tags are not transitive and the tags on a Transaction can be different than those on its line entry or entires.

metadata
object | null

Arbitrary structured information about the transaction. This could be location of the transaction to display to the user or vendor information to use as part of a Platform or Instance categorization rule. Teal does not use metadata for any accounting purposes.