Use Cases/Guides

Exporting Ticket Data

SitePro Exporting Ticket Data

The Transaction Logs API allows you to retrieve transaction records for one or more SitePro sites within a specified time range. This endpoint is commonly used for reporting, reconciliation, dashboards, and exporting operational data to external systems.

Endpoint: POST /v1/transactions/logs/load

Request - Load transactions

POST https://platform.sitepro.com/v1/transactions/logs/load

  curl https://platform.sitepro.com/v1/transactions/logs/load \
  -X POST \
  -H "Authorization: Bearer <your_token>" \
  -H "Content-Type: application/json" \
  -d '{
    "siteIds": [123, 124],
    "start": "2024-01-01T00:00:00Z",
    "end": "2024-02-01T00:00:00Z",
    "motionCap": true,
    "modifiedAfter": "2024-02-01T00:00:00Z"
  }'
FieldTypeRequiredDescription
siteIdsintegerYesOne or more site IDs to pull transactions from
startISO 8601YesUTC start of the date range
endISO 8601YesUTC end of the date range
motionCapbooleanNoFilter to motion-capture events only
modifiedAfterstringNoAn optional ISO 8601-formatted UTC time stamp. If provided, only transaction logs modified after this time will be returned.

Request - Load transaction change logs

POST https://platform.sitepro.com/v1/transactions/change-logs

Use the same date range as your transaction query. You can optionally filter by siteIds or ticketNums inside the filters object.

When to Use

Use this endpoint to:

  • Retrieve historical ticket and transaction data
  • Build dashboards or reports
  • Reconcile source and destination activity
  • Export data to external systems
  • Access ticket metadata, volumes, and notes

How You Can Use This Data:

Operational Dashboards

  • Display total volume moved per site using amount and units
  • Show real-time or daily activity using startTime and endTime
  • Track active lanes or service activity using laneName and service.type

Ticket Reconciliation & Validation

  • Match transactions across systems using ticketID, manifestNum, or truckNum
  • Compare source vs destination records using source.siteID and destination.siteID
  • Identify discrepancies between amount and meteredAmount

Customer or Partner Portals

  • Display haul details (driver, company, truck) from the service object
  • Show origin and destination site details for transparency
  • Surface notes and ticket images for audit visibility

Compliance & Regulatory Reporting

  • Extract operator, lease, and well data from the source object
  • Use timestamps and site metadata to generate audit-ready reports

Data Export & Accounting Systems

  • Send transaction data to ERP or billing systems
  • Calculate rates and totals using rate, amount, and units
  • Track service providers and activity for invoicing

Image & Document Workflows

  • Retrieve and display ticket images using ticketImage and imageUUIDs
  • Attach documentation to external systems or reports