Skip to main content
GET
https://www.xn--dkkango-n2a.com/api/integrations
/
restaurants
/
get
Get Restaurants
curl --request GET \
  --url https://www.xn--dkkango-n2a.com/api/integrations/restaurants/get \
  --header 'Access-Token: <api-key>'
{
  "status": true,
  "data": [
    {
      "id": "<string>",
      "name": "<string>"
    }
  ]
}

​
Overview

Retrieves all restaurants/branches accessible with your API key. A single API key can provide access to one or multiple restaurant locations.

​
Headers

​
Access-Token
string
required
Your API access token

​
Response

​
status
boolean
true if successful
​
data
array
Array of restaurant objects

​
Examples

curl -X GET https://www.xn--dkkango-n2a.com/api/integrations/restaurants/get \
  -H 'Access-Token: your-access-token'

​
Success Response (200)

{
  "status": true,
  "data": [
    {
      "id": "8f2b9ce2-04de-4712-842d-a39f64596fdf",
      "name": "Akat Şube"
    },
    {
      "id": "0ca1d2b1-a199-4960-8617-83a659d890c8",
      "name": "Halaskargazi Şube"
    }
  ]
}

​
Error Response (401)

{
  "status": false,
  "error": "yetkisiz erişim",
  "message": "Invalid or expired access token"
}

​
Usage

1

Call on Startup

Fetch restaurant list when your POS application starts
2

Store Locally

Cache restaurant IDs and names in your local database
3

Use in Operations

Use restaurant IDs for status operations and filtering

​
Multi-Branch Access

If your API key is branch-specific:
{
  "data": [
    {
      "id": "8f2b9ce2-04de-4712-842d-a39f64596fdf",
      "name": "Akat Şube"
    }
  ]
}
You can only manage this one location.
The number of restaurants returned depends on how your API key was configured by Dükkango.

Check Status

Get restaurant open/closed status

Open Restaurant

Set restaurant to open

Close Restaurant

Set restaurant to closed

Get Menu

Fetch menu items for restaurants