Actions8
Overview
This node integrates with the iFood API to manage merchant-related data, specifically focusing on listing interruptions for a merchant. It allows users to retrieve a list of interruptions (such as temporary closures or service pauses) associated with a specific merchant by providing the merchant's ID. This is useful for businesses that need to monitor or manage operational interruptions in their iFood merchant account.
Use Case Examples
- A restaurant owner wants to check all current and past interruptions to understand when their service was paused.
- A delivery service manager needs to retrieve interruption data to coordinate logistics around merchant availability.
Properties
| Name | Meaning |
|---|---|
| Merchant ID | The unique identifier of the merchant for whom the interruptions are to be listed. This property is optional; if not provided, the node may list interruptions for a default or all merchants depending on API behavior. |
Output
JSON
json- The JSON response from the iFood API containing the list of interruptions for the specified merchant.
Dependencies
- Requires an API key credential for iFood API authentication to make authorized requests.
Troubleshooting
- If the Merchant ID is incorrect or missing when required, the API may return an error or empty results. Verify the Merchant ID is correct.
- API request failures may occur due to network issues or invalid credentials; ensure the API key is valid and the network connection is stable.
- The node throws a NodeApiError if the API call fails, which includes error details from the iFood API response. Check the error message for specific issues such as rate limits or permission errors.
Links
- iFood API Documentation - Official documentation for the iFood API, useful for understanding available endpoints and data structures related to merchants and interruptions.