Wassenger icon

Wassenger

Interact with Wassenger WhatsApp API
Join our community

Actions148

Overview

This node allows users to send custom API requests to the Wassenger WhatsApp API using any HTTP method and endpoint under the base URL https://api.wassenger.com/v1. It is designed for advanced use cases where predefined operations do not cover specific API endpoints or when users want full control over the request details such as headers, URL parameters, and JSON body.

Common scenarios include:

  • Accessing new or less common API endpoints not yet supported by other node operations.
  • Testing or debugging API calls with custom parameters.
  • Integrating with parts of the Wassenger API that require dynamic or flexible request construction.

For example, a user might send a POST request to /custom-endpoint with specific headers and a JSON payload to trigger a custom workflow in their WhatsApp integration.

Properties

Name Meaning
API endpoint The URL path appended to the base URL https://api.wassenger.com/v1 to form the full API endpoint. Example: /contacts/list
HTTP Method The HTTP method used for the request. Options: GET, POST, PUT, PATCH, DELETE
Headers Key-value pairs representing HTTP headers to include in the request
URL Params Key-value pairs representing URL query parameters to append to the request URL
Body JSON-formatted string representing the request body. Required only for POST, PUT, PATCH, DELETE methods

Output

The node outputs the JSON response returned by the Wassenger API for the executed request. This output is accessible via the json property of the node's output data.

If the API returns binary data (not typical for this operation), it would be handled accordingly, but primarily the node deals with JSON responses.

Dependencies

  • Requires an API key credential for authenticating with the Wassenger API.
  • The base URL for all requests is fixed as https://api.wassenger.com/v1.
  • No additional external dependencies beyond standard HTTP request capabilities.

Troubleshooting

  • Invalid Endpoint or Method: If the API endpoint path or HTTP method is incorrect, the API will likely return an error. Verify the endpoint path and method against the official Wassenger API documentation.
  • Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Malformed JSON Body: For methods requiring a body, ensure the JSON is valid and properly formatted.
  • Header Issues: Incorrect or missing headers may cause authentication or content-type errors.
  • Network Issues: Connectivity problems can cause request failures; verify network access to the Wassenger API.

Common error messages typically come from the API response and should be interpreted according to the Wassenger API error codes and messages.

Links and References

Discussion