The request is always sent through a connection (auth wrapping + base URL), so
the /act body must also identify a connection via connectionId, connectionKey,
integrationId, or integrationKey.
url and data are accepted as aliases for path and body respectively — they
are marked [INTERNAL] so they're hidden from the OpenAPI spec but still validated
and passed through, in case callers think in http-request terminology.
Inline HTTP request spec —
apidispatch on /act.The request is always sent through a connection (auth wrapping + base URL), so the /act body must also identify a connection via
connectionId,connectionKey,integrationId, orintegrationKey.urlanddataare accepted as aliases forpathandbodyrespectively — they are marked[INTERNAL]so they're hidden from the OpenAPI spec but still validated and passed through, in case callers think inhttp-requestterminology.