Get a transaction

GET /v1/transactions/{id}

Path parameters

  • id string(uuid) Required

    ID of the transaction.

Responses

  • 200 application/json

    OK

    Hide response attributes Show response attributes object
    • id string(uuid) Required

      Unique ID of the transaction.

    • reference string(uuid) Required

      Reference of the money movement. In case you initiate a transfer between two of your own accounts, both transactions (debit and credit) will have the same reference, it can be safely used to correlate them.

    • account_id string(uuid) Required

      ID of the account this transaction belongs to.

    • amount integer(int64) Required

      Amount of the transaction, in cents. The amount is always positive, use direction to give it a sign.

    • local_iban string Required

      IBAN through which this transaction got in or out of the account. Can be the main IBAN of the account or a virtual IBAN.

    • currency string Required

      Currency of the transaction amount, in ISO 4217 format.

    • direction string Required

      Direction of the transaction.

      Values are debit or credit.

    • request_date string(date-time) Required

      Date at which the transaction has been requested, in ISO8601 format. Usually the same as the execution date, except for scheduled transfers and transfer requests.

    • execution_date string(date-time) Required

      Date at which the transaction processing has started or will start, in ISO8601 format. For debits, that’s when the money is removed from the available balance of the account.

    • accounting_date string(date-time)

      Date at which the transaction has been confirmed, in ISO8601 format. For credits, that’s when the money is credited from the available balance of the account.

    • counterparty_name string Required

      Name of the counterparty.

    • Internal note attached to this transaction, visible only in your Memo Bank workspace.

    • status string Required

      Current status of the transaction.

      Values are scheduled, authorized, confirmed, rejected, or canceled.

    • batch_id string(uuid)

      ID of the batch this transaction belongs to, if any.

    • Custom identifier attached to the transaction. It is not transmitted nor visible in your Memo Bank workspace. It can only be retrieved or used to search for transactions via Memo Bank API.

    • Custom metadata attached to the transaction. It is not transmitted nor visible in your Memo Bank workspace and can only be retrieved via API.

    • attachment_count integer(int32) Required

      Number of documents attached to this transaction.

    • source object Required

      Source of the transaction. We may add additional source types over time; your application should be able to handle such additions gracefully.

      One of:
GET /v1/transactions/{id}
curl \
 -X GET https://api.memo.bank/v1/transactions/c70bd7bc-58e0-4fdb-8c1f-70186e0de587
Response examples (200)
{
  "id": "fe98f29d-5165-45ff-83f9-d7aa83e970b5",
  "reference": "fe98f29d-5165-45ff-83f9-d7aa83e970b5",
  "account_id": "708683cb-60f6-464a-a62f-be2e339c34aa",
  "amount": 42,
  "local_iban": "FR27590171083068762111832788",
  "currency": "EUR",
  "direction": "debit",
  "request_date": "2024-05-04T09:42:00+00:00",
  "execution_date": "2024-05-04T09:42:00+00:00",
  "accounting_date": "2024-05-04T09:42:00+00:00",
  "counterparty_name": "string",
  "internal_note": "phone bill",
  "status": "scheduled",
  "batch_id": "dc47b1ee-1bd7-4072-8d1b-27ff4297b33e",
  "custom_id": "637406efda8534de8c0e",
  "custom_metadata": "This is some metadata",
  "attachment_count": 42,
  "source": {
    "type": "bank_account_remuneration"
  }
}