Frequently Asked Questions

Frequently Asked Questions (FAQ)

Below you can find answers to the most frequently asked questions about Adisyo API and Adisyo Webhook.

1. Is webhook integration available?

Currently, Adisyo API does not have webhook support. To receive order data, you need to pull data via API at certain intervals. You can follow the Webhook page for developments regarding webhooks.

2. How can I know if an order has been updated?

To find out if orders have been updated, you can use the View Recent Orders or View Completed Orders endpoints. You can detect changes by comparing the new data you receive from the API with the orders you previously saved.

However, we recommend using webhook integration for a more up-to-date and automatic solution. With webhooks, changes in orders can be delivered to you instantly. You can follow the Webhook page for webhook support and developments.

3. Is there an API to add products?

No, product addition operations cannot yet be performed via API. Product management must be performed through the Adisyo panel (https://pos.adisyo.com (opens in a new tab)).

4. How is product management done?

Products are defined through the Adisyo panel (https://pos.adisyo.com (opens in a new tab)). You can pull the defined products to your application via API and use them by matching with the productunitid found in Adisyo when sending orders. For more information, you can review the View Product List and Create Order pages.

5. Can request limits (rate limiting) be removed?

No, request limits are set for the performance and stability of the application, and special limit removal or increase cannot be made on a customer or company basis.

6. Is there a test environment?

Currently, there is no separate test environment. You can perform your tests in the live environment with the following methods:

  • You can create a separate restaurant for testing purposes.
  • You can proceed with your tests in the real restaurant environment.

7. How to get API Key (x-api-key) and API Secret (x-api-secret)?

API Key and API Secret are created and shared specially by Adisyo for each restaurant. To have this information, you need to contact Adisyo.

For more information, you can check the Authorization section or get support through the contact form (opens in a new tab).

8. What is Consumer Key (x-api-consumer), how should it be filled?

x-api-consumer (or Consumer Key) is a header information used to specify the name of the restaurant or company performing the integration. This field should be written completely with Turkish characters and spaces included for your or your customer's restaurant/company name on Adisyo.

For example:

  • --header "x-api-consumer: BenimKuryem.net"
  • --header "x-api-consumer: KuryeSepeti - Kardeşler Kebap"
  • --header "x-api-consumer: Burger Art - Web Siparişleri"

For more information, you can check the Authorization section.

9. If I have multiple branches, how do I know which restaurant my API request goes to?

In restaurant chains with multiple branches, the headers you send to Adisyo API play a determining role in accessing each restaurant's data:

  • x-api-key: Shows that your company is authorized for integration and is generally constant.
  • x-api-secret: It is defined specifically for each restaurant and varies by restaurant.

So, for example, when you send a request like "Get recent orders", you access the orders of whichever restaurant's x-api-secret information you use.

In summary: You can securely pull data for each branch by using the relevant x-api-secret information for each branch.

Contact

Rate Limits