Kapso API icon

Kapso API

Send WhatsApp messages, templates, flows, media, contacts, broadcasts, and inbox records through Kapso. Choose a resource, then follow each operation setup hints.

Custom API Call → Custom API Call

AI-generated

Summary

Sends an arbitrary HTTP request (GET, POST, PATCH, PUT or DELETE) to any Kapso API endpoint under a chosen API surface, for endpoints the node has no dedicated operation for.

Inputs

  • Custom API Surface — Selects the URL prefix applied before your path: Platform API (/platform/v1, the default), WhatsApp API (/meta/whatsapp/v24.0), or Media Download API (/meta/whatsapp).
  • Phone Number Name or ID — Shown only for the WhatsApp API surface. Selects a connected Kapso WhatsApp number. When set, the phone number ID is prefixed automatically, so you can use paths like /messages.
  • Custom Method — HTTP method: GET (default), POST, PATCH, PUT or DELETE.
  • Custom Relative Path (required) — Path under the selected surface, 1–256 characters, e.g. /whatsapp/contacts.
  • Body JSON (optional) — JSON request body. Shown only for POST, PATCH, PUT and DELETE. Defaults to {}.
  • Custom API Options > Query Parameters — Repeatable name/value pairs appended to the request as the query string.

Output shape

The Kapso API response for the request, returned as n8n JSON items.

The exact response shape depends on the endpoint called. Kapso API errors are normalized by the node's error handler. The source pack shows only signatures, so pagination and item-splitting behavior for this operation is not confirmed.

Examples

Example 1: List contacts from the Platform API with a page parameter

Surface: Platform API; Method: GET; Path: /whatsapp/contacts; Query Parameters: page=1

Example 2: Call a WhatsApp Cloud-style endpoint for a specific number

Surface: WhatsApp API; Phone Number: choose a number; Method: POST; Path: /messages; Body JSON: the message payload

Links

Discussion