Skip to content

HighLevel: Get Transaction by ID

HighLevel payments.getTransactionById: arguments, response, policy and SDK examples.

← Payments operations · Get started

Operation gohighlevel.get_transaction_by_id

Provider route: GET /payments/transactions/{transactionId}. Alter supplies the connection’s credentials and routing.

Install @alter-ai/sdk @alter-ai/gohighlevel with npm, or alter-sdk-gohighlevel with pip. Supply your connected customer’s grant ID and the arguments described below.

import { App } from "@alter-ai/sdk";
import { HighLevelIntegration } from "@alter-ai/gohighlevel";
async function execute(input: Parameters<HighLevelIntegration["payments"]["getTransactionById"]>[0]) {
const app = new App({ apiKey: process.env.ALTER_API_KEY! });
try {
const provider = new HighLevelIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! });
const call = await provider.payments.getTransactionById(input);
const result = await call.wait();
return result.bodyJson();
} finally {
await app.close();
}
}
import os
from alter_sdk import App
from alter_sdk_gohighlevel import HighLevelIntegration
async def execute(arguments):
async with App(api_key=os.environ["ALTER_API_KEY"]) as app:
provider = HighLevelIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]})
call = await provider.payments.get_transaction_by_id(arguments)
result = await call.wait()
return result.body_json()
FieldTypePresenceDescription and constraints
$objectRootAdditional keys: not allowed
pathobjectRequired within parentAdditional keys: not allowed
path.transactionIdstringRequired within parent
queryobjectRequired within parentAdditional keys: not allowed
query.locationIdstringOptional
query.altIdstringRequired within parent
query.altTypestringRequired within parent

Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.

FieldTypePresenceDescription and constraints
$ModelRootExpand Get Transaction by ID — response body

Referenced models: Get Transaction by ID — response body

Get Transaction by ID — response body
FieldTypePresenceDescription and constraints
$objectRoot
_idstringRequired within parentThe unique identifier for the transaction.
altIdstringRequired within parentAltId is the unique identifier eg: location id.
altTypestringRequired within parentAltType is the type of identifier.
amountJSONOptional
amount (anyOf 1)numberAlternativeTransaction value.
amount (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
amountRefundedJSONOptional
amountRefunded (anyOf 1)numberAlternativeTransaction amount refunded.
amountRefunded (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
chargeIdstringOptionalCharge id for transaction.
chargeSnapshotobjectOptionalCharge snapshot of transaction.
contactIdstringOptionalContact id corresponding to the transaction.
contactSnapshotobjectOptionalContact details of the transaction.
createdAtstringRequired within parentThe creation timestamp of the transaction.
Format: date-time
createdBystringOptionalUser ID who created the transaction.
currencystringOptionalCurrency in which transaction was made.
entityIdstringOptionalEntity id for the transaction. e.g: order id
entitySourceJSONOptionalEntity source details for the transaction.
entitySource (allOf 1)ModelAll variants applyExpand Get Order by ID — response body — source id, meta, name, sub Type, type
entityTypestringOptionalEntity type of transaction (eg: order).
invoiceIdstringOptionalInvoice id for the transaction.
ipAddressstringOptionalIp address from where transaction was initiated.
isParentbooleanOptionalIs parent transaction.
liveModebooleanOptionalTransaction is in live / test mode.
markAsTestbooleanOptionalIs test transaction.
mergedFromContactIdstringOptionalID of the contact that was merged from.
metaobjectOptionalMeta details of the transaction.
paymentProviderobjectOptionalPayment provider details of the transaction.
qboResponseobjectOptionalQbo details of the transaction.
qboSyncedbooleanOptionalIs transaction qbo synced.
receiptIdstringOptionalReceipt id for transaction.
statusobjectOptionalTransaction status.
subscriptionIdstringOptionalSubscription id for transaction.
traceIdstringOptionalTrace id of the transaction.
updatedAtstringRequired within parentThe last update timestamp of the transaction.
Format: date-time

Referenced models: Get Order by ID — response body — source id, meta, name, sub Type, type

Get Order by ID — response body — source id, meta, name, sub Type, type
FieldTypePresenceDescription and constraints
$objectRoot
idstringRequired within parent
metaobjectOptional
namestringOptional
subTypestringOptionalKnown values: one_step_order_form, two_step_order_form, upsell, tap_to_pay, card_payment, store, contact_view, email_campaign, payments_dashboard, shopify, subscription_view, store_upsell, woocommerce, service, meeting, imported_csv, qr_code, saas_one_time, saas_subscription
typestringRequired within parentKnown values: funnel, website, invoice, calendar, text2Pay, document_contracts, membership, mobile_app, communities, point_of_sale, manual, form, survey, payment_link, external

SDK function policy ID: gohighlevel.get_transaction_by_id. Catalog operation: get-transaction-by-id. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.

Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.

Required provider scopes: ["payments/transactions.readonly"]

Pinned headers: {"Version": "v3"}

Official provider source

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.