v3

latestOpenAPI 3.0.3Apache 2.02026-07-312637031.3 MB

Transactions

Get a posted transaction

Get a posted transaction by its uuid

get/transactions/posted/{id}

Path parameters

idstring uuid required

Example:472341e0-ea3e-41a1-96bc-fd0185e1eac8

Transaction ID

Response

Posted Transaction

createdstring date-time required

The creation date of the transaction

effective_datestring date-time required

The "effective date" of a transaction. This may be earlier than posted_date in some cases (for example, a transaction that occurs on a Saturday may not be posted until the following Monday, but would have an effective date of Saturday)

enhanced_transactionEnhancedTransactionResponse

Financial data that has been refined by cleansing, categorizing and adding metadata. For example, inconsistencies in raw transaction data that were introduced via data aggregation are removed, transactions are categorized into groups such as "groceries" or utilities", and metadata (such as merchant names or location and timing details) are added for clarity.

idinteger required

idemkeystring required

The idempotency key used when initially creating this transaction.

info_onlyboolean required

Whether or not this transaction represents a purely informational operation or an actual money movement

lead_modeboolean required

Whether or not this transaction was created operating in "lead ledger" mode

posted_datestring date-time required

The date the transaction was posted. This is the date any money is considered to be added or removed from an account.

reference_idstring nullable required

An external ID provided by the payment network to represent this transaction. This will always be null for internal transfers.

settlement_datestring date

The date the transaction was settled according to Synctera's platform. Generally, this can be interpretted the date the transaction was actually processed and settlement by the payment network.

statusstring required

subtypestring required

The specific transaction type. For example, for ach, this may be "outgoing_debit".

tenantstring required

The id of the tenant containing the resource. This is relevant for Fintechs that have multiple workspaces.

transaction_timestring date-time required

The time the transaction occurred.

typestring required

The general type of transaction. For example, "card" or "ach".

updatedstring date-time required

The date the transaction was last updated

uuidstring uuid required

The unique identifier of the transaction.

Example response

{
  "data": {
    "lines": [
      {
        "account_id": "7d943c51-e4ff-4e57-9558-08cab6b963c7",
        "tenant": "abcdef_ghijkl"
      }
    ]
  },
  "idemkey": "7d943c51-e4ff-4e57-9558-08cab6b963c7",
  "tenant": "abcdef_ghijkl"
}