Get Station by ID

​

Purpose

​

HTTP Request

GET https://integrations.clopos.com/open-api/v2/stations/{id}

​

Request Example

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

const response = await fetch('https://integrations.clopos.com/open-api/v2/stations/1', {
  headers: {
    'x-token': 'oauth_example_token',
  }
});

const station = await response.json();

import requests

url = "https://integrations.clopos.com/open-api/v2/stations/1"
headers = {
    "x-token": "oauth_example_token",
}

response = requests.get(url, headers=headers)
station = response.json()

​

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

​

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.