Skip to content

Get fiscal transactions

Request

Filters

ParameterDescription
pagePage number
editable_lengthNumber of clients per page
typeOperation type
statusOperation status
start_datePeriod start date
end_datePeriod end date

Types of all transactions with location account

MeaningDescription
0Sales operation – Active for documents of type Visit
1Sale return operation – Active for documents of type Visit
2Correction operation
4Shift opening operation – Opens a new POS shift
5Shift closing operation – Closes the current POS shift
9Get POS status – Retrieves the current status of the POS device
11Get POS team status – Retrieves the status of all POS devices connected to the team
12Correction operation
13Print X-report – Prints a non-fiscal summary report of the current shift
6Cash deposit – Registers a cash-in transaction in the POS
7Cash withdrawal – Registers a cash-out transaction in the POS

Statuses of All POS Operations

MeaningDescription
0Connection error with POS – Unable to establish a connection with the POS device
1Success – Operation completed successfully
2Sent for printing – The request has been sent to the POS and is waiting for print completion
3Runtime error – An error occurred while processing the operation on the POS device
4Status check error – Failed to retrieve the current status of the POS
5Waiting for POS readiness – Operation is pending until the POS device becomes ready

Document Types

MeaningDescription
1Sale of products
2Provision of services
3Arrival of products
4Products write-off
5Transfer of products
6Inventory
7Visit
8Consumables write-off
9Deposit replenishment
Security
BearerPartnerUser
Path
location_idnumberrequired

location ID

Query
pagenumber

Page number

Example:page=1
editable_lengthnumber

Number of customers per page

Example:editable_length=25
typenumber

Type of transaction

Example:type=20
statusnumber

Operation status

Example:status=6
start_datenumber

Period start date

Example:start_date=20251201
end_datenumber

Period end date

Example:end_date=20251231
Headers
Acceptstringrequired

application/vnd.api.v2+json

Content-Typestringrequired

application/json

Authorizationstringrequired

Bearer access_token, User user_token

curl -i -X GET \
  'https://developer.alteg.io/_mock/en/b2b-v1/openapi/kkm_transactions/{location_id}?page=1&editable_length=25&type=20&status=6&start_date=20251201&end_date=20251231' \
  -H 'Accept: string' \
  -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": 1059, "print_date": "2026-09-21T23:00:00.000-05:00", "printed_count": 1, "sum": 10, "type": { … }, "status": { … }, "document": { … }, "cashier": { … } } ]
metaobject

Metadata (contains the number of transactions found)

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