Skip to main content
GET
/
api
/
adm
/
backgroundProcesses
/
transactionReportSyncInfo
Get Transaction Report Sync Info
curl --request GET \
  --url https://localhost:44371/api/adm/backgroundProcesses/transactionReportSyncInfo \
  --header 'Authorization: Bearer <token>'
{
  "importedTransactionEventsInMainDB": 123,
  "transactionEventsInMainDB": 123,
  "importedTransactionEventsInReportDB": 123,
  "transactionEventsInReportDB": 123,
  "approximateNewChargebacks": 123
}

Documentation Index

Fetch the complete documentation index at: https://docs.chargeworx.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Description

Retrieves detailed information about the transaction report synchronization process, which keeps the reporting database in sync with the transactional database. This endpoint provides visibility into data freshness for reporting and analytics, helping administrators ensure that reports reflect the most current transaction data and identify any synchronization delays or failures.

​
Input

No input parameters required.

​
Output

Returns a ReportDataSyncQueryModel containing the current transaction report synchronization status and metadata.

​
Example Request

GET /api/admin/backgroundProcesses/transaction-report-sync-info
Authorization: Bearer {token}

​
Example Response

{
  "lastSyncDate": "2025-10-27T10:45:00Z",
  "transactionsSynced": 15234,
  "syncDurationSeconds": 45,
  "nextScheduledSync": "2025-10-27T11:00:00Z",
  "status": "Completed",
  "errorMessage": null
}

​
Errors

No errors expected - returns sync status even if sync has failed.

​
Notes

  • Sync typically runs every 15 minutes but may vary based on system configuration.
  • Reports may show slightly stale data if sync is delayed or failing.
  • Transactions processed between syncs will not appear in reports until next sync completes.
  • Status “Failed” indicates reports may be missing recent transactions.
  • Check errorMessage field for specific failure reasons when troubleshooting.

Authorizations

​
Authorization
string
header
required

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

Response

Always returned with transaction report synchronization details.

​
importedTransactionEventsInMainDB
integer<int32>
​
transactionEventsInMainDB
integer<int32>
​
importedTransactionEventsInReportDB
integer<int32>
​
transactionEventsInReportDB
integer<int32>
​
approximateNewChargebacks
integer<int32>