Skip to content
/
Get transactions

Get transactions

Request

Transaction filtering

  • page: Page number

  • count: Number of customers per page

  • account_id: Checkout ID

  • supplier_id: Supplier ID

  • client_id: Client ID

  • user_id: user ID

  • master_id: team member ID

  • type: transaction type

  • real_money: Indicates whether this is a real-money (fiat) transaction

  • deleted: whether the transaction was deleted

  • start_date: start date of the period

  • end_date: end date of the period

  • balance_is: 0 - any balance, 1 - positive, 2 - negative

  • document_id: document ID

  • changed_after: created or modified at or after this ISO 8601 date and time

Use document_id from a linked membership goods transaction to inspect money transactions on the sale document. A document can contain multiple items and payments; this endpoint does not calculate a membership-specific paid total. Reading it requires Finances access. Results are limited by the caller's allowed accounts, expense types, and finance history window.

Security
BearerPartnerUser
Path
location_idnumberrequired

location ID

Query
pagenumber

Page number

Example:page=1
countnumber

Number of customers per page

Example:count=50
account_idnumber

Checkout ID

Example:account_id=0
supplier_idnumber

Supplier ID

Example:supplier_id=0
client_idnumber

Client ID

Example:client_id=0
user_idnumber

User ID

Example:user_id=0
team_member_idnumber

Team Member ID

Example:team_member_id=0
typenumber

transaction type

Example:type=0
real_moneynumber

Indicates whether this is a real-money (fiat) transaction

Example:real_money=0
deletednumber

whether the transaction was deleted

Example:deleted=0
start_datenumber

period start date

Example:start_date=20251201
end_datenumber

period end date

Example:end_date=20251231
balance_isnumber

0 - any balance, 1 - positive, 2 - negative

Example:balance_is=1
document_idnumber

document ID

Example:document_id=0
changed_afterstring, (date-time)

Return only transactions created or modified at or after this date and time (ISO 8601, for example 2026-09-01T00:00:00+03:00). Use it with last_change_date from the response for incremental synchronization. There is no upper-bound filter: changed_before is accepted but ignored.

Example:changed_after=2026-09-01T00:00:00+03:00
Headers
Acceptstringrequired

e.g. application/vnd.api.v2+json

Example:application/vnd.api.v2+json
Content-Typestringrequired

application/json

Authorizationstringrequired

Bearer partner_token, User user_token

curl -i -X GET \
  'https://developer.alteg.io/_mock/en/b2b-v1/openapi/transactions/{location_id}?page=1&count=50&account_id=0&supplier_id=0&client_id=0&user_id=0&team_member_id=0&type=0&real_money=0&deleted=0&start_date=20251201&end_date=20251231&balance_is=1&document_id=0&changed_after=2026-09-01T00%3A00%3A00%2B03%3A00' \
  -H 'Accept: application/vnd.api.v2+json' \
  -H 'Authorization: Bearer <YOUR_Bearer {PartnerToken}, User {UserToken}_HERE>' \
  -H 'Content-Type: string'

Responses

OK

Bodyapplication/json
successboolean

Execution success status (true)

Example:true
dataArray of objects

Array of objects with data

Example:
[
  {
    "id": 4815162342,
    "document_id": 22256641,
    "expense": { … },
    "date": "2026-04-13T15:34:31-0500",
    "amount": 1000,
    "comment": "Comment",
    "master": { … },
    "supplier": { … },
    "account": { … },
    "client": { … },
    "last_change_date": "2026-02-01T12:00:00-0500",
    "record_id": 308786662,
    "visit_id": 262551993,
    "sold_item_id": 7134634,
    "sold_item_type": "service"
  }
]
metaArray of objects

Metadata (empty array)

Example:
[]
Response
{
  "success": true,
  "data": [
    { … }
  ],
  "meta": []
}