Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developer.clopos.com/llms.txt

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

​
Purpose

Verifies the status and printing capabilities of a single station, such as a kitchen, bar, or custom station.

​
HTTP Request

GET https://integrations.clopos.com/open-api/v2/stations/{id}
This endpoint requires authentication. Include your JWT in the x-token header. See Authentication for how to obtain a token and Errors for error responses.

​
Request Example

curl -X GET "https://integrations.clopos.com/open-api/v2/stations/1" \
  -H "x-token: oauth_example_token" \

​
Response

​
200 OK — Station found

{
  "success": true,
  "data": {
    "id": 1,
    "name": "Kitchen",
    "status": 1,
    "type": 1,
    "printable": 1,
    "created_at": "2026-01-13T14:08:49.000000Z",
    "updated_at": "2026-01-13T14:08:49.000000Z"
  }
}

​
404 Not Found — Station does not exist

{
  "success": false,
  "error": "resource_not_found",
  "message": "Station not found"
}

​
Field Reference

​
Station object

FieldTypeDescription
idintegerStation identifier.
namestringStation name.
statusinteger1 = active, 0 = inactive.
typeintegerStation type. 1 = kitchen, 0 = other.
printableinteger1 if the station can print tickets, 0 otherwise.
created_atstringCreation timestamp (ISO 8601).
updated_atstringLast update timestamp (ISO 8601).

​
Notes

  • The station ID is used for product and printer mapping on the POS side; verify the current restaurant flow before making changes.
  • Stations with printable=0 are designed only for screen notifications or digital preparation processes.
  • If a station is not found, it returns 404; selecting a fallback station on the client side or showing a remapping screen to the user provides a good experience.