Wolt ClientAPI icon

Wolt ClientAPI

Interact with the Wolt API

Actions5

Overview

This node interacts with the Wolt API to manage venue menus and related data. It supports operations such as retrieving a menu JSON, creating or replacing a menu, updating inventory quantities, updating item details, and updating menu options for a specific venue.

A common use case is for restaurants or venues using Wolt's platform to automate menu management directly from their POS or menu management system. For example, a restaurant can update item prices or availability in bulk without manually changing them on the Wolt app, or retrieve the current menu JSON to synchronize with other systems.

Specifically, the "Get Menu JSON" operation fetches the menu information for a given venue, returning a resource URL that can be used to poll for detailed menu data.

Properties

Name Meaning
Venue ID The unique identifier of the venue whose menu or items you want to manage or retrieve.
Data JSON data payload sent to the API for operations that modify menu data (not used for GET).

For the "Get Menu JSON" operation, only the "Venue ID" is required since it performs a GET request and does not send additional data.

Output

The output is an array of JSON objects representing the response from the Wolt API for each input item processed.

  • For "Get Menu JSON", the output JSON contains the menu information for the specified venue, including a resource_url field that can be used to poll for the actual menu details.
  • For other operations, the output JSON reflects the API response confirming the success or failure of the requested action.
  • No binary data is output by this node.

Example output snippet for "Get Menu JSON":

{
  "resource_url": "https://example.com/menu/resource/12345",
  "menu": { /* menu details */ }
}

Dependencies

  • Requires an API key credential for authenticating with the Wolt API.
  • Needs username and password credentials for Basic Authentication.
  • The node dynamically selects the API base URL depending on the environment (production or development).
  • Proper configuration of these credentials and environment selection is necessary for successful API calls.

Troubleshooting

  • Common issues:

    • Invalid or missing credentials will cause authentication failures.
    • Incorrect Venue ID may result in "not found" errors.
    • Sending malformed JSON in the "Data" property for PATCH or POST requests can cause API errors.
    • Using the wrong HTTP method for an operation could lead to unexpected responses.

  • Error messages:

    • Authentication errors typically indicate invalid API keys or username/password.
    • Validation errors from the API often point to incorrect data structure in the "Data" JSON.
    • Network or timeout errors suggest connectivity issues with the Wolt API endpoints.

  • Resolutions:

    • Verify and re-enter API credentials.
    • Double-check the Venue ID for correctness.
    • Validate JSON syntax before sending.
    • Ensure network access to the appropriate Wolt API URLs.

Links and References

Discussion